You may receive a “The network name cannot be found” error message when you use the fully qualified domain name to connect to a remote computer from a Windows Server 2003-based, Windows XP-based or Windows 2000-based computer
When you use the net use command on a computer that is running one of the operating systems that is listed in the "Applies to" section to access the shared resources of a remote computer, you may receive the following error message if you use the fully qualified domain name (FQDN) of the remote computer:
System error 67 has occurred
The network name cannot be found
When you use the Open box of the Run dialog box to connect to the remote computer, you may receive the following error message if you use the FQDN of the remote computer:
No network provider accepted the given network path
Note You may be able to ping the remote computer by using the FQDN of the remote computer. No entries may be recorded in the Domain Name System (DNS) cache or in the NetBIOS over TCP/IP (NetBT) cache when you try to connect to the remote computer.
When the name resolution request for FQDN is queued inside NetBT, the request times out, the redirector closes the connection after about eight seconds, and the FQDN name is not resolved. The issue occurs because of contention for the NetBT user mode DNS resolver. This resolver can only resolve names serially.
To resolve this issue, use one of the following methods.
Method 1: Increase the value of the LmhostsTimeout registry entry
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
You can increase the value of the LmhostsTimeout registry entry to increase the timeout interval of NetBT queries to the Lmhosts file and to DNS. You can use this method to give more time for NetBT queries to resolve the FQDN of the remote computer.
To modify the value of the LmhostsTimeout registry entry, follow these steps:
Click Start, click Run, type regedit, and then click OK.
In the left pane, locate and then click the following registry subkey:
Value type: REG_DWORD (Time in milliseconds) Valid range: Decimal: 1000 to 4294967295 (Hexadecimal: 3E8-0xFFFFFFFF) Default: 6000 (6 seconds) Description: This parameter specifies the time-out value for NetBT queries to the Lmhosts file and to DNS. The timer has a granularity of the time-out value. Therefore, the actual time-out could be as much as two times the value.
Technical support for x64-based versions of Microsoft Windows
If your hardware came with a Microsoft Windows x64 edition already installed, your hardware manufacturer provides technical support and assistance for the Windows x64 edition. In this case, your hardware manufacturer provides support because a Windows x64 edition was included with your hardware. Your hardware manufacturer might have customized the Windows x64 edition installation by using unique components. Unique components might include specific device drivers or might include optional settings to maximize the performance of the hardware. Microsoft will provide reasonable-effort assistance if you need technical help with a Windows x64 edition. However, you might have to contact your manufacturer directly. Your manufacturer is best qualified to support the software that your manufacturer installed on the hardware. If you purchased a Windows x64 edition such as a Microsoft Windows Server 2003 x64 edition separately, contact Microsoft for technical support.
For product information about Microsoft Windows XP Professional x64 Edition, visit the following Microsoft Web site:
Microsoft Windows Server 2003, Datacenter Edition (32-bit x86), Microsoft Windows Server 2003, Enterprise Edition (32-bit x86), Microsoft Windows Server 2003, Standard Edition (32-bit x86), Microsoft Windows XP Professional, Microsoft Windows XP Professional 64-Bit Edition (Itanium), Microsoft Windows XP for Itanium-based Systems Version 2003, Microsoft Windows XP Professional x64 Edition, Microsoft Windows 2000 Server, Microsoft Windows 2000 Professional Edition