Windows 10: Wndows computer can only see other Windows computers

Hi folks
I'm tempted to chuck this whole latest update into the Bin

Computer can see ALL other Windows machines on network including an XP VM and can access shares.
It now can't see ANY NAS / Linux servers (have 2)

Nas servers can see via SAMBA this Windows computer but can't access any of the shared folders -- Samba comes up with message Timeout on Server (after less than around 1/2 sec. !!!

Before the update Windows computers were able to see and access NAS - similarly NAS could access Windows.

The computer that has the problems is where a clean install was done. Windows W10 PRO X-64 UK version.

Honestly I'm getting 100% fed up with the mess that passes for Networking on Windows -- even small homes these days have some sort of network sharing with different devices etc so THIS SHOULD WORK !!!!! Big Fail Ms on this latest update !!

Cheers
jimbo

:)

 

Windows 10 homegroup file sharing issues

Isha,

I'd really appreciate a reply from you on how to resolve this. It is very frustrating that this feature has regressed under Windows 10 and My documents on other computers in our Homegroup can only be opened read only.

I guess reverting to Wndows 7 is an option.

Anyone up for finding a solution in Windows 10?

 

Computer cannot see itself and other computers cannot see it

Thanks for responding.

By saying originally that "Computer C is discoverable" I meant to convey that I'd already checked that setting, but I must not have done that in the best way I think. However I agree the discoverability setting is the first and most logical thing to check.

For anyone reading this who might benefit from knowing, since "Computer C is connected to an access point via ethernet" clicking on the Wi-Fi tab won't get you to the discoverability setting. Instead click on the Ethernet tab, then on the network connection
you are using to get to that setting. [This is the procedure as of Windows 10 version 1607. Windows 10 suffers from lack of product stability, so future versions may be entirely different.]

 

Hey Jimbo,
Not sure if you're asking for info or just ranting *Smile ... but FYI ... SMBv1 is deprecated and is not installed on a on a clean install of Win10 1709 and that might be the issue. Your NAS might still be using SMBv1. Check your NAS settings, some you can change which SMB version it uses or you can check/install SMBv1 again on Win10 ... Control Panel > Programs and Features > Turn Windows Features On or Off > SMB 1.0/CIFS File Sharing Support.

Note: If you do install it, I would not check the box for SMB 1.0/CIFS Automatic Removal.

Win10 1709 and SMBv1 - https://support.microsoft.com/en-us/...r-version-1709

 

Jimbo, you don't mention what Windows update you think broke your networking. Which updates was it?

Thanks.