Win10 can't connect to Win8.1 but Win8.1 can connect to Win10

So, you entered that other thread on p.18, &, by p.21, it was determined yours is a different problem than the FDResPub fix can solve. IOW, you restarted FDResPub but it wasn't a cure. Also, it happens to you whether the Ethernet or WiFi (two different computers) is used, but the FdResPub cure only applies to the former. Finally, it seems you are saying the Win 10 machines are not spotting the Win 8.1 machines (well they see but can't use them), but it would be the other way around if FDResPub were the problem. The Win 10 machine (using the Ethernet) would be the one that no other computer could spot, & it wouldn't even be able to see itself at the File Explorer Network folder. That's what restarting FdResPub (on the Win 10 machine) would cure.

So I did this BING of "win 8.1 cannot network with win 10"...

https://www.bing.com/search?q=win+8.1+cannot+network+with+win+10&form=WNSGPH&qs=SW&cvid=73b306b2bd7a461ca420f0701aff957d&pq=win+8.1+cannot+network+with+win+10&cc=US&setlang=en-US&nclid=DC7D30674C848AADC8AC41DC57B916B8&ts=1610931599920&wsso=Moderate

It will be very discouraging for you to read the first thread listed which was...

https://social.technet.microsoft.com/Forums/en-US/9d0d20da-b0e9-4c92-aaca-9abcca401679/win-81-cannot-see-win-10-computer-on-workgroup-network-but-the-opposite-works

win 8.1 cannot see win 10 computer on workgroup network but the opposite works

I suggest you skip it & try the next. I'm too discouraged to try more tonight, myself.

You are so pessimistic, I misread your post. But I am glad it is working now. And you've got something to try, if/when it goes again. Keep us informed, & good luck.

>> So you are saying it worked but only temporarily? <<

No, what happened is that Win10, for whatever reason, successfully connected to the Win8.1 computer before I had a chance to try the suggested fix, so, there was no reason to execute the command.

However, I'm sure that I will have another chance to try the fix in the not to distant future ;-)

Thanks,

Beverly

So you are saying it worked but only temporarily? So sorry to hear it. I'm watching the other thread. I'll let fg2001 have the first go at it because I can barely be more than theoretical not having more than this one computer. But, if neither he nor CSAMD show up for you, I will give it a try.

Maybe post pictures at fg2001 to see whether they match precisely to his. I do know he said "no SMB of any type is running", so maybe undo that & state in detail what were the other tweaks you did along the way.

Murphy is hard at work... making sure that no questions get answered.

I finally was able to get to the win10 computer. 

Before I saw your post about the cmd /c net stop FDResPub etc suggestion, I had gone into the Win8.1 computer's network and sharing settings, and turned ON password protected sharing for the public folders but had not had a chance to test that sitting at the win10 box.

When I got your reply, I went back in and turned OFF password protected sharing on the Win8.1 computer before I made the trek up to the Win10 computer, woke it up from sleep and clicked on the Win8.1 computer's shortcut and it connected immediately.

As posted in the other thread, I don't expect this to last.  The varied stories posted seem to indicate that something in the Win10 computer is randomly turning off network access FROM the Win10 computer, then, when any change is made to probably any network settings, that prompts the Win10 computer to gather itself up and set things up correctly until that random event happens again....

In my case, this change, the SMB change, and a couple of other network tweaks that I have attempted have had the same (temporary) result.

Back to square one and waiting... hopefully able to get some work done in the meantime.

ms doesn't care... they are focused only on cloud computing which will eliminate the messy need for computer to computer communications.

Thanks again,

Beverly Howard