Hi Matthew,
I think that we need to solve "Directory" disconnected issue firstly. At this time, would you please let me know?
1. Whether all the Outlook Clients encounter the problem?
2. How the Outlook connects to Exchange Server (RPC or RPC over Http)?
3. I suggest you increase MSExchangeSA\NSPI Proxy and MSExchangeSA\RFR Interface to expert:
Set-eventloglevel "MSExchangeSA\NSPI Proxy" "level expert
Set-eventloglevel "MSExchangeSA\RFR Interface" "level expert
Then, please reproduce the issue and check whether any error event can be located in Application log
I would like to explain when creating Outlook Profile, the Outlook Client needs to contact the Exchange Referral component which will redirect the Outlook client to a GC server. From your description, if we fail to create Outlook Profile when typing Exchange Server name and able to create Outlook Profile by using GC server name, the issue mostly occurs because the Outlook fail to contact the Exchange Referral component.
Therefore, please also let me know whether the Outlook connects to Exchange Server directly or through any network device or firewall. In addition, please run rpddump on the Exchange server to check related ports have been listened by Exchange Server:
RPCdump /s <exchange mailbox server>
You should get information like below:
If Outlook connects to Exchange through RPC over TCP:
ncacn_ip_tcp(Connection-oriented TCP/IP)
192.168.1.2[1394] [1544f5e0-613c-11d1-93df-00c04fd7bd09] MS Exchange Directory RFR Interface :NOT_PINGED
192.168.1.2[1416] [f5cc5a18-4264-101a-8c59-08002b2f8426] MS Exchange Directory NSPI Proxy :NOT_PINGED
If Outlook connects to Exchange through RPC over HTTP:
ncacn_http(Connection-oriented TCP/IP using Microsoft Internet Information Server as HTTP proxy.)
192.168.1.2[6002] [1544f5e0-613c-11d1-93df-00c04fd7bd09] MS Exchange Directory RFR Interface :NOT_PINGED
192.168.1.2[6004] [f5cc5a18-4264-101a-8c59-08002b2f8426] MS Exchange Directory NSPI Proxy :NOT_PINGED
Mike Shen
Thanks for this post, Mike.
Some answers to your questions:
All Outlook clients exhibit this behavior
we connect via RPC over TCPIP (we do not use Outlook Anywhere, we use OWA to connect outside the office)
we do not connect through any intermediaries like firewalls or proxy servers; all clients are on the local network
The output of rpcdump looks like this (for the ncacn_tcp_ip section)
ncacn_ip_tcp(Connection-oriented TCP/IP)
10.0.254.19[1025] [906b0ce0-c70b-1067-b317-00dd010662da] :NOT_PINGED
10.0.254.19[1025] [906b0ce0-c70b-1067-b317-00dd010662da] :NOT_PINGED
10.0.254.19[1025] [906b0ce0-c70b-1067-b317-00dd010662da] :NOT_PINGED
10.0.254.19[1025] [906b0ce0-c70b-1067-b317-00dd010662da] :NOT_PINGED
10.0.254.19[1037] [12345678-1234-abcd-ef00-0123456789ab] IPSec Policy agent endpoint :NOT_PINGED
10.0.254.19[1037] [12345778-1234-abcd-ef00-0123456789ac] :NOT_PINGED
10.0.254.19[1059] [b9fadb8d-53a1-41d7-b763-88d884b6b829] Microsoft Exchange Topology Information Server RPC Interface :NOT_PINGED
10.0.254.19[1065] [5261574a-4572-206e-b268-6b199213b4e4] Exchange Server STORE Async EMSMDB Interface :NOT_PINGED
10.0.254.19[1065] [a4f1db00-ca47-1067-b31f-00dd010662da] Exchange Server STORE EMSMDB Interface :NOT_PINGED
10.0.254.19[1065] [a9e05b20-6f57-4e24-a540-52412017e6ff] Microsoft Information Store :NOT_PINGED
10.0.254.19[1065] [0e4a0156-dd5d-11d2-8c2f-00c04fb6bcde] Microsoft Information Store :NOT_PINGED
10.0.254.19[1065] [bf6dd426-77b4-44b3-984e-d413fc075562] Microsoft Information Store :NOT_PINGED
10.0.254.19[1065] [1453c42c-0fa6-11d2-a910-00c04f990f3b] Microsoft Information Store :NOT_PINGED
10.0.254.19[1065] [10f24e8e-0fa6-11d2-a910-00c04f990f3b] Microsoft Information Store :NOT_PINGED
10.0.254.19[1065] [da107c01-2b50-44d7-9d5f-bfd4fd8e95ed] Exchange Server STORE ADMIN Interface :NOT_PINGED
10.0.254.19[1065] [99e64010-b032-11d0-97a4-00c04fd6551d] Exchange Server STORE ADMIN Interface :NOT_PINGED
10.0.254.19[1065] [99e64010-b032-11d0-97a4-00c04fd6551d] Exchange Server STORE ADMIN Interface :NOT_PINGED
10.0.254.19[1065] [89742ace-a9ed-11cf-9c0c-08002be7ae86] Exchange Server STORE ADMIN Interface :NOT_PINGED
10.0.254.19[1065] [a4f1db00-ca47-1067-b31e-00dd010662da] Exchange Server STORE ADMIN Interface :NOT_PINGED
10.0.254.19[1108] [f1f21151-7185-4170-ac8d-9bb077c29bd3] :NOT_PINGED
10.0.254.19[1116] [76c0d124-a18e-49d4-adf1-d8c6ba868ea6] :NOT_PINGED
10.0.254.19[1135] [37fc1b02-da36-4b27-a745-bf2f58a98ff6] :NOT_PINGED
10.0.254.19[1140] [52d3f3f5-248c-4d74-a01f-a06e41d5cd59] :NOT_PINGED
10.0.254.19[1160] [41f5fae1-e0ac-414c-a721-0d287466cb23] :NOT_PINGED
10.0.254.19[1160] [bd5790c9-d855-42b0-990f-3dfed8c184b3] :NOT_PINGED
10.0.254.19[1160] [8384fc47-956a-4d1e-ab2a-1205014f96ec] :NOT_PINGED
10.0.254.19[12634] [1544f5e0-613c-11d1-93df-00c04fd7bd09] MS Exchange Directory RFR Interface :NOT_PINGED
10.0.254.19[12656] [f5cc5a18-4264-101a-8c59-08002b2f8426] MS Exchange Directory NSPI Proxy :NOT_PINGED
10.0.254.19[12634] [3cb4be69-9ba1-448c-9a44-a1f759a1878a] MS Exchange Recipient Update Service RPC Interface :NOT_PINGED
10.0.254.19[12634] [f930c514-1215-11d3-99a5-00a0c9b61b04] MS Exchange System Attendant Cluster Interface :NOT_PINGED
10.0.254.19[12634] [83d72bf0-0d89-11ce-b13f-00aa003bac6c] MS Exchange System Attendant Private Interface :NOT_PINGED
10.0.254.19[12634] [469d6ec0-0d87-11ce-b13f-00aa003bac6c] MS Exchange System Attendant Public Interface :NOT_PINGED
after setting the log level for the MSExchangeSA service, I see several log entries like this:
Event Type: Information
Event Source: MSExchangeSA
Event Category: RFR Interface
Event ID: 9073
Date: 8/4/2009
Time: 9:12:05 AM
User: N/A
Computer: BIZSVSERVER01
Description:
The Directory Service Referral interface (RFRI) received a client request on RPC protocol sequence ncacn_ip_tcp. RFRI is returning the Domain Controller name bizsvserver01.bizspeed.com.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
****************************
It should be noted that the server in this preceding log event (bizsvserver01.bizspeed.com) is our exchange server, not our domain controller.
****************************
and some log errors like this:
Event Type: Error
Event Source: MSExchangeSA
Event Category: RFR Interface
Event ID: 9143
Date: 8/4/2009
Time: 9:10:04 AM
User: N/A
Computer: BIZSVSERVER01
Description:
Referral Interface cannot contact any Global Catalog that supports the NSPI Service. Clients making RFR requests will fail to connect until a Global Catalog becomes available again. After a Domain Controller is promoted to a Global Catalog, it must be rebooted to support MAPI Clients.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
and this:
Event Type: Error
Event Source: MSExchangeSA
Event Category: NSPI Proxy
Event ID: 9057
Date: 8/4/2009
Time: 9:10:04 AM
User: N/A
Computer: BIZSVSERVER01
Description:
NSPI Proxy cannot contact any Global Catalog that supports the NSPI Service. New clients will be refused until a Global Catalog is available. After a Domain Controller is promoted to a Global Catalog, it must be rebooted to support MAPI Clients.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
and some errors like this:
Event Type: Error
Event Source: MSExchangeSA
Event Category: NSPI Proxy
Event ID: 9176
Date: 8/4/2009
Time: 9:05:04 AM
User: N/A
Computer: BIZSVSERVER01
Description:
NSPI Proxy can contact Global Catalog bzspdatldc02.bizspeed.com 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 bzspdatldc02.bizspeed.com as soon as possible.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
We only have one domain controller in the organization, and I'm pretty sure it's the global catalog server.
Thanks,
Matthew