Share this article
Improve this guide
System error 67 has occured? Fix it in 5 easy steps
3 min. read
Updated onOctober 4, 2023
updated onOctober 4, 2023
Share this article
Improve this guide
Read our disclosure page to find out how can you help Windows Report sustain the editorial teamRead more
Key notes
System error 67 is aWindows Serverissue that can occur when users try to map a network drive. Theerror messagestates:System error 67 has occurred.
The network name cannot be found. Consequently, users can’t map their network drives whenCommand Promptdisplays thaterror message.
If you need to fix that issue, check out some of these potential resolutions.
How can I fix the System error 67 on Windows 10?
1. Update the network adapter driver for the domain controller
Updating the network adapter driver on the domain controller server might fix the System error 67 that you are dealing with. That’s why this is our first recommendation for you today.
You can update your drivers by accessing the Device Manager panel from the taskbar. Find the network adapter in the list of hardware, right-click on the driver and select update.
Alternatively, in order to quickly update the network adapter driver for the domain controller, don’t hesitate to use Outbyte Driver Updater.
This tool will literally solve the problem for you by scanning thecomputerfor missing and outdated device drivers.
Once they are identified, choose only the adapter driver to update or download and install all of your out-of-date device drivers at once.
It’s convenient that you can always see the download progress of each of your files, not to mention that you can easily schedule driver scans.
Outbyte Driver Updater
2. Check the command’s syntax
System error 67 can often be due to a syntax error within the net map command. So, double-check you’ve entered the net map command right.
Check whether you’ve entered the slashes for the command right. The basic syntax for the net map command is:net use * IP Addresssharename.
So, there should be backslashes, not forward slashes, around the command’sIP address.
3. Disable the Network Address Translator
4. Turn on Desktop Experience
Some users have also confirmed they’ve fixed System error 67 by enablingDesktop Experiencein Windows Server. You may try the same by applying the above steps.
5. Turn off the Hardened UNC Paths policy
The resolutions above will probably fix System error 67 for most users. With that issue fixed, users can then map network drives and run Network Discover scans as required.
More about the topics:System Errors
Matthew Adams
Windows Hardware Expert
Matthew is a freelancer who has produced a variety of articles on various topics related to technology. His main focus is the Windows OS and all the things surrounding it.
He is passionate about the tech world, always staying up-to-date with the latest and greatest. With an analytical view, he likes problem-solving, focusing on errors and their causes.
In his free time, he likes to read and write about history and tries to always develop new skills.
User forum
0 messages
Sort by:LatestOldestMost Votes
Comment*
Name*
Email*
Commenting as.Not you?
Save information for future comments
Comment
Δ
Matthew Adams
Windows Hardware Expert
He is passionate about everything surrounding Microsoft’s OS, focusing on troubleshooting guides & tips for everyday problems.