Export (0) Print
Expand All
Expand Minimize

System Attendant NSPI port has been manually overridden

[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at http://go.microsoft.com/fwlink/?linkid=34707.]  

Topic Last Modified: 2007-01-17

The Microsoft® Exchange Server Analyzer Tool reads the following registry entries to determine whether the Name Service Provider Interface target server (NSPI target server) service has been manually overridden:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeSA\Parameters\TCP/IP NSPI Port

If the Exchange Server Analyzer finds TCP/IP NSPI Port to be present and configured, a non-default configuration message is displayed.

The most common reason this value is configured is to enable MAPI clients to connect to an Exchange server that is on the other side of a firewall. This scenario involves opening multiple ports on a firewall to enable Microsoft Office Outlook® 2003 clients to connect using MAPI to an Exchange server, typically over the Internet.

The recommended deployment for using Outlook in Corporate or Workgroup Mode to connect to an Exchange server over the Internet, is to use the remote procedure call (RPC) over HTTP features found in Microsoft Windows Server™ 2003, Exchange Server 2003, Outlook 2003 and Windows® XP Professional.

RPC over HTTP eliminates the need to use a virtual private network (VPN) connection or to open multiple ports on your firewall to allow MAPI access from Outlook 2003 to Exchange Server 2003. A user who runs Outlook 2003 can connect to an Exchange server over the Internet. The RPC client establishes the Internet connection by tunneling the RPC traffic through the HTTP protocol. If the RPC client can make an HTTP/HTTPS connection to a remote computer that is running Internet Information Services (IIS), that RPC client can connect to any server on the remote network. The server on the remote network must be configured to be accessible over the Internet by using RPC over HTTP. Additionally, the RPC client and the RPC server programs can connect across the Internet, even if both programs are behind firewalls that are on different networks.

importantImportant:
This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore the registry if a problem occurs. For information about how to restore the registry, view the "Restore the Registry" Help topic in Regedit.exe or Regedt32.exe.

  1. Open a registry editor, such as Regedit.exe or Regedt32.exe.

  2. Navigate to: HKLM\System\CurrentControlSet\Services\MSExchangeSA\Parameters

  3. Delete the registry value called TCP/IP NSPI Port.

  4. Exit the registry editor and restart Exchange System Attendant Service.

  1. Review "Exchange Server 2003 RPC over HTTP Deployment Scenarios" (http://go.microsoft.com/fwlink/?linkid=47577).

  2. Review the Microsoft Knowledge Base article 833401, "How to configure RPC over HTTP on a single server in Exchange Server 2003" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=833401).

  3. Review the Knowledge Base article 827330, "How to troubleshoot client RPC over HTTP connection issues in Office Outlook 2003" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=827330).

  4. Review the Microsoft Support Web Cast, "Using Microsoft Exchange over the Internet (RPC/HTTP) with Microsoft Office Outlook 2003" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=829134).

Before you edit the registry, and for information about how to edit the registry, see the Microsoft Knowledge Base article 256986, "Description of the Microsoft Windows Registry" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=256986).

For more information about the use of the TCP/IP NSPI Port registry value in a firewall environment, see the Knowledge Base article 270836, "Exchange 2000 and Exchange 2003 Static Port Mappings" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=270836).

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft