Article ID: 322834
Article Last Modified on 2/28/2007
APPLIES TO
- Microsoft Exchange 2000 Server Standard Edition
This article was previously published under Q322834
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
SYMPTOMS
When you try to start the System attendant, the following event may be logged in the Application event log:
If you run the "nltest /dsgetsite /force" command, it does not discover the Active Directory site, and generates the following output:
DSGetSiteName failed: Status = 1919 0x77f ERROR_NO_SITENAME
Also, the "nltest /dsgetdc:DomainName /force" command does not discover the domain controller, and generates the following output:
DsGetDcName failed: Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN
NOTE: the Nltest.exe utility is included in the Microsoft Windows 2000 Resource Kit.
CAUSE
This issue may occur when the client computer cannot dynamically discover its site membership. For example, you may see this issue when Active Directory sites have no corresponding subnet mappings.
RESOLUTION
To resolve this issue, associate a subnet with Default-First-Site-Name, and then manually set the site membership. To do so, follow these steps.
Associate a Subnet with Default-First-Site-Name
- Click Start, click Programs, point to Administrative Tools, and then click Active Directory Sites and Services.
- Double-click the Sites node that corresponds to the Site where the Exchange Server resides, and then right-click Subnets.
- Click New Subnet on the shortcut menu.
- Type the IP address, and the subnet mask of the subnet, and then click Default-First-Site-Name on the Site Name list. Click OK to close the New Object-Subnet dialog box.
Set the Site Membership
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
- Start Registry Editor, Regedit.exe.
- Locate and click the following registry key:'
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters
- Double-click the SiteName value, and then type the site name (as it is configured in Active Directory) in the Value Data box.NOTE: If the SiteName value does not exist, follow these steps to create it:
- On the Edit menu, point to New, and then click String Value.
- Type SiteName to change the name of the newly created value, and then press ENTER.
- Double-click the SiteName value, and then type the site name in the Value Data box.
- Quit Registry Editor.
- Restart the computer.
- Start the System attendant service. In Computer Management, double-click Services and Applications, click Services, right-click Microsoft Exchange System Attendant, and then click Start on the shortcut menu.
NOTE: The HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters registry key does not apply to domain controllers. After you manually configure site membership on the member server, the computer may still not be able to receive site-based policies or be able to form a security-enhanced channel with the correct domain controller. If this is the case, use the information from the following Knowledge Base article to correct the problem:
293515 Statically Configured Site Name Value Is Not Enforced
MORE INFORMATION
For additional information about the Nltest.exe utility, click the article number below to view the article in the Microsoft Knowledge Base:
158148 Domain Secure Channel Utility -- Nltest.exe
Keywords: kberrmsg kbprb KB322834
