question

DocBoyLLC-6064 avatar image
0 Votes"
DocBoyLLC-6064 asked RobinsonGray-9855 commented

Windows 10 Cumulative April 2021 Update causing all client workstation to not able to access the server.

Clients running Win 10, Server is running Win 2012. On my client workstations today I installed Win 10 April 2021 update (2021-04 Cumulative Update for Windows 10 Version 2004 for x64-based Systems (KB5001330)). After installing the update, the client workstation can no longer connect to the server. I get the Network Error message "Windows cannot access \\Server; Check the spelling of the name. Otherwise, there might be a problem with the network. To try to identify and resolve the network problems, click Diagnose" (Clients still have internet access, Windows network icon on bottom right of screen shows it is still connected properly to the network).

Error code: 0x80070035
Network path was not found

I tried "troubleshooting." Win 10 claims there is issue with DNS Server.

Under Network Icon --> The client can visibly see other workstations, printers, and the server. Clients can access other workstation clients. When clicking on the server icon, the workstation cannot access the server directory.

I tried various regedits on the client workstations, no avail. Huge problem for me as I'm running a patient database that is stored on the server, and the client workstations constantly access the server and the patient database.

After I uninstalled the April 2021 update, everything is working ok again, and the clients can access server contents again.

Anyone run into this issue? Please help.

msc-essentials
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

RobinsonGray-9855 avatar image
0 Votes"
RobinsonGray-9855 answered RobinsonGray-9855 edited

You're not alone. It appears MS may have used this update to disable SMB1, which will cripple communication for a lot of Windows-based software programs.
Changing software data paths to use the server's IPv4 address has a positive impact (e.g. "\\ServerName\Share\DataDir" becomes "\\ServerIP\Share\DataDir").

Edit:
I've been told that re-enabling Multicast Name Resolution in group policy (gpedit.msc) can also reverse this issue without rolling the update back.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

DocBoyLLC-6064 avatar image
0 Votes"
DocBoyLLC-6064 answered RobinsonGray-9855 commented

@RobinsonGray-9855

I went into the Local group policy editor, and set "Turn off multicast name resolution" to "Disabled" (this setting was previously set to "Enabled"). Flushed the DNS and rebooted the workstation, and still did not work.

Any other suggestions?

I am not able to change the software data path. The software I use will only recognize "ServerName" Even though it "sees" the "ServerName" I cannot change the software to recognize the server's IP address instead of its name.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Another possibility would be to add an exception to the hosts file...

  1. Browse to C:\Windows\System32\drivers\etc

  2. Open hosts (no file ext) with Notepad.

  3. Type the server's IP address and name, with a space between (the example in the file shows multiple spaces, but one space is sufficient).
    e.g.
    Server 192.168.1.1

  4. Save.


0 Votes 0 ·