W10 no longer can access other devices on network.

I THINK I found the problem/answer in another thread, ... but it is an old thread and I am not sure. That thread is here:

Cannot access shared network drive

In any case, here is the case:

Computer #1 DELL W10-64
Computer #2 Toshiba W7-64
Computer #3 Acer W7-32
NAT drive connected to router.

#2 and #3 work perfectly in every respect. They both access the entire network.

#1 lists itself, #2 and #3 but not NATdrive in Explorer but when I try to connect to either, 2 or 3, I get:

Windows cannot access \\ACER-PC (or \\TOSH-64)

I can access Dell-64 (itself) good and proper.

This has developed within the last week.

#1 Network Discovery on. File and printer sharing on. Homegroup managed by Windows (but I am on a WORKGROUP). Same for PUBLIC. Password Protection is ON.

Help is greatly appreciated in advance.

I have a client that developed the same problem, in the last week.

In his case, it is a Linksys wireless router with a My Book hard drive attached to the router. Three laptops are involved (Win 10, Win 10, Win 8.1) and the laptop with the latest Win 10 updates will not see the My Book while the other laptops can use the My Book. Related to the WannaCry patch from Microsoft??

mahoneycutt said:

I have a client that developed the same problem, in the last week.
In his case, it is a Linksys wireless router with a My Book hard drive attached to the router. Three laptops are involved (Win 10, Win 10, Win 8.1) and the laptop with the latest Win 10 updates will not see the My Book while the other laptops can use the My Book. Related to the WannaCry patch from Microsoft??

My problem is a little worse. W10 doesn't see the NAT at all, and will not connect/access #2 or #3. I would say the problem started just about when WannaCry came on the scene. Let us hope it will be fixed, IF it is a MS update. Thank you for the input. Good to know.

MS update being the cause of the problem is speculation. Still need help with this if available.

WacoJohn said:

...W10 doesn't see the NAT at all... I would say the problem started just about when WannaCry came on the scene...

Did you then turn off SMB1 as a precaution?
WannaCry

Bree said:

Did you then turn off SMB1 as a precaution?
WannaCry

Yes, .. under advice I found in several places on the Internet (CNET, ZDNET, etc) ... Guess I need to turn it back on(?) I will bet my life that is the problem. THANK YOU. Give me your opinion on turning it back on, please.

The worm that delivers WannaCry uses SMB1 to do it. On a corporate network allowing SMB1 poses a risk.

As long as you are happy that your Windows 7 machines are fully up to date and that your router's firewall is blocking access from outside than it should be safe to turn it back on. It's crucial that Windows 7 has the latest patches...

Almost all WannaCry victims were running Windows 7

Bree said:

The worm that delivers WannaCry uses SMB1 to do it. On a corporate network allowing SMB1 poses a risk.

As long as you are happy that your Windows 7 machines are fully up to date and that your router's firewall is blocking access from outside than it should be safe to turn it back on. It's crucial that Windows 7 has the latest patches...

Almost all WannaCry victims were running Windows 7

Based on your BRILLIANT advice, I feel it safe to turn it back on which I just now did. All problem(s) are resolved. Thank you ... immensely.

I have got the same problem. It only show my PC name in network. It won't connect to \\wdmycloud but mycloud does appear in Media Devices section and not Computers. I didn't disable SMB. Please help