Windows 10: Win10 suddenly stopped seeing other computers on network
Win10 suddenly stopped seeing other computers on network
I have two desktops and a NAS drive on my network. Both PC's are Win10. One Pro, the other Home. Everything was working beautifully then out of nowhere the Home machine just stopped accessing the public folder on the Pro machine saying it didn't have permission. I thought the Public folder didn't need permissions if it's shared with Everybody. But it will access and read the other non-public shares on the Pro machine. Weird The Pro machine, however, doesn't even see the Home machine on the network any more, although I can ping it. Again, weird. I had a mapped drive to the Home machine which is now broken. Both PC's can see and access the NAS drive. No settings were changed, nothing was touched, it just worked one minute and stopped the next. The Pro machine was just updated to Build 10586.3 on 11/13/15. But I don't think that caused it because everything worked until the 17th. All the network settings were correct and they have not been changed. I can't find anything about it on the internet except the typical "Make sure Network Discovery is on and file sharing is enabled." Yes, Network Discovery is on and file and printer sharing is enabled on both machines. Still no go. So I'm guessing I'm the only one with this problem. Lucky me. Anyone have any ideas?
10586 broke my network of 9 computers as well...There is a Name Resolving problem right now...
If you are using upper case and lower case for your computer names and or shares rename them'
so they have all the same case Upper or Lower...I was able to fix my network issues on all except
one PC that is on a Wifi link (I can see that one still from a Windows 7 PC)...
This may help some...May not fix all issues depending on your installation.
(don't forget to reboot PC and Router).
Thanks for responding. I tried your advice and ran into the following issues:
1. You can't change the computer name from mixed case to all upper or lower case. You have to change the name itself. ie. "Computer Name" changed to "COMPUTER NAME" won't work. The OK button is greyed out until you change the name to something other than "Computer Name."
2. I changed the name of the one computer with mixed case to something different in all upper case, renamed the problem share to all lower case, rebooted everything and had the exact same issue.
There are other shares that have mixed case names and there's not a problem reading them. Just a quick update. The Pro machine "magically" started working again. I say "magically" because I went to another folder and came back to the Network folder, and presto, everything was there again. The Home machine still doesn't see the NAS drive or itself in its Network folder, and still needs Permission to access the public folder on the Pro machine. I compared the sharing settings from the public folder to the working shared folder and they are identical, yet one works and the other doesn't.
This is maddening. I'm about ready to uninstall Build 10586 and wait for Microsoft to fix this latest "feature." I've experienced network instability and unreliability issues ever since I upgraded to Win8.1. Problems seem to magically fix themselves only to reappear again at a later date for unknown reasons. Microsoft's code quality has suffered in the past few years IMHO.
So the problem as it stands right now:
Pro machine can see itself, the Home machine and the NAS drive in its network folder and can access everything on the network.
Home machine only shows Pro machine in its network folder. Itself and NAS drive are missing. It cannot access Pro's public folder with the error message that it doesn't have permission. It can access shortcuts that point to the NAS drive and the non-public shares.
I am glad changing case on the computer name worked for you. Changing Case on computer doesn't help my issue at my business at all. All of my computer names on the network are the same case and all are running Windows 10 Pro. MS broke networking on 10586 or before and it hasn't been fixed. I have a support plan and they are absolutely clue-less about what is going on. They have been on every system in my business and still can't fix the issue.
Try this fix instead...
Changing the case solved the problem (Partially) on a couple of my PCs...This post was from some time ago...
The "fix" that fixed all of my network is this...Now I can access all my machines...But I've already had to redo it on all
my machines since the last MS Updates...So try it and just be warned that if it works for you you might have to keep redoing it after everytime MS puts out updates...
1. Open a command prompt as an administrator (Elevated Command Prompt)...You can do this by searching
for cmd.exe and then right clicking on it and select run as administrator...
2. Run each of these commands in the elevated command prompt...From what I understand it is disabling part of
SAMBA (Not a problem for me since I don't use SAMBA Shares)...
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc.exe config mrxsmb20 start= disabled
It should say SUCCESS after each command when entered.
You need to do this on all your PCs (I have Nine)...And then reboot each.
This worked for me and I also left all shares in one case as well (May or may not be necessary with this fix)...
Hope this works for you like it did for me...regards.
THIS is the fix. I have about 16 computers in business and we now have our Workgroup back up and running without problems!
Glad to see it worked for you...Just bear in mind that if you're doing Auto Updates as soon as they are available (You can delay this if you are running Win10 PRO) then what appears to be happening is that with the MS Updates, MS is pushing out the networking problem again to users after they implemented this fix and it requires the users (or administrators) to re-implement it...At least that's been the case for me and some others who have posted about it as well...
Davel, thank you.
I'm now able to see all the other computers on the network again. Why don't Microsoft fix this gremlin?
MS are very slow and resistant to change that they do not initiate. (IMHO)
My guess is there's some new feature that they are insistent on and they won't fix the networking problem that is
happening to many until they can make it work for their new feature as well...But that's a guess...
This fix has been posted in this forum as well as their own MS Tech forums so if anybody from MS actually monitors these then they should know about it...
(They were real fast to issue a fix for the privacy settings reset glitch but I'm sure their lawyers had something
to do with that one).
How can I disable this? I tried to type "enabled" in the second line which didnt work. I've had a few extra problems since doing this which may or may not be related.
Today my keyboard stopped working, there was a usb error message pop up but i didn't realise what it was about, then then my k70 corsair keyboard stopped working, i tried restarting and doing an sfc scan but nothing changed, then i...
I work for a small company, with a network of 25 users. We have recently replaced 4 of the users with new Intel machines.
All of the other machines on the network have retained their ability to print to the network printer after the Windows 10...
Just got an ASUS ZenBook UX305 and am having trouble mapping network drives as I can't connect to the devices via explorer (either in the list in Network under "computers" or my manually browsing to the device name or the IP...
after add pin number I can't see or connect to my network computers, If I logon on using my password everything worksi use Microsoft account and my sharing network is work fine
So i have a Tp-Link mr3420 running dd-wrt. On my windows 10 machine in the network tab i can see computers that are not mine, hovever on my router in the dhcp table i cannot see any other computers than my owns. On my linux machine i do not see the...