Groups | Search | Server Info | Login | Register
Groups > alt.msdos.batch.nt > #19654
| From | Frank Slootweg <this@ddress.is.invalid> |
|---|---|
| Newsgroups | alt.msdos.batch.nt, alt.comp.os.windows-10, alt.comp.os.windows-11 |
| Subject | Re: Finding names of computers in network |
| Date | 2024-09-30 09:13 +0000 |
| Organization | NOYB |
| Message-ID | <vde13h.874.1@ID-201911.user.individual.net> (permalink) |
| References | (1 earlier) <vcukjm$384n5$3@toylet.eternal-september.org> <vd1g41.pfk.1@ID-201911.user.individual.net> <vd5q50$lomf$1@dont-email.me> <vd676m.ko4.1@ID-201911.user.individual.net> <vdcbhu$1s7di$1@dont-email.me> |
Cross-posted to 3 groups.
Tom Del Rosso <fizzbintuesday@that-google-mail-domain.com> wrote: > Frank Slootweg wrote: > > Tom Del Rosso <fizzbintuesday@that-google-mail-domain.com> wrote: > >> Frank Slootweg wrote: > >>> > >>> I'm not subscribed to alt.msdos.batch.nt, so had to lookup the OP. > >>> > >>> As this NET VIEW stuff is rather a flimsy/brittle mess on modern > >>> Windows systems, the OP (Tom Del Rosso) may want to have a look at > >>> NirSoft's NetResView. > >>> > >>> <https://www.nirsoft.net/utils/netresview.html> > >> > >> Thanks but the need was for a CLI command. That's why I posted in > >> batch.nt but somebody cross-posted his reply. > > > > NetResView doesn't only have a GUI, but can also save the list of > > network resources to a file in several formats (text, tab-delimited > > text, comma-delimited text, etc.), so you can process that output in a > > batch file. It also has command-line options for specifying what type > > of info is/is-not generated. So perhaps a little less elegant than a > > pure CLI command, but quite workable. > > I tested it and found that at those random times when the peer-to-peer > network is in a state that prevents the NET VIEW command from detecting > the other machines, NetResView is also unable to see them. So all 3 of > these commands fail at the same times. > > NET VIEW > PSEXEC > NetResView Yes, I was afraid that would be the case. I have only a small network, mostly two computers and a NAS, so I know the NetBIOS names and can check things with nbtstat (-n and -r (and, if needed, -a and -R or -RR)), but for a bigger network or/and unknown NetBIOS names, that's of course not feasible. > I don't know yet what makes that happen. Right now I can't make it > happen again, but when it does I have some things to try like restarting > services. Good luck.
Back to alt.msdos.batch.nt | Previous | Next — Previous in thread | Next in thread | Find similar
Finding names of computers in network "Tom Del Rosso" <fizzbintuesday@that-google-mail-domain.com> - 2024-09-23 16:55 -0400
Re: Finding names of computers in network "Tom Del Rosso" <fizzbintuesday@that-google-mail-domain.com> - 2024-09-23 19:31 -0400
Re: Finding names of computers in network "Tom Del Rosso" <fizzbintuesday@that-google-mail-domain.com> - 2024-09-23 23:54 -0400
Re: Finding names of computers in network Ammammata <ammammata@tiscali.it> - 2024-09-24 08:48 +0200
Re: Finding names of computers in network JJ <jj4public@outlook.com> - 2024-09-24 13:48 +0700
Re: Finding names of computers in network "Tom Del Rosso" <fizzbintuesday@that-google-mail-domain.com> - 2024-09-27 04:10 -0400
Re: Finding names of computers in network "Tom Del Rosso" <fizzbintuesday@that-google-mail-domain.com> - 2024-09-27 04:17 -0400
Re: Finding names of computers in network "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2024-09-24 23:07 +0800
Re: Finding names of computers in network Paul <nospam@needed.invalid> - 2024-09-24 20:42 -0400
Re: Finding names of computers in network "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2024-09-25 18:58 +0800
Re: Finding names of computers in network gazelle@shell.xmission.com (Kenny McCormack) - 2024-09-25 13:30 +0000
Re: Finding names of computers in network "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2024-09-25 21:49 +0800
Re: Finding names of computers in network Quincy the fifth <quincythefifth@telekom.net> - 2025-01-31 22:25 +0100
Re: Finding names of computers in network Frank Slootweg <this@ddress.is.invalid> - 2024-09-25 15:09 +0000
Re: Finding names of computers in network Ammammata <ammammata@tiscali.it> - 2024-09-26 08:47 +0200
Re: Finding names of computers in network wasbit <wasbit@nowhere.com> - 2024-09-26 09:42 +0100
Re: Finding names of computers in network Ammammata <ammammata@tiscali.it> - 2024-09-26 12:07 +0200
Re: Finding names of computers in network "Tom Del Rosso" <fizzbintuesday@that-google-mail-domain.com> - 2024-09-27 04:25 -0400
Re: Finding names of computers in network "Tom Del Rosso" <fizzbintuesday@that-google-mail-domain.com> - 2024-09-27 04:26 -0400
Re: Finding names of computers in network Frank Slootweg <this@ddress.is.invalid> - 2024-09-27 10:08 +0000
Re: Finding names of computers in network "Tom Del Rosso" <fizzbintuesday@that-google-mail-domain.com> - 2024-09-27 07:56 -0400
Re: Finding names of computers in network Andy Burns <usenet@andyburns.uk> - 2024-09-27 13:10 +0100
Re: Finding names of computers in network "Tom Del Rosso" <fizzbintuesday@that-google-mail-domain.com> - 2024-09-29 15:58 -0400
Re: Finding names of computers in network Frank Slootweg <this@ddress.is.invalid> - 2024-09-30 09:13 +0000
Re: Finding names of computers in network Andy Burns <usenet@andyburns.uk> - 2024-09-30 10:24 +0100
Re: Finding names of computers in network Paul <nospam@needed.invalid> - 2024-09-30 06:49 -0400
Re: Finding names of computers in network Bernard Peek <bap@shrdlu.com> - 2024-10-06 17:43 +0000
Re: Finding names of computers in network "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2024-10-14 19:32 +0800
Re: Finding names of computers in network Bernard Peek <bap@shrdlu.com> - 2024-10-06 17:40 +0000
csiph-web