Microsoft KB Archive/276269

{|
 * width="100%"|

XGEN: NSPI Proxy Does Not Take Static Port Mapping If Installed on a Global Catalog

 * }

Q276269

-

The information in this article applies to:


 * Microsoft Exchange 2000 Server

-

SYMPTOMS
After setting static port mappings for the Exchange 2000 Server Information Store, Directory and Name Service Provider Interface (NSPI) Proxy services and restarting the services, you may see that NSPI Proxy has not registered the mapped port. You can verify (by using RPCMon) that NSPI Proxy is still listening on some port in the range from 1024 to 5000 instead of the port mapping that was assigned in the registry.

CAUSE
Exchange 2000 is installed on a Domain Controller acting as a Global Catalog Server. When the System Attendant service starts, and initializes Dsproxy.dll, the DSProxy component checks whether the NSPI is registered locally. If it is, this indicates that this server is a Global Catalog, that the referral and proxy services are not needed, and that the NSPI Proxy does not register itself with the End Point Mapper by using the mapped port registry setting. MAPI clients, however, still access NSPI Proxy during logon and will not be successful if this port is blocked by a firewall or otherwise unavailable.

RESOLUTION
Microsoft has confirmed this to be a problem in Microsoft Exchange 2000 Server.

WORKAROUND
To force the NSPI Proxy service to use the mapped port assignment, follow these steps:


 * 1) Bring up another DC in the Exchange2000 domain.
 * 2) Assign this server the role of Global Catalog Server. In Active Directory Sites and Services Microsoft Management Console (MMC), navigate to Sites\Site-name\Servers\servername\NTDS Settings. Right-click this setting, and then click Properties. On the General tab, click to select the Global Catalog check box to assign the role of Global Catalog to this server.
 * 3) Allow sufficient time to replicate account and schema information to the new Global Catalog Server.
 * 4) Restart this server.
 * 5) In Active Directory Sites and Services, follow the same steps shown in Step 2. This time, click to clear the Global Catalog check box for the Exchange 2000 server.
 * 6) Restart the Exchange 2000 server to reinitialize NSPI Proxy. During startup, an event 9091 will be logged that will indicate that NSPI Proxy has taken the port mapping from the registry.
 * 7) Now DSProxy registers its endpoint with the RPC End-Point-Mapper Manager and initializes its referral and proxy services. From this point on, DSProxy listens to incoming NSPI requests from MAPI clients on the assigned endpoint.

MORE INFORMATION
NSPI Proxy acts as a legacy Exchange Directory for MAPI client access.

For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

"Q256976 XCLN: How MAPI Clients Access Active Directory" For additional information about registry settings, click the article number below to view the article in the Microsoft Knowledge Base:

"Q270836 XCLN: Exchange 2000 Static Port Mappings" Additional query words:

Keywords :

Issue type : kbprb

Technology :