New
#1
Win10 PC must be booted before Win7 otherwise network drives missing?
hi all, I have a Windows 10 PC and its connected via network to a Win7 PC. Both x64
They share drives. I have the problem where the Win7 PC can see the Win10 drives at all times, but not the other way around.
Believe me when i say that ive been thru EVERYTHING on this forum about this topic. Ive been thru the firewall settings. Ive set the services recommended list to "auto", ive done the registry settings thing. Ive spent 4 hours every nite for 2 weeks researching this and trying out things.
What drove me completely nuts was that *sometimes* I could see drives in both directions...but other days it was only one way (always Win7 to Win10 worked ok). I thought my changes that I was trying were sticking...until a reboot, and then the next day when the pc's were turned on...network drives not available.
So ive finally figured out that if i turn on the Win7 PC first, and then the Win10 PC second, i can see network drives of the other in both directions. If i get the order wrong, and the Win 10 PC is turned on first, i cant access the Win7's network drives. Its infuriating. It makes no sense.
So if i get the order wrong, the Win10 PC can see the Win7's network name. But if you try to see a network drive it just goes into thinking mode for what seems like forever, hanging, and then returns with a "cant access network drive". If you try to Map a Network drive it says the same thing, but then allows you to run Windows Network diagnostics and throws this explanation:
As i mentioned...a reboot of win10 so that it is second to boot fixes the problem. So win10 is not seeing new PCs properly that appear on the network unless they are present at bootup? wtf. Please help! any suggestions appreciated. This is a wierd one.
Thanks in advance
Blackout