Windows 10 upgrade network issue
I had a Windows 7 Pro computer sitting on a domain network. The computer was able to see all the network computers in the File Explorer. I upgraded the computer to Windows 10 using the MediaCreationTool. Everything went fine during the upgrade - no errors. However when I went to the File Explorer (equivalent) I was not able to see any of the network computers. I was able to see some other devices on the network - printers (which are not shared from a PC), my Amazon Fire device etc. I have tried just about everything I can think of and have done an extensive Internet search for a solution so far no go. I have tried turning off the firewall, removing the computer from the domain and renaming then putting it back on the domain. I have tried reinstalling the network drivers etc. One interesting thing is that I can connect to shared drives on any of the other computers on the network using the "Add Network Location". Also, I can see all the network computers in "Search Active Directory". I have no problem connecting to the Internet.
ASKER
Network discovery is on.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi Wes,
Both the FDRP and UPnP were set to Manual and not running the other two were running. I started both and this permitted that computer and one other Win 10 computer to show up in the Network Computer section. My network has mostly Windows 7, now two Windows 10 and one XP computer. The other Windows 10 actually has the same issue, however it was a virtual (Virtual Box) machine, I used to initially try Win 10. I wasn't using it for any actual work - just trying to get familiar with Win 10. It was an early build of Win 10 and I attributed the issue to that fact. After checking and modifying the services on both computers, I am able to see both from each other - but still none of the Windows 7 or XP computers.
Both the FDRP and UPnP were set to Manual and not running the other two were running. I started both and this permitted that computer and one other Win 10 computer to show up in the Network Computer section. My network has mostly Windows 7, now two Windows 10 and one XP computer. The other Windows 10 actually has the same issue, however it was a virtual (Virtual Box) machine, I used to initially try Win 10. I wasn't using it for any actual work - just trying to get familiar with Win 10. It was an early build of Win 10 and I attributed the issue to that fact. After checking and modifying the services on both computers, I am able to see both from each other - but still none of the Windows 7 or XP computers.
Maybe an issue with Server Message Block (SMB)
Try this:
•You must run these commands at an elevated command prompt.
Search: cmd.exe , Right Click on it and Run as Administrator.
•You must restart the computer after you make these changes.
•To enable SMBv1 on the SMB client, run the following commands:
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/n
sc.exe config mrxsmb10 start= auto
•To enable SMBv2 and SMBv3 on the SMB client, run the following commands:
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/n
sc.exe config mrxsmb20 start= auto
Reference below is the technical overview of above, although 10 isn't listed in the title.
Scroll to the bottom and it is in properties.
https://support.microsoft.com/en-us/kb/2696547
Try this:
•You must run these commands at an elevated command prompt.
Search: cmd.exe , Right Click on it and Run as Administrator.
•You must restart the computer after you make these changes.
•To enable SMBv1 on the SMB client, run the following commands:
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/n
sc.exe config mrxsmb10 start= auto
•To enable SMBv2 and SMBv3 on the SMB client, run the following commands:
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/n
sc.exe config mrxsmb20 start= auto
Reference below is the technical overview of above, although 10 isn't listed in the title.
Scroll to the bottom and it is in properties.
https://support.microsoft.com/en-us/kb/2696547
ASKER
I've requested that this question be closed as follows:
Accepted answer: 0 points for TopCatOnyx's comment #a41462039
for the following reason:
Hi Wes,
After trying your second suggestion and not having it do anything (all the commands were successful), I decided to check the services on one of the Windows 7 computers. The FDRP was off, so I started it. Wa-La that computer showed up in the network area of both Windows 10 computers. I started the service on all the rest of the Windows 7 computers, and now they all show up! This begs the question - Why was that service off (set to manual starting)? Anyway, thanks for the quick and helpful responses.
Accepted answer: 0 points for TopCatOnyx's comment #a41462039
for the following reason:
Hi Wes,
After trying your second suggestion and not having it do anything (all the commands were successful), I decided to check the services on one of the Windows 7 computers. The FDRP was off, so I started it. Wa-La that computer showed up in the network area of both Windows 10 computers. I started the service on all the rest of the Windows 7 computers, and now they all show up! This begs the question - Why was that service off (set to manual starting)? Anyway, thanks for the quick and helpful responses.
ASKER
Hi Wes,
After trying your second suggestion and not having it do anything (all the commands were successful), I decided to check the services on one of the Windows 7 computers. The FDRP was off, so I started it. Wa-La that computer showed up in the network area of both Windows 10 computers. I started the service on all the rest of the Windows 7 computers, and now they all show up! This begs the question - Why was that service off (set to manual starting)? Anyway, thanks for the quick and helpful responses.
After trying your second suggestion and not having it do anything (all the commands were successful), I decided to check the services on one of the Windows 7 computers. The FDRP was off, so I started it. Wa-La that computer showed up in the network area of both Windows 10 computers. I started the service on all the rest of the Windows 7 computers, and now they all show up! This begs the question - Why was that service off (set to manual starting)? Anyway, thanks for the quick and helpful responses.
Great glad that you got it resolved.
Interesting that all the Windows 7 Pc's could see each other until updated to Win 10, then the FDRP on the machines not running became a problem.
Glad I was able to guide to finding the solution.
Interesting that all the Windows 7 Pc's could see each other until updated to Win 10, then the FDRP on the machines not running became a problem.
Glad I was able to guide to finding the solution.
Control Panel\All Control Panel Items\Network and Sharing Center\Advanced sharing settings
Click on Domain, Ensure Turn on Network Discovery is on.