On 24/9/2024 4:55 am, Tom Del Rosso wrote:
This is easy in a domain, but the problem is peer-to-peer at home.
To get a list of computers in the network, this usually works:
NET VIEW /NETWORK
This commmand relies on SMB 1.0, which is disabled (if not deprecated) in Windows 10 and 11. You need to enable SMB 1.0 first in Windows Features.
I dunno whether there is a Micro$ft successor to that command for newer SMB versions. :)
It is easier to just write the names on a slip
of paper and tape the paper to the side of the monitor
for future reference.
On 24/9/2024 4:55 am, Tom Del Rosso wrote:
This is easy in a domain, but the problem is peer-to-peer at home.
To get a list of computers in the network, this usually works:
NET VIEW /NETWORK
This commmand relies on SMB 1.0, which is disabled (if not deprecated)
in Windows 10 and 11. You need to enable SMB 1.0 first in Windows Features.
I dunno whether there is a Micro$ft successor to that command for newer
SMB versions. :)
Paul wrote:
On Tue, 9/24/2024 11:07 AM, Mr. Man-wai Chang wrote:
On 24/9/2024 4:55 am, Tom Del Rosso wrote:
This is easy in a domain, but the problem is peer-to-peer at home.
To get a list of computers in the network, this usually works:
NET VIEW /NETWORK
This commmand relies on SMB 1.0, which is disabled (if not deprecated) in Windows 10 and 11. You need to enable SMB 1.0 first in Windows Features.
I dunno whether there is a Micro$ft successor to that command for newer SMB versions. :)
I have a test install, and with SMB 1.0 turned on, rebooted and messing about
multiple times in services.msc , "net view" is *still* returning
a complaint about "some service" is not started (2184). Of course,
it does not say which service. Which is Microsofts definition of "fun".
The file sharing troubleshooter (only available via searching for it),
does not help.
I bet I need to reinstall.
Amiright, MWC ? :-) OK, reinstall complete, picture below.
It is easier to just write the names on a slip
of paper and tape the paper to the side of the monitor
for future reference.
Let's see, there is "Sleepy", "Dopey", "Bashful"...
I can see why the machine does not want to connect to them.
[Picture]
https://i.postimg.cc/sgJSRNVF/net-view-W11-W11.gif
Paul
This symptom regarding NET VIEW when run yielding the results
- Service not started Seee HelpMsg 2184 is an age old one dating back to Win8/Win10 era, still applies in the Win11/Win10 era.
Ensure
Window Features
SMB1.0 Client and Server are enabled Windows Features
SMB1.0 Removal - disabled
Services (if not already configured as below)
Function Discovery Provider Host - Auto
Function Discovery Resource Publication - Auto
SSDP Discovery - Auto
Network Sharing
Private
Turn on network discovery, check automatic setup of network connected devices
Turn on ile and printer sharing(optional)
All Networks
Public folder(On or Off, optional for either setting)
Use 128-bit encryption(unlikely anything is still using 40-56 on Windows) Password Protected sharing(recommended)
Restart
Logon same account
****Restart the Router*** - most important step!!
(if a built in router/modem, restart the modem)
Then issue the command via Command Com(Admin)or Powershell(Admin)issuing NET VIEW /NETWORK
and
NET VIEW
Paul wrote:
Let's see, there is "Sleepy", "Dopey", "Bashful"...
I can see why the machine does not want to connect to them.
[Picture]
https://i.postimg.cc/sgJSRNVF/net-view-W11-W11.gif
Paul
This symptom regarding NET VIEW when run yielding the results
- Service not started Seee HelpMsg 2184 is an age old one dating back
to Win8/Win10 era, still applies in the Win11/Win10 era.
Ensure
Window Features
SMB1.0 Client and Server are enabled Windows Features
SMB1.0 Removal - disabled
Services (if not already configured as below)
Function Discovery Provider Host - Auto
Function Discovery Resource Publication - Auto
SSDP Discovery - Auto
Network Sharing
Private
Turn on network discovery, check automatic setup of network connected
devices
Turn on ile and printer sharing(optional)
All Networks
Public folder(On or Off, optional for either setting)
Use 128-bit encryption(unlikely anything is still using 40-56 on Windows)
Password Protected sharing(recommended)
Restart
Logon same account
****Restart the Router*** - most important step!!
(if a built in router/modem, restart the modem)
Then issue the command via Command Com(Admin)or Powershell(Admin)issuing
NET VIEW /NETWORK
and
NET VIEW
On Thu, 26 Sep 2024 01:33:41 -0400, "...winston" <winstonmvp@gmail.com> wrote:
Paul wrote:
Let's see, there is "Sleepy", "Dopey", "Bashful"...
I can see why the machine does not want to connect to them.
[Picture]
https://i.postimg.cc/sgJSRNVF/net-view-W11-W11.gif
Paul
This symptom regarding NET VIEW when run yielding the results
- Service not started Seee HelpMsg 2184 is an age old one dating back
to Win8/Win10 era, still applies in the Win11/Win10 era.
Ensure
Window Features
SMB1.0 Client and Server are enabled Windows Features
SMB1.0 Removal - disabled
Services (if not already configured as below)
Function Discovery Provider Host - Auto
Function Discovery Resource Publication - Auto
SSDP Discovery - Auto
Network Sharing
Private
Turn on network discovery, check automatic setup of network connected
devices
Turn on ile and printer sharing(optional)
All Networks
Public folder(On or Off, optional for either setting)
Use 128-bit encryption(unlikely anything is still using 40-56 on Windows) >> Password Protected sharing(recommended)
Restart
Logon same account
****Restart the Router*** - most important step!!
(if a built in router/modem, restart the modem)
Then issue the command via Command Com(Admin)or Powershell(Admin)issuing
NET VIEW /NETWORK
and
NET VIEW
Just curious, but what is the purpose of restarting the router?
Char Jackson wrote:
On Thu, 26 Sep 2024 01:33:41 -0400, "...winston" <winstonmvp@gmail.com> wrote:
Paul wrote:
Let's see, there is "Sleepy", "Dopey", "Bashful"...
I can see why the machine does not want to connect to them.
[Picture]
https://i.postimg.cc/sgJSRNVF/net-view-W11-W11.gif
Paul
This symptom regarding NET VIEW when run yielding the results
- Service not started Seee HelpMsg 2184 is an age old one dating back
to Win8/Win10 era, still applies in the Win11/Win10 era.
Ensure
Window Features
SMB1.0 Client and Server are enabled Windows Features
SMB1.0 Removal - disabled
Services (if not already configured as below)
Function Discovery Provider Host - Auto
Function Discovery Resource Publication - Auto
SSDP Discovery - Auto
Network Sharing
Private
Turn on network discovery, check automatic setup of network connected >>> devices
Turn on ile and printer sharing(optional)
All Networks
Public folder(On or Off, optional for either setting)
Use 128-bit encryption(unlikely anything is still using 40-56 on Windows)
Password Protected sharing(recommended)
Restart
Logon same account
****Restart the Router*** - most important step!!
(if a built in router/modem, restart the modem)
Then issue the command via Command Com(Admin)or Powershell(Admin)issuing >>> NET VIEW /NETWORK
and
NET VIEW
Just curious, but what is the purpose of restarting the router?
More so related to Windows shortcomings and deprecated features.
SMB 1.0 => deprecated
Net view => deprecated
SMB1 deprecated in favor of the Function Discovery services
Net view relies on SMB1
Windows has a tendency when SMB1 is enabled on Win10/11 to step on its
own toes in the presence of both SMB1 and Function Discovery being
active when looking for connected computernames on the network.
- even more so by enabling SMB1 after and when Function Discovery's
services are currently running.
Resetting the router to find and reassigning ip's(static or dynamic)
gives the deprecated SMB1(and Net View) a better chance when all other >network sharing options are configured properly.
Not a perfect workaround, but helpful and more often than not, worth the >effort.
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.
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
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.
I have only a small network, mostly two computers and a NAS, so I know
the NetBIOS names and can check things with nbtstat
On Thu, 26 Sep 2024 16:08:41 -0400, Paul <nospam@needed.invalid> wrote:
On Thu, 9/26/2024 10:10 AM, Char Jackson wrote:
On Thu, 26 Sep 2024 01:33:41 -0400, "...winston" <winstonmvp@gmail.com> wrote:
Paul wrote:
Restart
Logon same account
****Restart the Router*** - most important step!!
(if a built in router/modem, restart the modem)
Then issue the command via Command Com(Admin)or Powershell(Admin)issuing >>>> NET VIEW /NETWORK
and
NET VIEW
Just curious, but what is the purpose of restarting the router?
It might affect DHCP, but the VM Guest seems to be on the same subnet as the Host.
By firing up a third OS, I can at least see some things work, so I'm not convinced
a router is in the picture.
It remains a mystery. I thought the discovery procedure was essentially contained within a LAN, meaning there wouldn't have to be a router in the picture at all, but perhaps there's an option somewhere to retrieve OUI info from the Internet to help identify the various MAC addresses? Even if so, I wonder why one would be asked to reboot the router, and I especially wonder why
that step would be considered to be "****Restart the Router*** - most important
step!!".
Frank Slootweg wrote:resolution, machines end-up trying broadcasts
I have only a small network, mostly two computers and a NAS, so I know >> the NetBIOS names and can check things with nbtstat
On a large network, there will almost always be multiple domain controllers (often with WINS installed) and due to higher votes, these will tend to win subnet and domain master browser elections, giving stability.
On small networks, there won't tend to be server versions of Windows, just desktop versions, and possibly samba on NASes, and machines will be "off" more of the time,therefore you don't get a stable master browser hence unreliable NETBIOS name
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>
That command works every time in a Windows domain.
Frank Slootweg wrote on 25/09/2024 : <https://www.nirsoft.net/utils/netresview.html>
I compared this with the above soft perfect network scanner
the nirsoft tool misses almost all computers in the network; it lists
the servers (not all of them) , the printers (not all of them), all the
NAS, some VMs and my computer
right now didn't detect at least 6 computers (a couple of them could be
off)
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.
[...]
Frank Slootweg wrote:or within cmd window, try nbtstat with various flags, I forget which do
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.
[...]
Thanks. I'll try that.
On Thu, 9/26/2024 10:10 AM, Char Jackson wrote:
On Thu, 26 Sep 2024 01:33:41 -0400, "...winston" <winstonmvp@gmail.com> wrote:
Paul wrote:
Let's see, there is "Sleepy", "Dopey", "Bashful"...
I can see why the machine does not want to connect to them.
[Picture]
https://i.postimg.cc/sgJSRNVF/net-view-W11-W11.gif
Paul
This symptom regarding NET VIEW when run yielding the results
- Service not started Seee HelpMsg 2184 is an age old one dating back
to Win8/Win10 era, still applies in the Win11/Win10 era.
Ensure
Window Features
SMB1.0 Client and Server are enabled Windows Features
SMB1.0 Removal - disabled
Services (if not already configured as below)
Function Discovery Provider Host - Auto
Function Discovery Resource Publication - Auto
SSDP Discovery - Auto
Network Sharing
Private
Turn on network discovery, check automatic setup of network connected
devices
Turn on ile and printer sharing(optional)
All Networks
Public folder(On or Off, optional for either setting)
Use 128-bit encryption(unlikely anything is still using 40-56 on Windows) >>> Password Protected sharing(recommended)
Restart
Logon same account
****Restart the Router*** - most important step!!
(if a built in router/modem, restart the modem)
Then issue the command via Command Com(Admin)or Powershell(Admin)issuing >>> NET VIEW /NETWORK
and
NET VIEW
Just curious, but what is the purpose of restarting the router?
It might affect DHCP, but the VM Guest seems to be on the same subnet as the Host.
By firing up a third OS, I can at least see some things work, so I'm not convinced
a router is in the picture.
On 24/9/2024 4:55 am, Tom Del Rosso wrote:
This is easy in a domain, but the problem is peer-to-peer at home.
To get a list of computers in the network, this usually works:
NET VIEW /NETWORK
This commmand relies on SMB 1.0, which is disabled (if not deprecated)
in Windows 10 and 11. You need to enable SMB 1.0 first in Windows Features.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 361 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 123:22:50 |
| Calls: | 7,716 |
| Files: | 12,861 |
| Messages: | 5,727,955 |
