I have been struggling to establish a connection with an SMB share and receiving error messages like “Unexpected Network Error” and “Error 0x80004005”. I have attempted to enable SMBv1 through Windows Features and ensured that sharing is enabled on the network. The server I am trying to connect to is an old Linux-based NAS server, but I do not have more information on it.
Interestingly, I can connect to it using my MBP (macOS Mojave), which is perplexing me.
Can someone guide me on how to connect to this server?
SMB not working Windows 8/10 – Unexpected Network Error 0x80004005
If you’re trying to connect to an SMB share on a Linux-based NAS server and you’re receiving the error “Unexpected Network Error” or “Error 0x80004005”, you’re not alone. This is a common issue that many Windows 8/10 users have encountered. In this post, we’ll explore some of the reasons why this error might be occurring and provide some solutions to help you get connected.
Check Your Network Settings
The first thing you should do when encountering this error is to check your network settings. Make sure that your computer is connected to the same network as the NAS server and that your network settings are configured correctly. You can do this by going to the Control Panel > Network and Sharing Center and checking your network status.
If you’re not sure whether your network settings are correct, try restarting your computer and router. This often resolves connectivity issues and can help you get connected to your NAS server.
Check Your Firewall Settings
Another common reason why you might be receiving this error is because your firewall is blocking the connection. Windows 8/10 has a built-in firewall that can sometimes interfere with network connections. To check your firewall settings, go to the Control Panel > System and Security > Windows Firewall and make sure that file and printer sharing is allowed.
If file and printer sharing is already allowed, try disabling your firewall temporarily to see if this resolves the issue. If it does, you can then re-enable your firewall and create a rule to allow the connection.
Check Your SMB Version
Windows 8/10 uses SMB version 2 by default, which might not be compatible with your NAS server. To resolve this issue, you can try enabling SMB version 1. To do this, go to the Control Panel > Programs and Features > Turn Windows features on or off and check the box next to SMB 1.0/CIFS File Sharing Support.
Note that enabling SMB version 1 can be a security risk, as it is an older protocol that is vulnerable to attacks. If possible, try to upgrade your NAS server to a newer version that supports SMB version 2 or higher.
Check Your NAS Server Settings
It’s also possible that the issue is with your NAS server settings. Make sure that SMB sharing is enabled on your NAS server and that the correct permissions are set for the shared folder. You can usually access your NAS server settings through a web interface or a dedicated software application.
If you’re not sure how to access your NAS server settings, check the documentation that came with your device or contact the manufacturer for assistance.
Try Connecting Using IP Address
If you’re still having trouble connecting to your NAS server, try connecting using its IP address instead of its hostname. Sometimes DNS resolution can be a problem, and using the IP address can help you get connected.
To connect using the IP address, open File Explorer and type \IP_ADDRESS in the address bar, replacing IP_ADDRESS with the actual IP address of your NAS server.
If you’re encountering “Unexpected Network Error” or “Error 0x80004005” when trying to connect to an SMB share on a Linux-based NAS server, there are several things you can try to resolve the issue. Check your network settings, firewall settings, SMB version, NAS server settings, and try connecting using the IP address. With a bit of troubleshooting, you should be able to get connected and access your shared files and folders.
In my case, the solution involved making a change to the registry, which was easy and harmless, and could be undone easily. To do this, open regedit.exe and navigate to
However, it’s important to note that you should back up the entire registry or take a screenshot of the page before making any changes. Change the value of
This may seem counter-intuitive, but it’s correct. In addition, some other systems in our organization also required the following changes: change
1, and add
RequireSecureNegotiate and set it to
After these modifications, everything worked as expected.