Windows 10, Version 1809. Network does not show computers

>> FDResPub <<

The problem seemed to have cured itself, but it's back.

I turned on all of the services listed in the response on the first page of this (very long) thread, but that didn't work.

So, I set up a task scheduler event for FDResPub as suggested in the above post, but, it does not work, including restarting the computer.

fwiw, when I was presented with a login credential screen with my current login as the user, but, when I filled in the password, I received the message that "The specified Account name is not valid"

Turns out that you have to manually add the <computername>&lt;username>

Note

-====================-

I just purchased a second Win10 computer for my wife, and confirmed that the problem is the same with that computer as well.  Again, I can connect to this Win8.1 computer using another Win8.1 computer on the same network.

Help (again)

Beverly Howard

This thread is specifically for windows 10 network, not a mixed of windows 8.1 and Windows 10.

I assume all you PCs are on the same workgroup.

See my first entry on page 18 to setup the FDResPub Restart in Task scheduler.

All the other settings should be just the windows 10 defaults for File sharing on Private network, no need for any special settings.

When you have the problem described in this thread the PC is not visible to itself on the network not just from other PCs. This only affects Ethernet connections, never seen this problem on Wi-Fi.

OK, possibly a clue.

The Win8.1 computer that neither Win10 computer can connect to normal user is a "Non Administrative" user.

I just logged in to the Win8.1 computer using my administrative login, and I was then able to access the Win8.1 computer using both Win10 computers.

The problem is that I need to use the Win8.1 computer not logged in as administrator.

That seems to be at least part of the problem.  Any thoughts or suggestions?

For example should I run FDResPub on the Win8.1 box?

Thanks in advance for any thoughts.

Beverly Howard

>> FDResPub <<

The problem seemed to have cured itself, but it's back.

I turned on all of the services listed in the response on the first page of this (very long) thread, but that didn't work.

So, I set up a task scheduler event for FDResPub as suggested in the above post, but, it does not work, including restarting the computer.

fwiw, when I was presented with a login credential screen with my current login as the user, but, when I filled in the password, I received the message that "The specified Account name is not valid"

Turns out that you have to manually add the <computername>&lt;username>

Note

-====================-

I just purchased a second Win10 computer for my wife, and confirmed that the problem is the same with that computer as well.  Again, I can connect to this Win8.1 computer using another Win8.1 computer on the same network.

Help (again)

Beverly Howard

Great information!

Thanks!

Beverly Howard

>> all running windows 10 Pro <<

That's may be a major factor in why you are not having problems... as posted elsewhere, I have two Win8.1 machines on my network, and the Win10 computer only has problems connecting with one of them... they both have identical setups.

>> there is no way I'll ever use the cloud to transfer or store my files. :-( <<

Same feelings... I'll switch to Linux before I move to the cloud... I was just shining a light on ms' plans and priorities.

Beverly

@BeveHoward, 

F.Y.I.

I recently came across a new bug that has been reported and known by Microsoft where the Credential Manager clears all the Windows credentials after a reboot. No Fix available yet.

Outlook and other apps won't remember password after Windows Updates - Outlook (microsoft.com)

Following the instructions in the link above to workaround this recent bug that showed up with Build 19042.685, I had to retest all the Home Private network issues and verified once again that the specific network problem described in this thread only affects the Ethernet connections, it never happens if I use  Wi-Fi connection on 6 different machines that I have connected on the same network.

Anyway, if I use the Task Scheduler to restart the service FDResPub as described in this thread previously, I have to make sure that the option "Do not store password" is unchecked otherwise it will expose the new bug that clears the credentials after a reboot. This new credentials bug showed up in Dec 2020 after the cumulative updates of Win 10 2004 or 20H2.