Network Reset after W10 Updates!

Ken429 · 31 Aug 2020

I've posted this issue in the past (this has been a problem for years) but maybe there has been a better way to resolve developed since then? Every #$%ing time W10 does one of its Cumm Updates I have to go into each computer and "Reset Network" in order to get that computer to show up on my home network. Then if I forget to go into the Device Manager and set the Network Adapter so that it ignores requests to Wake the Sleep function becomes useless since every few minutes the system gets a "wake up" call. There has got to be a better solution. Too bad Microsoft can't fix the problem - must be some hidden issue I'm ignoring and the Windows Developers know better?

I must be one of the few that have a home network with multiple computers that uses file sharing across the network?! I would think that by now more people would be complaining. Anyway, is there a better way or do I have something setup wrong on my home network that causes this to happen? Frustrated.

Samuria · 31 Aug 2020

It actually makes sense after major update it's a new network and PC so for security everything is set to best practice to keep it safe. The problem connecting to network shares can be over come by settings fixed IP adding pc to host file or by using IP to connect instead of NetBIOS

Ken429 · 31 Aug 2020

Since I got 8 systems on my home network the Network Reset routine is an annoyance. So...a long time ago I mapped the drives I use on my "Home Server" on all the systems on the home network. That works to defeat the Microsoft we know best for you after an update! But... I don't want to map all the shared drives on all the systems on the network. You seem to know what I need to do to avoid the "Reset" routine. Could you please share with me a brief "tutorial" or where I can find a detailed explanation of what I need to setup or change in W10 2004 to get the job done once and for all. Thanks.

Samuria · 31 Aug 2020

There isnt a simply reset as 2004 had updates to fix its problems so things change again.

You can create simple scripts to map drives

net us s: \\192.168.1.24\sharename

type in notepad and save as a cmd file ie mapserver.cmd then you can run it to map the drive change s: to the drive letter you want

Paul Black · 31 Aug 2020

Samuria said:

There isnt a simply reset as 2004 had updates to fix its problems so things change again.

You can create simple scripts to map drives

net us s: \\192.168.1.24\sharename

type in notepad and save as a cmd file ie mapserver.cmd then you can run it to map the drive change s: to the drive letter you want

I agree with @Samuria, a script will be the simplest method!

Ken429 · 31 Aug 2020

Seems like the cure may be worse that the disease? The last thing I want to do is Map all the shared drives on all the systems I have on the home network. I guess I'll learn to live with the "Net Work Reset" after a "major" update for the next ? years.

Just to confuse the issue - the one system on the network that does not always require a Network Reset is the 3900X/ASRock Taichi X470 MB. Seems like every CPU/MB combination I have on the network has it's own set of W10 anomalies after W10 update.

Thanks all for the input.

andyc56 · 31 Aug 2020

Ken429 said:

I've posted this issue in the past (this has been a problem for years) but maybe there has been a better way to resolve developed since then? Every #$%ing time W10 does one of its Cumm Updates I have to go into each computer and "Reset Network" in order to get that computer to show up on my home network. Then if I forget to go into the Device Manager and set the Network Adapter so that it ignores requests to Wake the Sleep function becomes useless since every few minutes the system gets a "wake up" call. There has got to be a better solution. Too bad Microsoft can't fix the problem - must be some hidden issue I'm ignoring and the Windows Developers know better?

I must be one of the few that have a home network with multiple computers that uses file sharing across the network?! I would think that by now more people would be complaining. Anyway, is there a better way or do I have something setup wrong on my home network that causes this to happen? Frustrated.

I have had similar problems intermittently after updates with my two desktop machines, and repeatably after restart of my laptop. I've had 100 percent success by implementing this solution, which involves restarting the "Function Discovery Resource Publication" service. I initially did this manually in the services applet (services.msc), then changed to a batch file (which needs to be run as administrator). Finally, I implemented the task scheduler solution from the linked post on my laptop (as described here).

What happened in my case was that intermittently after a Windows update of all my machines, at least one machine could not see itself under the "Network" node in Windows File Explorer. When this occurred, other machines on the network could not see it either. Then I restarted the "Function Discovery Resource Publication" service on the machine in question, and afterwards it could see itself under the Network node, and other machines on the network could see it too. Rinse and repeat for all machines on the network, and after doing so, each machine could see itself and all others under the Network node of File Explorer. The batch file commands look like this:

net stop "Function Discovery Resource Publication"
net start "Function Discovery Resource Publication"

This worked out really nicely, as the network reset workaround that I used to do required a restart, and changed several network settings I didn't want to change, making more work to set them back. When restarting the "Function Discovery Resource Publication" service, one sees the results right away without needing a restart, and no other changes are made to the network configuration.

jbm417 · 31 Aug 2020

Ken429 - You said it very well. I too have a home network similar to what you describe & what a pain to get all the resources visible after an update. Will try the solution Andyc56 provided.

Ztruker · 01 Sep 2020

This is a batch file I have that I run when one of my systems does not show on my Network.

Code:

Rem From Megabyte Doctor @ tenforums.com
Rem and OldNavyGuy @ tenforums.com
Rem Self elevating code from Matthew Wai @ tenforums.com 
Rem Make computer visible in Network
(Net session >nul 2>&1)&&Goto:✱||Echo CreateObject^("Shell.Application"^). ^
ShellExecute "%~0","✶","","RunAs",1 >"%temp%\(+).vbs"&&"%temp%\(+).vbs"&Exit
:✱
net stop fdPHost /yes
net start FDResPub /yes

fdPHost is Function Discovery Provider Host
FDResPub is the same as Function Discovery Resource Publication that Andy mentioned above.

iamc3k · 06 Feb 2021

Gents,

I have this same issue (some computers on my LAN drop off the Network, seemingly at random, after a few days). Until this thread, I've had to manually "Reset Network", restart the problem machine, and then see if it shows up on the others' Networks.

Of course, this happens to more than just one machine. (I have 4 ethernet-connected PCs and three laptops.)

It seems that RESTARTing fdPHost and FDResPub is my solution.

The batch file that @Ztruker has graciously provided, above, does not work for my situation.
1. It stops one service and then starts the other. (I -think- that the services are linked and this is similar to restarting.)
2. The batch file opens a systems dialogue window that requires I allow the action to be taken by clicking "yes".

Can I just edit the last two lines of the batch file to read:
net restart fdPHost /yes
net restart FDResPub /yes

(I'm a total newb at this, but that seems a logical way to get these services to restart.)

How do I make this batch file something that runs every day, without my intervention? (I'd have to call it with Windows Task Scheduler, but the requirement that I have to respond to "Do you want to allow this app to make changes to your device", makes me think that it cannot run automatically.

Thanks,
Ken