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

Anonymous
2020-11-12T16:34:38+00:00

Frustrating problem on local home network. 

I regularly access multiple computers on the lan remotely, but often my win10 box cannot connect to other non win10 computers even though they can connect to the win10 computer.

I resolved this once, can't remember what I did and now it's back and creating major time wasting.

Win10 wastes even more time by taking almost 5 minutes to timeout before anything else can be done in windows explorer.

Thanks in advance,

Beverly Howard

Windows for home | Windows 10 | Internet and connectivity

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

42 answers

Sort by: Oldest
  1. Anonymous
    2020-11-30T17:17:07+00:00

    That's an excellent thread and, among other things, it better reflects the scope and depth of the problem.  Thanks.

    I have not yet had the time to dig into the suggestions, especially CSAM's but will do so when I can and will report back the results in that thread as well as here.

    Thanks again,

    Beverly Howard

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2020-11-30T19:32:45+00:00

    You are welcome. It's an elegant solution that I expect will work. Looking forward to hearing of it.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2020-12-01T00:31:15+00:00

    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

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2020-12-01T01:01:38+00:00

    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.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2020-12-01T13:59:32+00:00

    >> 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

    Was this answer helpful?

    0 comments No comments