Windows 10, Version 1809. Network does not show computers

I have seen those 'old style' USB-A to Ethernet adapters, but I don't fancy any extra device hanging on PC's. There is already all kind of things attached to desktops and I would like to keep laptop as 'free' as possible: With wireless mouse only power supply is connected.

At work I have USB-C doc so which make it easy to take that laptop (that's also Dell) to carry if when needed. Extra power and mouse (can't use AutoCAD with touch pad) are always on backpack.

This USB-A to USB-C adapter may have usable some times and it's not so expensive. 

Hi Pauli, 

Another interesting detail about those Anker USB Ethernet adapters that I showed on page 20.

The newer one with USB-C and the older one with USB-A connector use the same Realtek Driver and the most recent one is 10.43.20.1029 dated 10/29/2020.

Yet the behavior is different when I test them in the same machine Dell XPS 8700 and the same USB-3.0 port, same results on the Lenovo Yoga 920 Laptop.

I ended up doing the same test on 3 more machines and got the same results:

The newer one with USB-C connector (which also has the USB 3 hub) never fails to show the computer in the Network, while the older style with the USB-A connector fails to show the computer exactly the same way as the Internal Ethernet adapter and have to use the FDResPub restart workaround.

Apparently the timing on the 2 adapters is different enough to cause the bug to show up solid on one, but not the other.  😆

It is really obvious what the issue is that FD starts before the network is ready. This is why turning on Remote desktop works because that happens before FD and waits for the network to be ready. Also the Task workaround makes sure the network is ready.

Not sure why MS won't fix it. Seems like an easy fix.

Quite frankly, I don't know why the let it break to begin with.

Thanks for your interest.

Some more info on why my win10 can't see w8.1 computers. I have not had the need recently to access a win8.1 computer from this win10 computer, and, sure enough, could not do so when I needed to today.

Went to the win8.1 computer and it had no problem accessing the win10 computer and, after doing so, went back to the win10 computer and confirmed that it could still not access the win8.1 computer

Stopped the FDResPub service (it was running) and re started it.  Didn't help.

Then;

• went to the win8.1 computer
• restarted it
• logged in as administrator
• then immediately logged out
• then logged in as the non-admin user which is the norm for this computer
• went to the win10 computer
• was able to access the win8.1 computer

It did take a while for win10 file explorer to display the win8.1 icon, and it balked when I first tried to open the share, but eventually it connected and allowed me to access and transfer win8.1 files.

In other words, a win8.1 administrative login is required before any win10 computer can access that box.

Hope this info is helpful,

Beverly Howard

In other words, a win8.1 administrative login is required before any win10 computer can access that box.

Hope this info is helpful,

Beverly Howard

@BaveHoward,

Unfortunately I don't have any win 8.1  left on my network to verify the case you are describing.

You should open a separate thread and topic for that specific case.

With Windows 10 I don't have any problem accessing another computer even if it is logged in as a standard user without Administrator privileges. 

This thread is dealing with a specific windows 10 problem on publishing the name of the computer on the network due to FDResPub service starting up before the Ethernet adapter is ready, when the problem occurs the Win 10 computer simply does not show up in the network.