Network computers not showing after 20H2 update

All,
There seems to be a problem with the network computers not showing up.
Say my computer is named "BRYCE-PC" and the remote computer is "YuleLog-PC"
I am trying to get psexec to work properly, and worked until today.
I have Spectrum (using their new Wave 2 router and Modem with QR Code) and resetting it shows the computer for a split second, and then disappears.

The above picture shows what it does now.
The below picture shows what I try to do in order to connect.


I have enabled Function Discovery and placed on Autostart, already have everything on except password, and reset modem and router, only to work for a few seconds.

- - - Updated - - -

And also it seems to be RDC is broken too

In my case, updates reset the share settings.
Check that your advanced sharing settings under "All Networks" has the sharing turned on.

Digital Life said:

Try to connect using the computers IP in file Explorer
EG:

Code:

\\192.168.x.x

This will show you all the shared folders on that computer and if you right click on a folder you can select "Map Network Drive"

For some reason Windows prefers the IP compared to the computer name, Probably due too not being able to pick up the IP from your DNS server which is usually your router or not reading the ARP table from itself.

Windows IP Configuration Host Name . . . . . . . . . . . . : Bryce-PC Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : lanEthernet adapter Ethernet: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : lan Description . . . . . . . . . . . : Intel(R) 82579LM Gigabit Network Connection Physical Address. . . . . . . . . : D8-9D-67-95-BA-35 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : YesWireless LAN adapter Local Area Connection* 1: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter Physical Address. . . . . . . . . : 84-3A-4B-1E-9B-5D DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : YesWireless LAN adapter Local Area Connection* 11: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2 Physical Address. . . . . . . . . : 86-3A-4B-1E-9B-5C DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : YesWireless LAN adapter Wi-Fi: Connection-specific DNS Suffix . : lan Description . . . . . . . . . . . : Intel(R) Centrino(R) Advanced-N 6205 Physical Address. . . . . . . . . : 84-3A-4B-1E-9B-5C DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2600:6c60:5d00:4bc4::40ad(Preferred) Lease Obtained. . . . . . . . . . : Monday, October 26, 2020 11:29:48 AM Lease Expires . . . . . . . . . . : Sunday, November 1, 2020 11:57:19 PM IPv6 Address. . . . . . . . . . . : 2600:6c60:5d00:4bc4:a1c0:7ba:e8aa:f12e(Preferred) Temporary IPv6 Address. . . . . . : 2600:6c60:5d00:4bc4:a8cc:cbcf:38fc:f777(Preferred) Link-local IPv6 Address . . . . . : fe80::a1c0:7ba:e8aa:f12e%5(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.1.126(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Monday, October 26, 2020 11:19:39 AM Lease Expires . . . . . . . . . . : Monday, October 26, 2020 2:30:49 PM Default Gateway . . . . . . . . . : fe80::f85b:3bff:fea2:66e9%5 192.168.1.1 DHCP Server . . . . . . . . . . . : 192.168.1.1 DHCPv6 IAID . . . . . . . . . . . : 75774539 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-27-09-8B-D7-D8-9D-67-95-BA-35 DNS Servers . . . . . . . . . . . : 2607:f428:ffff:ffff::2 2607:f428:ffff:ffff::1 192.168.1.1 NetBIOS over Tcpip. . . . . . . . : EnabledEthernet adapter Bluetooth Network Connection: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network) Physical Address. . . . . . . . . : 7C-E9-D3-EB-B7-16 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes

Now says unspecified error when trying to connect


- - - Updated - - -

geobrick said:

In my case, updates reset the share settings.
Check that your advanced sharing settings under "All Networks" has the sharing turned on.

All networks has sharing on.

If it was working pre update and now isn't try Network Reset, Under Networking in settings.Worked for me a while back.

Yep. It seems Sharing is turned on. I'm not sure why updates change that setting in my case. It happens with every major update.

Also, something I've noticed when trying to troubleshoot these kinds of problem is sometimes the changes you make to correct the problem don't have an immediate affect. They take time to propagate through the network or take effect after the PC you changed or other PCs on the network are rebooted. This makes it really hard to know what change actually fixed the problem. One day you'll just start seeing the computer on the network and have no real idea which change actually fixed it. You'll just assume it was the last thing you did. I think this is why there's so much misinformation out there on this subject. Everyone claims the last thing they changed fixed the problem for them.

clam1952 said:

If it was working pre update and now isn't try Network Reset, Under Networking in settings.Worked for me a while back.

Network reset did not help.

- - - Updated - - -

geobrick said:

Yep. It seems Sharing is turned on. I'm not sure why updates change that setting in my case. It happens with every major update.

Also, something I've noticed when trying to troubleshoot these kinds of problem is sometimes the changes you make to correct the problem don't have an immediate affect. They take time to propagate through the network or take effect after the PC you changed or other PCs on the network are rebooted. This makes it really hard to know what change actually fixed the problem. One day you'll just start seeing the computer on the network and have no real idea which change actually fixed it. You'll just assume it was the last thing you did. I think this is why there's so much misinformation out there on this subject. Everyone claims the last thing they changed fixed the problem for them.

Ok.

- - - Updated - - -

I will try to reset the computer and downgrade to 2004. If that works then it seems to be a bug!

f14tomcat said:

Try this this. I had a similar problem.

On all affected machines, set these values in Programs and Features. May need a restart.

Sadly same result.