This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
In Win10, v 1809 I go to "Network" in file explorer and no computers are showing - neither my computer nor other computers on the network.
I was able to find the ip address of the computer I was searching for and successfully ping it via command prompt.
Any ideas?
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.
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.
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. 😆
>> Restarting FDResPub is only a remedy for Win 10 in the case that your own PC is not visible on the network <<
Thanks... I think that removes the problem that I am having from this discussion.
To answer other followups;
all computers and all users have identical network/sharing settings.
the triggers are reboot, and at logon and I have started the service manually to test several times without success.
It's been educational,
bye,
Beverly Howard
True but I'd rather have it the old way, all computers are populated in Windows Explorer Network so I can see who is on or not. \computername doesn't do that all at the same time.
@Garth Clark,
Me too, that is why I use the FDResPub restart workaround in the machines that are affected by this bug.
In 2 years MS never got around to release an official fix. 😜
True but I'd rather have it the old way, all computers are populated in Windows Explorer Network so I can see who is on or not. \computername doesn't do that all at the same time.
