Windows 10 Insider Preview Fast Build 19631.1 (mn_release) - May 21 Insider
-
With this build I can not access network drive calling it by name only by IP address.
-
-
With this build I can not access network drive calling it by name only by IP address.
Interesting. I can still navigate the network on this build. First time for a while on the Fast Ring. Jimbo could to start with but now can't.
-
Interesting. I can still navigate the network on this build. First time for a while on the Fast Ring. Jimbo could to start with but now can't.
Yeah! Calling it by name Windows always complains:
And "Diagnose" does nothing.
-
Yeah! Calling it by name Windows always complains:
And "Diagnose" does nothing.
That's what I was getting on previous builds. At the moment it's working for me.
-
-
That's what I was getting on previous builds. At the moment it's working for me.
Go figure it..
On my previous build all was working just fine, I will wait to next one and see.
-
As we all know, MS has this really unwelcome habit of changing some of our settings after an update/upgrade. It had happened to me countless of times. The solution, at least in my case , is to check the following:
- Go from Control Panel to Windows Defender Firewall > Allow an app or feature through WDF > Change settings > Make sure there is a tick before "Remote Desktop"
-Still From Control Panel go to Network and Sharing Center > Change Advanced sharing settings > make sure that "Network Discovery" & "File and Printer sharing" are turned on under Private section.
-Next, the following can be used in a command prompt (run as administrator):
netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns
Press enter after each command and reboot.
-If all else fails, my final go-to solution is to reset the network settings: Win key > Settings (cogwheel) > Network & Internet > Status > Network Reset at the bottom on right pane.
Same thing has to be done on every other computer on your network.
-
As we all know, MS has this really unwelcome habit of changing some of our settings after an update/upgrade. It had happened to me countless of times. The solution, at least in my case , is to check the following:
- Go from Control Panel to Windows Defender Firewall > Allow an app or feature through WDF > Change settings > Make sure there is a tick before "Remote Desktop"
-Still From Control Panel go to Network and Sharing Center > Change Advanced sharing settings > make sure that "Network Discovery" & "File and Printer sharing" are turned on under Private section.
-Next, the following can be used in a command prompt (run as administrator):
netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns
Press enter after each command and reboot.
-If all else fails, my final go-to solution is to reset the network settings: Win key > Settings (cogwheel) > Network & Internet > Status > Network Reset at the bottom on right pane.
Same thing has to be done on every other computer on your network.
Thanks @IronZorg89
The "Network Reset" did the trick. I got my network name back!
-
Go figure it..
On my previous build all was working just fine, I will wait to next one and see.
I haven't had any networking problems with this Fast build series, but have them occasionally with Release Preview 19041.264.
-
I haven't had any networking problems with this Fast build series, but have them occasionally with Release Preview 19041.264.
I haven't had either, until now... But, it's resolved with @IronZorg89 tip.
-
-
Thanks @
IronZorg89
The "Network Reset" did the trick. I got my network name back!
Really glad it worked out for you.