Windows 10: Problems with Networking went away with 20H2

There have a number of people (including myself) that have posted here about problems with home networking. Ever since I first installed Windows 10 back in 2017 I have been having problems.
I have three computers networked together
1. Desktop #1 (wired)
2. Desktop #2 (wired)
3. Laptop (wireless)

Problems included:

1. Computer sometimes could not even ping each other
2. Even when they could ping each other they did not show up in Windows Explorer > Network

Things improved a little in October when Desktop #1 and Laptop were updated to 20H2. Sometimes I had to run "FDResPub.bat" to get the computers to show up in Windows Explorer > Network. Even when that did not work I could use a desktop shortcut such as "\\Darkmatter" to access the other computers.

Things really improved in November when Desktop #2 was updated to 20H2. Now without doing anything all three computers could see each other in Windows Explorer > Network

My question is this. Did 20H2 improve networking or was there some other update that finally fixed networking?

BTW, I will still keep a folder on my desktop with shortcuts to the other computers. I found that even if a computer was asleep clicking on its shortcut would remotely wake it.

:)

 

Network Adapter PROBLEM

Hi,

Thank you for posting in Microsoft Community.

First Verify if the WLAN service is started and set to automatic, if the WLAN service is stopped, I would suggest you to start the service and put it to automatic.

Step 1: Please follow the steps to
start the WLAN service.

• 
  Click on Start, type in services.msc
  and press Enter.
  
• 
  Select WLAN Autoconfig from the list, Right click
  properties.
  
• 
  Change the startup type to Automatic.
  
• 
  Click on Start button.
  
• 
  Click on Apply, Ok.
  

Restart the computer and verify if it works.

Also check if all the dependencies are also running. Try the steps to check Dependencies.

• 
  Right-click on WLAN Autoconfig and select Properties.
  
• 
  Click on Dependencies, you will find all the dependency services under box labeled this service depends on the following system components.
  

Step 2: Run an inbuilt Network troubleshooter.

• 
  Press Windows + X key and select
  Control Panel.
  
• 
  Type troubleshooting and select troubleshooting.
  
• 
  Click on view all on the left pane and select
  Network adapter.
  
• 
  Follow the on-screen steps and check.
  

I would also suggest you to check with the below link to check how to resolve wireless problems.

Refer:
Wired and wireless network problems

Keep us posted to help you better.

 

Windows 10 20H2 network connection

Since upgrading from Windows 2004 to Windows 20H2 cannot connect to our network drives. The computer has a Local account created, and when I map to a network drive I get this error:
Microsoft Windows Network: Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again.
This was never a problem in any previous Windows update - what changed?
We use local user accounts on several 'shared' computers. Normally when a user needs to connect to a network drive on one of these computers they will need to enter their network credentials. Then connection to the network will be made.
Since updating to Windows 10 20H2 this no longer works. Anyone have a fix for this?
Note: I have rolled back to 2004 and network connections work correctly, so this is definitely a 20H2 issue.

 

Network problem

Hi Aslam,

We would like to know more about this concern. Please answer the following questions:

• Are you connecting via wired or wireless?
• What troubleshooting steps have you done?
• Did you make any changes on the computer before you encountered this issue?
• Are you experiencing this issue using a different device?
  

In the meantime, we suggest that you check this
link and follow the steps provided on how to fix network connection issue in Windows 10.

We'll be waiting for your response.