I'm facing a frustrating issue with a file share on our Windows Server 2022. We have a Windows 11 machine running the 22H2 update, and for some users, accessing the file share becomes hit or miss. After the update, things calmed down a bit, but one user still encounters problems daily. The main error is: "Windows cannot access \\server1\share1. Check the spelling of the name. Otherwise, there might be a problem with your network. Error code: 0x80070035 - The network path was not found." Interestingly, shares \\server1\share2 and \\server1\share3 work fine. After rebooting the client, \\server1\share1 is accessible again. Permissions are set correctly for the folder, and we've tried toggling sharing off and on. The problems seem to mainly crop up in the morning, and the Event Viewer hasn't revealed any obvious issues.
5 Answers
Make sure to check your SMB logs in the Event Viewer under Applications & Services > Microsoft > Windows (SMBserver/SMBClient) on both the server and client. They can provide clues to what's causing these errors.
How exactly are you accessing your drives? If you're not mapping them, just typing the path will work but can sometimes be finicky.
Since you're on a wired connection, ensure there are no pinched cables or other physical network issues. Check your connections.
If you’re using Group Policy to map drives, double-check that they're set to 'update' instead of 'replace' or 'create'. That might help with persistence issues.
It might be worth looking into DNS issues. Make sure your clients aren't picking up incorrect DNS settings from DHCP or that there are no old demoted domain controllers messing things up.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures