Windows 10: System error 67 has occurred, The network name cannot be found

​

While attempting to run a Network Discovery scan or when trying to map a network drive from Command Prompt or PowerShell, you may encounter the System error 67 has occurred, The network name cannot be found. In this post, we provide the most suitable solutions to this issue. The most widely known cause of this […]

This article System error 67 has occurred, The network name cannot be found first appeared on TheWindowsClub.com.

read more...

 

Windows PE - System Error 67 | The Network Name Cannot Be Found

Your screenshot clearly shows the error:





You cannot map network shares like that, \\servername\driveletter:. A share must have a name, mapping must be done using share names, so for instance if your drive E: on server DC1 is shared as Deployment, you map it on WinPE as follows:

net use * \\DC1\Deployment





If you shared drive E: using default settings, not renaming it, its share name is E (notice the missing colon after the drive letter). In that case, the net use command should look like this:

net use * \\DC1\E

Just a trivial tip: Instead of a drive letter in net use command, you can use asterisk as in above command samples. It maps a share to a free drive letter at the end of the alphabet, starting from Z.

 

Windows PE - System Error 67 | The Network Name Cannot Be Found

First, let me make sure that I have the scenario correct:

The Windows PE VM is connected to both a bridged virtual network and a host only VM and that VM physically resides on the VM. Do I have that right?

If that is the case, let's simplify things by at least temporarily going into the VM settings and disabling the bridged network. Next, determine the IP address of the host only network on the DC and try to connect to that IP address. If that still does not work, then, on the DC, make sure that file and print sharing is enabled on the host only interface. Finally, if that still is not working, would it be possible for you to temporarily disable the firewall on that host only interface on the DC? Since no one other than the VM has access to it, that should be perfectly safe to do.

If you need more detailed directions on the above steps, do let me know. I don't have a DC setup here so my steps would come from Win 10 which may be a bit different.

Finally, as an aside, what you are doing sounds very much like a really great tutorial available here on TenForums writen by @Kari. If you have not seen this tutorial yet, I highly suggest looking it over. It's exceptionally well done and may spark a few ideas for you. Here is the link to that tutorial:

Create media for automated unattended install of Windows 10

 

Windows PE - System Error 67 | The Network Name Cannot Be Found

Windows Version On Host Machine - 2004

VMWare Network Acronyms

Main Router VM (Bridged & Host-Only Virtual LANs) - PFSense

Domain Controller VM (DC1) [Host-Only LAN] - Windows Server 2016

Windows 10 Imageing Machine (Host-Only LAN) - Win10 VM



Hey everyone! A couple of months ago, as a personal project of mine, I managed to create a Windows Deployment Server virtual machine that could deploy Windows (with Adobe Reader & Notepad++ already installed) on any of my virtual machines that were connected to my virtual network.

Since I really enjoyed that project and the idea of Windows Imaging, a couple of days ago I decided to do another Windows Imaging project, but instead of using WDS, I wanted to try sysprepping an image and than deploying it using ImageX and Windows PE. I managed to sysprep the Windows image and capture the install.wim file on a separate virtual HDD that was on my Windows 10 VM. I than took that same virtual HDD from my W10 VM and attached to my main Domain Controller VM and copied the install.wim file onto a shared folder I have on my DC.

With the .wim file copied to the shared folder, I than booted into WinPE on my WIN10 VM with the intent to map the shared folder and than deploy the install.wim file using ImageX. When I got into WinPE's main screen, I made sure I had a working Internet connection by pinging Google, my virtual router, and my DC by IP Address, which I could do on all three.

I than went to map the shared folder in WinPE by using net use Z: \\dc1"Shared Folder" but I keep getting System Error 67 Has Occurred The Network Name Cannot Be Found. I made sure that the folder was actually shared, which it was. Another weird thing I came across was when I tried pinging my DC by name (ping dc1), I get all four replies, but they're IPv6 replies and not IPv4 replies.

The main issue I'm having is trying to map the network drive to deploy the .wim file

I'm thinking the cause of this issue is a DNS issue, but I'm not exactly sure. If anyone has any advice/tips, that would be fantastic!