Error 67

“System error 67 has occurred. The network name cannot be found”. Does this sound familiar? Let’s take a quick look at error 67 and find out what’s going on and how to work around the issue.

Error 67 can happen both under Windows Server 2003 and under Windows NT.

Windows Server 2003 Error 67:

This error typically occurs when you attempt to log on to a computer with your domain account and the domain controller stops responding. In addition, you find that you can no longer access your folder with the universal naming convention network path.

According to Microsoft, this can happen for one of two reasons. It could be because the network components on the domain controller are configured improperly or it could be because the network drivers are out of date on the domain controller or don’t function with Windows Server 2003.

The following advice applies to:

·          Microsoft Windows Server 2003, 64-Bit Datacenter Edition

·          Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)

·          Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)

·          Microsoft Windows Server 2003, Enterprise x64 Edition

·          Microsoft Windows Server 2003, Standard Edition (32-bit x86)

·          Microsoft Windows XP Professional for Itanium-based systems

To resolve your error 67 issues try updating the adaptor driver on the domain controller making sure to use the correct network adaptor driver for the operating system that you have.

If you have the Network Address Translator installed but find that it is not configured properly, you can disable the Internet Protocol Network Address Translator driver and reboot the computer. Follow these steps to do this:

·          Click on the Start button, right-click on My Computer, and then choose Properties from the list

·          Find the Hardware tab and click on Device Manager

·          Find the View menu and click on Show hidden devices.

·          Next, expand Non-Plug and Play Drivers and right-click on IP Network Address Translator

·          Click Disable

·          Choose Yes twice to reboot the PC

You can also try to solve your error 67 problem by restarting the Distributed File System service on the domain controller.

Windows NT Error 67:

Another error 67 issue revolves around Inaccessible Roaming Profiles. The following information relates to:

•          Microsoft Windows NT Server 4.0 Standard Edition

•          Microsoft Windows NT Server 4.0, Terminal Server Edition

•          Microsoft Windows NT Workstation 4.0 Developer Edition

Sometimes when you log onto a PC running Windows NT Workstation 4.0 or Windows NT Server 4.0 in a domain with roaming profiles configured, you will see the following error 67:

•          “Your roaming profile is not available, the operating system is attempting to log you on with your local profile. Error 67”

•          “The update of your roaming profile failed. Please contact your NetworkAdministrator. Error 67”

In addition if you look in the Event Viewer Application Log on the client computer, you may find the following event:

“Event ID: 1000   Source:   Userenv   Description: Your roaming profile is not available, the operating system is attempting to log you on with your local profile. Error 67.”

You might see this under the description instead:

“You do not have permission to access your central profile located at:

 \\Server\Share\%UserName%.

The operating system is attempting to log you on with your local profile. Please contact you Network Administrator.”

The underlying cause of error 67 is essentially that the network name is unable to be found. One common reason is when the syntax in the profile path is wrong.

To fix this, verify that the profile path listed correctly matches the share’s location and directory name where the profile is actually stored.

Solving error 67 problems depend on the operating system in use of the network. By double checking your drivers and the syntax of the profile path, you should be able to connect to the network once again without the error 67 problems.