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

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

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

@BaveHoward,

I don't have any Win8.1 left on my network anymore, but I thought 8.1 was still using HomeGroup which is no longer used in windows 10.

The FDResPub restart only helps the case where the PC is not visible to itself and not just to other machines in the network. It simply does not publish the name when it fails, the workaround only applies to windows 10.

If the PC is visible to itself but not to other PCs on the network, you are looking to a completely different issue.

Another workaround that fixed the problem described in this thread for Win 10 is just enabling Remote Desktop, in that case there is no need of restarting FDResPub with Task Scheduler.

B.T.W. You can restart FDResPub manually in the Services if you just want to test.

>> Win10/Win8.1 <<

This is specifically a Windows 10 problem... it is not a windows "other than10" problem because other computers on the same lan running different versions of windows have no problems connecting with each other.

In fact, the non Win8.1 computers have no problem connecting with the Win10 computers, it's the Win10 computers that cannot connect to the Win8.1 computers.

>> Ethernet <<

My problems today confirm that this is not a "cable ethernet" problem as I have confirmed the problem to be the same with both the original Win10 computer which is connected via cable and the new Win10 computer which has the identical problem is connected via wifi.

>> FDResPub <<

I appreciate your info on the FDFResPub

It took me a while, but as posted, I was able to get the FDResPub task scheduled (and run it) on the original Win10 machine, but, it did not work to allow connecting to a share... I was still unable to connect to the Win8.1 machine even after rebooting the Win10 machine.

It's not clear if you are telling me to do create the same FDResPub task on the Win8.1 machine.

>> Bottom Line <<

There is still a problem with Win10 connecting to other shares on the LAN.  It seems to be related to the rights of the current user logged into the Win8.1 machine.

Thanks again for your info,

Beverly Howard