This is most frustrating since it was working.
I have checked and double checked network discovery and sharing settings on all computers I updated the NIC drivers to the latest for my model on the Lenovo site as well as updating some other things while I was at it. I turned this off and tried the USB stick in the router solution with no change. My NAS was specifically set in the SMB settings to be the master browser. On the laptop I tried the ipscan25.exe mentioned by the OP and it does not see all computers on the network, but, those it does see I can access. That is fine with the NAS since it has a fixed IP, with the other and their DHCP address it means more work. The only way to access other computers is by IP address. Typing \\computer_name in the address bar or trying to map a drive by computer name fails. Yesterday morning it could see the whole network correctly but now it only sees itself. However, the Windlaptop can only see itself. All of the wired PCs (Windwith one WIndows 7) can see each other and the Linux NAS computer in the Windows Network. I have the same problem mentioned in this thread and the funny thing is it just started yesterday.
I have no idea why the USB thing worked, but thank to Eagle51! After this procedure, everything was visible and accessible again. In addition, I have some NAS devices that could be located on the local network only by IP address, not be device name (such as NAS01).
Started turning computers back on and they could all see each other. powered router back up and waited for it to fully initialize (about 2 minutes). This should make the pre 1703 PC the Master Browser.I had same problem. If you have a pre 1703 PC (1607,win7,win8) on your network - Shut down all PC's, start the pre 1703 PC first, then the other PC's. This should make the router the Master Browser.Ģ. If you have a router that has a USB port (and a USB stick) - Shut down all PC's, insert USB stick in the router (may need to reboot router), then start the other PCs. Until MS fixes the Master Browser issue with 1703(Creators Update), here are a couple of workarounds that should work.ġ.
0 kommentar(er)
