XADM: Error Message: Network Problems Are Preventing Connection to the Microsoft Exchange Server Computer

Article translations Article translations
Article ID: 280401 - View products that this article applies to.
This article was previously published under Q280401
Expand all | Collapse all

SYMPTOMS

MAPI clients, such as Microsoft Outlook, cannot connect to an Exchange 2000 Server computer after rebuilding the global catalog server. Outlook clients may receive one of the following error messages:
The name could not be resolved. Network problems are preventing connection to the Microsoft Exchange Server Computer. Contact your system administrator if this condition persists.

Unable to expand the folder. The set of folders could not be opened. The information store could not be opened.
You may be able access the mailbox by using Internet Message Access Protocol, version 4rev1 (IMAP4) and Post Office Protocol version 3 (POP3).

In the application log of Exchange 2000 Server, the following event may be logged:
Event Type: Error
Event Source: MSExchangeSA
Event Category: (11)
Event ID: 9176
Date: 9/30/2000
Time: 9:58:21 AM
User: N/A
Computer: EXCHANGESRVR

Description: NSPI Proxy can contact Global Catalog GCName but it does not support the NSPI service. After a Domain Controller is promoted to a Global Catalog, the Global Catalog must be rebooted to support MAPI Clients. Reboot GCName as soon as possible.

For more information, click http://search.support.microsoft.com/search/?adv=1.
If you restart the global catalog server, this does not fix this problem. Outlook 2000-and-later clients that connected before the problem occurred can still connect. However, new client connection attempts are not successful. This behavior occurs because of the cached value generated by the smart client feature and directory service referrals (RFR interface).

CAUSE

This issue occurs because the Name Service Provider Interface (NSPI) is not advertised by the global catalog server.

RESOLUTION

This problem is fixed in Windows 2000 Service Pack 3 (SP3).

WORKAROUND

To work around this problem, demote the domain controller from global catalog server status, restart the global catalog server, and then promote the domain controller to a global catalog server again.

NOTE: For information about promoting a Windows 2000 domain controller to global catalog server, see Online Help for Windows 2000 Server.

After the domain controller reports that it is successfully advertising as a global catalog server again (by logging Event ID 1119 in the Directory Service event log), restart the server to advertise the NSP interface.

Stop and then restart the Exchange services, or restart the Exchange Server computer. Exchange Server should now be able to contact the global catalog server.

MORE INFORMATION

For additional information about directory service referrals, click the article numbers below to view the articles in the Microsoft Knowledge Base:
256976 XCLN: How MAPI Clients Access Active Directory
302914 XCCC: How Outlook 2000 Accesses Active Directory
For additional information about Exchange 2000 considerations when you promote a Windows 2000 domain controller to a global catalog server, and about how to use the global catalog Partition Occupancy registry value to direct the global catalog promotion process to complete the full replication of all naming contexts before advertising itself, click the article number below to view the article in the Microsoft Knowledge Base:
304403 XADM: Exchange Considerations for Promoting a Domain Controller to a Global Catalog Server

Properties

Article ID: 280401 - Last Review: February 27, 2007 - Revision: 2.2
APPLIES TO
  • Microsoft Exchange 2000 Server Standard Edition
Keywords: 
kberrmsg kbprb KB280401

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com