Using the same name for your server cluster and for your Exchange Virtual Server may prevent some services from starting in Windows 2000 (887416)

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 restart a Microsoft Windows 2000 Advanced Server-based server cluster, you may receive the following error message:

The workstation service terminated with service specific error 2250

Additionally, you may receive events in the System log that are similar to the following event messages:

Event ID: 7024
Source: Service Control Manager
Description :

The workstation service terminated with a service-specific error 2250

Event ID: 7001
Source: Service Control Manager
Description:

The Net Logon service depends on the workstation service which failed to start because of the following error: The service has returned a service-specific error code. Cluster services fail to start.

Event ID: 2505
Source: Server
Description:

The server could not bind to the transport because another computer on the network has the same name. The server could not start.

CAUSE

This issue may occur if the Windows 2000-based server cluster has an Exchange Virtual Server that is configured with the same name that is used for the server cluster. To use the ISINTEG utility on the Exchange 2000 server, you must specify the Exchange Virtual Server name in the User Environment Variables list of the server cluster.

If you add the Exchange Virtual Server name in the System Environment Variables list instead of adding the name in the User Environment Variables list, and you then restart the server cluster, the following issues may occur:

Some of the operating system files on the server cluster will point to the name of the Exchange Virtual Server instead of pointing to the name of the computer.
Some of the services that depend on these operating system files may not start correctly. These services are the Workstation service and all its dependent services. The dependent services include the Cluster service and the Net Logon service.

RESOLUTION

To resolve this issue, follow these steps:

Delete the following variable from the System Environment Variables list:
_CLUSTER_NETWORK_NAME

To do this, follow these steps:
1. Click Start, click Run, type control.exe in the Open box, and then click OK.
2. In Control Panel, double-click System.
3. Click the Advanced tab, and then click Environment Variables.
4. In the System variables list, locate and then click _CLUSTER_NETWORK_NAME, and then click Delete.
5. Click OK to close the Environment Variables dialog box.
6. Click OK to close the System Properties dialog box.
Locate and then click the following registry subkey:
HKEY_CURRENT_USER\Software\Microsoft\Windows\ShellNoRoam
Locate and then remove the registry entry in this subkey that has the computer name. To do this, follow these steps:

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.
1. Click Start, click Run, type regedit in the Open box, and then click OK.
2. In Registry Editor, locate and then click the following registry subkey:
  HKEY_CURRENT_USER\Software\Microsoft\Windows\ShellNoRoam
3. In the details pane, locate and then right-click the registry entry with the computer name. Then click Delete.
4. Quit Registry Editor.
5. Restart your computer.