reboot system, now I can't connect to that system over the LAN

So I have this very stable :) Workgroup LAN. All systems are Win 10 64 Pro, and all share some drives for easy backup and file sync, etc.

So this one system, call it A, is rebooted for normal maintenance reasons. Suddenly, system D can't see system A. Even a ping by IP address doesn't work. A ping by system A's name doesn't work. Did I say that system A can see system D over the LAN.

I've had this problem so many times that if Microsoft paid me minimum wage for all the time I've struggled with this problem, I could by a nice shiny new Surface laptop.

Sometimes rebooting both system A and system D 2-3 times each works. This time it didn't.

I've been through all the permissions for private networks and public networks.

I'm beyond frustrated. I'm mad as hell and this time, I'm going to do something about it. I just started this thread. Just what am I supposed to do? or not do?

Hi x509.

Given A was rebooted I think I would run the network reset option on A.

Then I would run the following four bolded commands on A. Use a Command Prompt(admin)
Do not key in info in brackets, there for your information.
ipconfig /flushdns (Clear the dns cache)
nbtstat -RR (release and refesh NetBIOS names)
netsh int ip reset (reset ip settings)
netsh winsock reset (Reset Winsock Catalog)


I read that you rebooted A for normal maintenance and that you've spent hours dealing with issues like this. By any chance did you reset your router. I assume it is also a common element in this issue. I would check if there might be a firmware update available for it. Given your experience you know the risks involved with updating firmware. To do so is your choice, I'm just suggest it be checked.

I will give to you this could and very well is an MS issue. So many threads with sharing on this forum. I assume all your devices are V1703, correct ?


Ken

Caledon Ken said:

Hi x509.

Given A was rebooted I think I would run the network reset option on A.

Then I would run the following four bolded commands on A. Use a Command Prompt(admin)
Do not key in info in brackets, there for your information.
ipconfig /flushdns (Clear the dns cache)
nbtstat -RR (release and refesh NetBIOS names)
netsh int ip reset (reset ip settings)
netsh winsock reset (Reset Winsock Catalog)


I read that you rebooted A for normal maintenance and that you've spent hours dealing with issues like this. By any chance did you reset your router. I assume it is also a common element in this issue. I would check if there might be a firmware update available for it. Given your experience you know the risks involved with updating firmware. To do so is your choice, I'm just suggest it be checked.

I will give to you this could and very well is an MS issue. So many threads with sharing on this forum. I assume all your devices are V1703, correct ?


Ken

Ken,

Yes, I've spent hours and hours over the past 10 or so years dealing with LAN connectivity issues. Always "this just stopped working" situations.

The router hasn't been touched. Internet connections from both (or all) systems performing normally. The router is actually an XFinity cable modem/wireless router, so I don't get to decided on firmware updates.

All systems on my LAN are running Creators Update.

As for the ipconfig, etc. commands, I think I have to wait until System A is misbehaving again. (Or System B or C or D misbehaves.) So I'm going to save off this thread for future use.

Thanks.

x509