XCLN: Resolve_Netbios_Names_Last Registry Entry Does Not Work Correctly (169702)
The information in this article applies to:
- Microsoft Exchange Windows NT client 4.0
- Microsoft Exchange Windows NT client 5.0
- Microsoft Exchange Client 4.0
- Microsoft Exchange Client 5.0
This article was previously published under Q169702
IMPORTANT: This article contains information about editing the registry.
Before you edit the registry, make sure you understand how to restore it if
a problem occurs. For information about how to do this, view the "Restoring
the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key"
Help topic in Regedt32.exe.
SYMPTOMS
Both the Microsoft Exchange Windows 95 client and the Exchange Windows NT
client provide a registry entry called Resolve_Netbios_Names_Last, which
can control the name resolution process. This setting prevents the NETBIOS
name from being sent out first, and allows the Microsoft Exchange Client to
send the Fully Qualified Domain Name (FQDN) of the Microsoft Exchange
Server computer. This registry setting can be used to improve the Exchange
Client startup time. If you use this, in the Client Profile setting, for
server name, you must also enter the FQDN of the Exchange server
(server.domain.com) and NOT the server NETBIOS name.
CAUSE
When the Resolve_Netbios_Names_Last registry key is set to 2 (NETBIOS off),
Microsoft Exchange Client resets it to 0 (NETBIOS first).
STATUS
Microsoft has confirmed this to be a problem in Microsoft Exchange Client
versions 4.0 and 5.0. We are researching this problem and will post new
information here in the Microsoft Knowledge Base as it becomes available.
Modification Type: | Minor | Last Reviewed: | 8/17/2005 |
---|
Keywords: | KB169702 |
---|
|