Lost connection to network NAS's on one PC. Works fine on another

Windows 10 ver 1909.

I can see and connect to two different NAS devices on my network from a laptop, but cannot from PC now. I tried to insure Network settings (Sharing settings, SMB, IPv4 NetBios, etc) from laptop were the same on the PC, but nothing worked. Seem to have the same Win 10 updates.

Cannot connect to any devices via \\sharename in Explorer. One NAS icon does show up in Explorer Network devices list, but clicking on it gives a connection error. All mapped links are now broken as well. Thanks in advance for assistance!

JackHughs said:

Have you tried accessing the NAS from the desktop by the NAS' IPv4 address - such as \\192.168.x.x?

Also, try this. From the desktop, open a command prompt and type nbtstat -a Nasname. This won't connect to the NAS but will give you information on the NAS' status.

JackHughs

With nbtstat I see the NAS and Workgroup is registered in the table. I cannot access the NAS via IP in Explorer.

mediamasternc said:

With nbtstat I see the NAS and Workgroup is registered in the table. I cannot access the NAS via IP in Explorer.

I've experienced this same behavior between Windows 10 computers and Windows XP (SMBv1) computers on my LAN.

Check your desktop to make sure that the SMBv1 Client and the SMBv1 Server boxes are both checked. Go to Control Panel > Programs > Turn Windows Features on and off.

JackHughs

I don't think SMB1 needs to be used any longer with Win 10, but nevertheless I have tried it with SMB1 On and OFF. Makes no difference.

- - - Updated - - -

Laptop and PC appear to have same network settings. What am I overlooking?

mediamasternc said:

I don't think SMB1 needs to be used any longer with Win 10...

Whether W10 needs SMB1 or not depends on the server you want to connect to. If the server only supports SMB1 then a W10 machine needs the SMB1 Client in order to connect to it. If you want to connect to a W10 share from an SMB1 device then that W10 PC needs the SMB1 Server enabled. The default in W10 is for SMB1 to be turned off because you won't need it if all the machines on your network are running W10.

Examples of devices that only support SMB1 are XP machines and some older NAS devices.

Bree said:

Whether W10 needs SMB1 or not depends on the server you want to connect to. If the server only supports SMB1 then a W10 machine needs the SMB1 Client in order to connect to it. If you want to connect to a W10 share from an SMB1 device then that W10 PC needs the SMB1 Server enabled. The default in W10 is for SMB1 to be turned off because you won't need it if all the machines on your network are running W10.

Examples of devices that only support SMB1 are XP machines and some older NAS devices.

Yup. Enable SMBv1 Client and Server, reboot, and wait. Discovery is not instantaneous. It may take several on-off cycles of your computer and may not happen for hours - sometimes many hours.

JackHughs

JackHughs said:

Yup. Enable SMBv1 Client and Server, reboot, and wait. Discovery is not instantaneous. It may take several on-off cycles of your computer and may not happen for hours - sometimes many hours.

JackHughs

Yes, I will wait a little longer, but if the icon of the device is shown under "Computers" in Explorer, isn't it considered "discovered"? Also, I can set SMB levels on my NAS, and it is Min=1 and Max=3 so I doubt that would matter. Thx

mediamasternc said:

Yes, I will wait a little longer, but if the icon of the device is shown under "Computers" in Explorer, isn't it considered "discovered"? Also, I can set SMB levels on my NAS, and it is Min=1 and Max=3 so I doubt that would matter. Thx

What error message do you get when you click on the NAS icon?

If you see the icon but cannot access the NAS through the icon, you should be able to access it by typing either \\NASname or \\NAS IPv4 address.

I know that you've tried these methods before. Try them again - can't hurt.

JackHughs