Microsoft Knowledge Base Email Alertz

KBAlertz.com: You receive a System error 67 has occurred. The network name cannot be found error message in Windows Server 2003

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]





ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
KBAlertz referrals get
** SIX MONTHS FREE **


Community Site



We Send hundreds of thousands of emails using ASP.NET Email


ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
KBAlertz referrals get
** SIX MONTHS FREE **




Mentioned In








Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks




Article ID: 843156 - Last Review: November 1, 2006 - Revision: 1.2

You receive a "System error 67 has occurred. The network name cannot be found" error message in Windows Server 2003

This article applies to a different version of Windows than the one you are using. Content in this article may not be relevant to you.
Visit the Windows Vista Solution Center

On This Page

SYMPTOMS

If you try to log on to a computer by using your domain account, the domain controller stops responding. Additionally, you cannot access your folder by using the universal naming convention (UNC) network path, and you receive the following error message:
System error 67 has occurred. The network name cannot be found

CAUSE

This issue occurs if one of the following conditions is true:
  • The network components on the domain controller are not configured correctly.
  • You did not update the network drivers on the domain controller or the drivers do not work with Microsoft Windows Server 2003.

RESOLUTION

To resolve this issue use either of the following methods.

Method 1

Update the network adaptor driver on the domain controller.

Note Make sure that you use a network adaptor driver that works with the operating system that you are using.

Method 2

If Network Address Translator (NAT) is installed but is not configured correctly, disable the Internet Protocol (IP) NAT driver, and then restart the computer. To do this, follow these steps:
  1. Click Start, right-click My Computer, and then click Properties.
  2. On the Hardware tab, click Device Manager.
  3. On the View menu, click Show hidden devices.
  4. Expand Non-Plug and Play Drivers, right-click IP Network Address Translator, and then click Disable.
  5. Click Yes two times to restart the computer.

WORKAROUND

To work around this issue, restart the Distributed File System service on the domain controller.

APPLIES TO
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition for the Workstation
  • Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise x64 Edition
Keywords: 
kbtshoot kbprb KB843156
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Be the first to leave feedback, to help others about this knowledge base article.

(Optional) Name

(Optional) Public URL Or Email

Comments
No HTML -- Text Only Please