Tuesday 5 December 2017

networking - Windows 10 computer can't connect to any other computer on the network

Just upgraded my laptop to Windows 10. Everything seemed fine until I tried to connect to my Win7 desktop. Manually typing the name doesn't work (gives me Unspecified Error (0x80004005)), and when I open the Network section in Windows Explorer it is not listed there. What is listed is two of the other computers on the network, neither of which it will let me connect to (same Unspecified Error). All my computers (including the desktop) are functioning and on the network. They can all see each other, and if I turn on a share from my Win10 laptop then it can be connected to by the desktop. But for some reason, the Win10 machine can see only a few of the machines on the network and cannot connect to any of them, seen or unseen.


I thought at first it was the firewall, but no settings helped and even disabling it did nothing. I have made sure that all relevant computers have discovery turned on but that didn't change anything either. I can ping my desktop, both by IP and by name, but even after pinging I can't browse the drives or even see most of the PCs. By the way, this is impacting being able to connect to explicitly shared drives and to the implicit administrative shares (C$, etc.).




UPDATE:


I realized that since I could ping the desktop that I could try connecting via IP address. That worked, and mysteriously fixed the problem of connecting by name. The Win10 laptop still won't "see" most of the network devices, but it now seems to be able to at least connect to them by name. No idea what's going on with it. I would still hope someone can weigh in with a proper fix for the network discovery (or whatever it is that's broken).

No comments:

Post a Comment

Where does Skype save my contact's avatars in Linux?

I'm using Skype on Linux. Where can I find images cached by skype of my contact's avatars? Answer I wanted to get those Skype avat...