Sign in
 
Exchange Server TechCenter > Exchange Server Forums > Secure Messaging > RPC over HTTPS
Ask a questionAsk a question
Search Forums:
 

AnswerRPC over HTTPS

  • Monday, August 31, 2009 7:43 PMMTLER1 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    RPC over HTTPS is not working. My setup is a s follows: ISA ver 2006 in DMZ, one Exchange 2003 back end server and one Exchange 2003 front end server, both version 6.5 (build 7638.2 Service Pack 2. I believe RPC over HTTPS works internally since when I run outlook.exe /rpcdiag, it shows https protocol rather than TCP at least for most of the items displayed there. Also, OWA and active sync for Mobile phones work fine externally. I think there is something missing/misconfigured on the ISA server but I'm not sure what.
    Thank you.
     

Answers

  • Monday, September 14, 2009 11:55 AMMike ShenMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote

    Hi,

     

    Thanks for your response.

     

    1. Please run rpcdump /I >c:\dump.txt on the Backend server and post result here.

    2. Please understand that the RPC over HTTP is not able to work with 2000 GC servers. We need to upgrade to Windows Server 2003 GCs to have RPC over HTTP work.

     

    For your reference:

     

    System Requirements for RPC over HTTP on Exchange Server 2003

    http://technet.microsoft.com/hi-in/library/aa998943(en-us,EXCHG.65).aspx

     

    To use RPC over HTTP, you must run Microsoft® Windows Server™ 2003 on the following computers:

     

    1. All Exchange Server 2003 servers that Microsoft Office Outlook® 2003 clients will access using RPC over HTTP, such as mailbox servers and public folder servers.

    2. All Exchange Server 2003 front-end servers that act as RPC proxy servers.

    3. All global catalog servers that Outlook 2003 clients and Exchange Server 2003 servers (that are configured to use RPC over HTTP) use.

     

    Mike Shen

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfb@microsoft.com  

     

     
  • Tuesday, September 22, 2009 7:08 AMMike ShenMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    Hi,

    Any update regarding the issue?

    Whether the Outlook is able to connects to Exchange through Https in internal network after upgrading GC to 2003?

    Thanks,
    Mike
    • Marked As Answer byMTLER1 Monday, September 28, 2009 3:14 PM
    •  
     

All Replies

  • Tuesday, September 01, 2009 9:53 AMMike ShenMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Hi,

     

    Firstly, I would like to double confirm whether the Outlook is able to connect to Exchange through RPC over HTTPs in internal network environment.

     

    Note: Please ensure both Mail and Directory connections are HTTPs and the Status is established.

     

    If we can ensure the Outlook is able to connect to Exchange through RPC over HTTPs in internal network, I agree with you that the issue may relate to incorrect ISA configuration. I suggest you refer to following two articles regarding the ISA configuration:

     

    How to configure ISA Server 2006, ISA Server 2004, or Microsoft Forefront Threat Management Gateway, Medium Business Edition, to allow for RPC over HTTP client connections from Outlook 2003 to Exchange Server 2003

    http://support.microsoft.com/kb/884506/en-us

     

    Publishing Exchange Server 2003 with ISA Server 2006

    http://technet.microsoft.com/en-us/library/bb794845.aspx

     

    If the above articles cannot help you solve the issue, I also suggest you post your question on ISA forum regarding the issue:

     

    http://social.technet.microsoft.com/Forums/en-US/category/forefrontedgesecurity

     

    Mike Shen

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfb@microsoft.com  

     

     
  • Friday, September 04, 2009 5:26 AMMike ShenMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hi,

    Any update regarding the issue?

    Thanks,
    Mike
     
  • Thursday, September 10, 2009 3:53 PMMTLER1 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Mike,
    For some reason I haven't been receiving any e-mail notifications about new updates. I just logged in and see you response. Let me go over your suggestions and I'll reply back by end of the day.
    Thank you!
     
  • Thursday, September 10, 2009 8:50 PMMTLER1 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Ok, I tried RPC over HTTPs internally and Mail connection is HTTPs however Directory - TCP/IP. What do you think I need to do to make Directory use HTTPs?

    Thank you.

     
  • Friday, September 11, 2009 5:56 AMMike ShenMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Hi,

     

    Thanks for your response.

     

    I suggest you check following configuration:

     

    1. On the Exchange 2003 Front End Server, please check whether following registry is configured correctly:



    You should have value like below:

    HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\RpcProxy\ValidPorts

     

     

    mbx:6001-6002;mbx:6004;mbx.contoso.com:6001-6002;mbx.contoso.com:6004

     

    Note: The mbx is your Backend Server netbios name.

     

    2. Please let me know whether the backend server is installed on GC server. If yes, please adding related registry key refer to following article

     

    How to Set the NTDS Port on a Global Catalog Server Acting as an Exchange Server 2003 Back-End Server

    http://technet.microsoft.com/hi-in/library/bb124159(en-us,EXCHG.65).aspx

     

    3. Run RPCDump tool on the Exchange backend server, please check whether the 6002 and 6004 port is listened. You should get following entry under ncacn_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

     

    4. Please let me know whether there is Windows 2000 GC servers in the environment

    5. Please use RPCPing tool to check the Directory connection. I suggest you run RPCPing tool on the Front End Server directly in order to bypass firewall or proxy server.

     

    rpcping -t ncacn_http -o RpcProxy=FE.contoso.com -P "user,domain,password" -H 1 -F 3 -a connect -u 10 -v 3 -s BE.contoso.com -I " user,domain,password " -e 6004

    rpcping -t ncacn_http -o RpcProxy=FE.contoso.com -P "user,domain,password" -H 1 -F 3 -a connect -u 10 -v 3 -s BE.contoso.com -I " user,domain,password " -e 6002

     

    Regarding RPCPing tool:

     

    How to use the RPC Ping utility to troubleshoot connectivity issues with the Exchange over the Internet feature in Outlook 2007 and in Outlook 2003

    http://support.microsoft.com/kb/831051/en-us

     

    For more information regarding RPC over HTTP configuration, you can refer to following article:

     

    How to Deploy RPC over HTTP for the First Time on Exchange Server 2003, Front-End/Back-End Scenario, Back End on Global Catalog Server

    http://technet.microsoft.com/hi-in/library/bb124796(en-us,EXCHG.65).aspx

     

    Mike Shen

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfb@microsoft.com  

     

     
  • Friday, September 11, 2009 4:26 PMMTLER1 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    the registry didn't have mbx:6004 so I added it and rebooted the box. Still same issue. The BE server is not AD server therefore it is not GC server. Run rpcdump /p ncacn_http /v on the BE:
    Querying Endpoint Mapper Database...
    0 registered endpoints found.
    rpcdump completed sucessfully after 1 seconds

    Run on FE:
    rpcping -t ncacn_http -o RpcProxy=FE.contoso.com -P "user,domain,password" -H 1 -F 3 -a connect -u 10 -v 3 -s BE.contoso.com -I " user,domain,password " -e 6004

    RPCPing v2.12. Copyright (C) Microsoft Corporation, 2002
    OS Version is: 5.2, Service Pack 2

    Exception 1722 (0x000006BA)
    Number of records is: 3
    ProcessID is 2796
    System Time is: 9/11/2009 16:14:13:765
    Generating component is 13
    Status is 1722
    Detection location is 1352
    Flags is 0
    NumberOfParameters is 1
    Long val: -1073606646
    ProcessID is 2796
    System Time is: 9/11/2009 16:14:13:765
    Generating component is 14
    Status is -1073606646
    Detection location is 1380
    Flags is 0
    NumberOfParameters is 2
    Long val: 12175
    Unicode string: /rpc/rpcproxy.dll?mtlmail02.mtl.corp:6004
    ProcessID is 2796
    System Time is: 9/11/2009 16:14:13:765
    Generating component is 14
    Status is 65536
    Detection location is 1385
    Flags is 0
    NumberOfParameters is 1
    Long val: 16

    Run on FE:
    rpcping -t ncacn_http -o RpcProxy=FE.contoso.com -P "user,domain,password" -H 1 -F 3 -a connect -u 10 -v 3 -s BE.contoso.com -I " user,domain,password " -e 6002
    RPCPing v2.12. Copyright (C) Microsoft Corporation, 2002
    OS Version is: 5.2, Service Pack 2

    Exception 1722 (0x000006BA)
    Number of records is: 3
    ProcessID is 4092
    System Time is: 9/11/2009 16:23:45:484
    Generating component is 13
    Status is 1722
    Detection location is 1352
    Flags is 0
    NumberOfParameters is 1
    Long val: -1073606646
    ProcessID is 4092
    System Time is: 9/11/2009 16:23:45:484
    Generating component is 14
    Status is -1073606646
    Detection location is 1380
    Flags is 0
    NumberOfParameters is 2
    Long val: 12175
    Unicode string: /rpc/rpcproxy.dll?mtlmail02.mtl.corp:6002
    ProcessID is 4092
    System Time is: 9/11/2009 16:23:45:484
    Generating component is 14
    Status is 65536
    Detection location is 1385
    Flags is 0
    NumberOfParameters is 1
    Long val: 16

    I have 2 Windows 2000 Domain Controllers and both are GCs.

    Thank you.

     
  • Monday, September 14, 2009 11:55 AMMike ShenMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote

    Hi,

     

    Thanks for your response.

     

    1. Please run rpcdump /I >c:\dump.txt on the Backend server and post result here.

    2. Please understand that the RPC over HTTP is not able to work with 2000 GC servers. We need to upgrade to Windows Server 2003 GCs to have RPC over HTTP work.

     

    For your reference:

     

    System Requirements for RPC over HTTP on Exchange Server 2003

    http://technet.microsoft.com/hi-in/library/aa998943(en-us,EXCHG.65).aspx

     

    To use RPC over HTTP, you must run Microsoft® Windows Server™ 2003 on the following computers:

     

    1. All Exchange Server 2003 servers that Microsoft Office Outlook® 2003 clients will access using RPC over HTTP, such as mailbox servers and public folder servers.

    2. All Exchange Server 2003 front-end servers that act as RPC proxy servers.

    3. All global catalog servers that Outlook 2003 clients and Exchange Server 2003 servers (that are configured to use RPC over HTTP) use.

     

    Mike Shen

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfb@microsoft.com  

     

     
  • Monday, September 14, 2009 3:19 PMMTLER1 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Mike,
    Thank you for your response. Here's the rpcdump /I result:
    ___________________________________________________
    Querying Endpoint Mapper Database...

    172 registered endpoints found.


    Collecting Data....  This may take a while.

              0    10   20   30   40   50   60   70   80   90  100
              |----|----|----|----|----|----|----|----|----|----|
              ...................................................

     

    ncacn_http(Connection-oriented TCP/IP using Microsoft Internet Information Server as HTTP proxy.)

      172.16.1.30[6002] [1544f5e0-613c-11d1-93df-00c04fd7bd09] MS Exchange Directory RFR Interface :NO

      172.16.1.30[6002] [f930c514-1215-11d3-99a5-00a0c9b61b04] MS Exchange System Attendant Cluster Interface :UNKNOWN

      172.16.1.30[6002] [83d72bf0-0d89-11ce-b13f-00aa003bac6c] MS Exchange System Attendant Private Interface :UNKNOWN

      172.16.1.30[6002] [469d6ec0-0d87-11ce-b13f-00aa003bac6c] MS Exchange System Attendant Public Interface :UNKNOWN

      172.16.1.30[6004] [f5cc5a18-4264-101a-8c59-08002b2f8426] MS Exchange Directory NSPI Proxy :NO

      172.16.1.30[6001] [a4f1db00-ca47-1067-b31f-00dd010662da] Exchange 2003 Server STORE EMSMDB Interface :NO

      172.16.1.30[6001] [99e64010-b032-11d0-97a4-00c04fd6551d] Exchange Server STORE ADMIN Interface :UNKNOWN

      172.16.1.30[6001] [99e64010-b032-11d0-97a4-00c04fd6551d] Exchange Server STORE ADMIN Interface :UNKNOWN

      172.16.1.30[6001] [89742ace-a9ed-11cf-9c0c-08002be7ae86] Exchange Server STORE ADMIN Interface :UNKNOWN

      172.16.1.30[6001] [a4f1db00-ca47-1067-b31e-00dd010662da] Exchange Server STORE ADMIN Interface :UNKNOWN

     

    ncadg_ip_udp(Datagram (connectionless) UDP/IP)

      172.16.1.30[1067] [bfa951d1-2f0e-11d3-bfd1-00c04fa3490a]  :YES

      172.16.1.30[1085] [1544f5e0-613c-11d1-93df-00c04fd7bd09] MS Exchange Directory RFR Interface :YES

      172.16.1.30[1085] [f930c514-1215-11d3-99a5-00a0c9b61b04] MS Exchange System Attendant Cluster Interface :YES

      172.16.1.30[1085] [83d72bf0-0d89-11ce-b13f-00aa003bac6c] MS Exchange System Attendant Private Interface :YES

      172.16.1.30[1085] [469d6ec0-0d87-11ce-b13f-00aa003bac6c] MS Exchange System Attendant Public Interface :YES

      172.16.1.30[1144] [38a94e72-a9bc-11d2-8faf-00c04fa378ff] MS Exchange MTA 'QAdmin' Interface :YES

      172.16.1.30[1144] [9e8ee830-4459-11ce-979b-00aa005ffebe] MS Exchange MTA 'Mta' Interface :YES

      172.16.1.30[1146] [a4f1db00-ca47-1067-b31f-00dd010662da] Exchange 2003 Server STORE EMSMDB Interface :YES

      172.16.1.30[1146] [99e64010-b032-11d0-97a4-00c04fd6551d] Exchange Server STORE ADMIN Interface :YES

      172.16.1.30[1146] [99e64010-b032-11d0-97a4-00c04fd6551d] Exchange Server STORE ADMIN Interface :YES

      172.16.1.30[1146] [89742ace-a9ed-11cf-9c0c-08002be7ae86] Exchange Server STORE ADMIN Interface :YES

      172.16.1.30[1146] [a4f1db00-ca47-1067-b31e-00dd010662da] Exchange Server STORE ADMIN Interface :YES

     

    ncacn_ip_tcp(Connection-oriented TCP/IP)

      172.16.1.30[1049] [12345678-1234-abcd-ef00-0123456789ab] IPSec Policy agent endpoint :YES

      172.16.1.30[1049] [12345778-1234-abcd-ef00-0123456789ac]  :YES

      172.16.1.30[1066] [bfa951d1-2f0e-11d3-bfd1-00c04fa3490a]  :YES

      172.16.1.30[1058] [bfa951d1-2f0e-11d3-bfd1-00c04fa3490a]  :YES

      172.16.1.30[1057] [bfa951d1-2f0e-11d3-bfd1-00c04fa3490a]  :YES

      172.16.1.30[1056] [bfa951d1-2f0e-11d3-bfd1-00c04fa3490a]  :YES

      172.16.1.30[1055] [bfa951d1-2f0e-11d3-bfd1-00c04fa3490a]  :YES

      172.16.1.30[1058] [a520d06e-11de-11d2-ab59-00c04fa3590c]  :YES

      172.16.1.30[1057] [a520d06e-11de-11d2-ab59-00c04fa3590c]  :YES

      172.16.1.30[1056] [a520d06e-11de-11d2-ab59-00c04fa3590c]  :YES

      172.16.1.30[1055] [a520d06e-11de-11d2-ab59-00c04fa3590c]  :YES

      172.16.1.30[1058] [8cfb5d70-31a4-11cf-a7d8-00805f48a135]  :YES

      172.16.1.30[1057] [8cfb5d70-31a4-11cf-a7d8-00805f48a135]  :YES

      172.16.1.30[1056] [8cfb5d70-31a4-11cf-a7d8-00805f48a135]  :YES

      172.16.1.30[1055] [8cfb5d70-31a4-11cf-a7d8-00805f48a135]  :YES

      172.16.1.30[1057] [1be617c0-31a5-11cf-a7d8-00805f48a135]  :YES

      172.16.1.30[1056] [1be617c0-31a5-11cf-a7d8-00805f48a135]  :YES

      172.16.1.30[1055] [1be617c0-31a5-11cf-a7d8-00805f48a135]  :YES

      172.16.1.30[1056] [97f83d5c-1994-11d1-a90d-00c04fb960f8]  :YES

      172.16.1.30[1055] [97f83d5c-1994-11d1-a90d-00c04fb960f8]  :YES

      172.16.1.30[1055] [82ad4280-036b-11cf-972c-00aa006887b0]  :YES

      172.16.1.30[1084] [1544f5e0-613c-11d1-93df-00c04fd7bd09] MS Exchange Directory RFR Interface :YES

      172.16.1.30[1084] [f930c514-1215-11d3-99a5-00a0c9b61b04] MS Exchange System Attendant Cluster Interface :YES

      172.16.1.30[1084] [83d72bf0-0d89-11ce-b13f-00aa003bac6c] MS Exchange System Attendant Private Interface :YES

      172.16.1.30[1084] [469d6ec0-0d87-11ce-b13f-00aa003bac6c] MS Exchange System Attendant Public Interface :YES

      172.16.1.30[1114] [f5cc5a18-4264-101a-8c59-08002b2f8426] MS Exchange Directory NSPI Proxy :YES

      172.16.1.30[1143] [38a94e72-a9bc-11d2-8faf-00c04fa378ff] MS Exchange MTA 'QAdmin' Interface :YES

      172.16.1.30[1143] [9e8ee830-4459-11ce-979b-00aa005ffebe] MS Exchange MTA 'Mta' Interface :YES

      172.16.1.30[1145] [a4f1db00-ca47-1067-b31f-00dd010662da] Exchange 2003 Server STORE EMSMDB Interface :YES

      172.16.1.30[1145] [0e4a0156-dd5d-11d2-8c2f-00c04fb6bcde] Microsoft Information Store :YES

      172.16.1.30[1145] [1453c42c-0fa6-11d2-a910-00c04f990f3b] Microsoft Information Store :YES

      172.16.1.30[1145] [10f24e8e-0fa6-11d2-a910-00c04f990f3b] Microsoft Information Store :YES

      172.16.1.30[1145] [99e64010-b032-11d0-97a4-00c04fd6551d] Exchange Server STORE ADMIN Interface :YES

      172.16.1.30[1145] [99e64010-b032-11d0-97a4-00c04fd6551d] Exchange Server STORE ADMIN Interface :YES

      172.16.1.30[1145] [89742ace-a9ed-11cf-9c0c-08002be7ae86] Exchange Server STORE ADMIN Interface :YES

      172.16.1.30[1145] [a4f1db00-ca47-1067-b31e-00dd010662da] Exchange Server STORE ADMIN Interface :YES

    ncacn_np(Connection-oriented named pipes)

      \\servername[\PIPE\atsvc] [0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53]  :YES

      \\servername[\PIPE\atsvc] [378e52b0-c0a9-11cf-822d-00aa0051e40f]  :YES

      \\servername[\PIPE\atsvc] [1ff70682-0a51-30e8-076d-740be8cee98b]  :YES

      \\servername[\PIPE\protected_storage] [12345678-1234-abcd-ef00-0123456789ab] IPSec Policy agent endpoint :YES

      \\servername[\PIPE\lsass] [12345678-1234-abcd-ef00-0123456789ab] IPSec Policy agent endpoint :YES

      \\servername[\PIPE\protected_storage] [12345778-1234-abcd-ef00-0123456789ac]  :YES

      \\servername[\PIPE\lsass] [12345778-1234-abcd-ef00-0123456789ac]  :YES

      \\servername[\PIPE\RESVC] [bfa951d1-2f0e-11d3-bfd1-00c04fa3490a]  :YES

      \\servername[\PIPE\SMTPSVC] [bfa951d1-2f0e-11d3-bfd1-00c04fa3490a]  :YES

      \\servername[\PIPE\POP3SVC] [bfa951d1-2f0e-11d3-bfd1-00c04fa3490a]  :YES

      \\servername[\PIPE\KNETINFO] [bfa951d1-2f0e-11d3-bfd1-00c04fa3490a]  :YES

      \\servername[\PIPE\INETINFO] [bfa951d1-2f0e-11d3-bfd1-00c04fa3490a]  :YES

      \\servername[\PIPE\RESVC] [a520d06e-11de-11d2-ab59-00c04fa3590c]  :YES

      \\servername[\PIPE\SMTPSVC] [a520d06e-11de-11d2-ab59-00c04fa3590c]  :YES

      \\servername[\PIPE\POP3SVC] [a520d06e-11de-11d2-ab59-00c04fa3590c]  :YES

      \\servername[\PIPE\KNETINFO] [a520d06e-11de-11d2-ab59-00c04fa3590c]  :YES

      \\servername[\PIPE\INETINFO] [a520d06e-11de-11d2-ab59-00c04fa3590c]  :YES

      \\servername[\PIPE\SMTPSVC] [8cfb5d70-31a4-11cf-a7d8-00805f48a135]  :YES

      \\servername[\PIPE\POP3SVC] [8cfb5d70-31a4-11cf-a7d8-00805f48a135]  :YES

      \\servername[\PIPE\KNETINFO] [8cfb5d70-31a4-11cf-a7d8-00805f48a135]  :YES

      \\servername[\PIPE\INETINFO] [8cfb5d70-31a4-11cf-a7d8-00805f48a135]  :YES

      \\servername[\PIPE\POP3SVC] [1be617c0-31a5-11cf-a7d8-00805f48a135]  :YES

      \\servername[\PIPE\KNETINFO] [1be617c0-31a5-11cf-a7d8-00805f48a135]  :YES

      \\servername[\PIPE\INETINFO] [1be617c0-31a5-11cf-a7d8-00805f48a135]  :YES

      \\servername[\PIPE\KNETINFO] [97f83d5c-1994-11d1-a90d-00c04fb960f8]  :YES

      \\servername[\PIPE\INETINFO] [97f83d5c-1994-11d1-a90d-00c04fb960f8]  :YES

      \\servername[\PIPE\INETINFO] [82ad4280-036b-11cf-972c-00aa006887b0]  :YES

      \\servername[\pipe\7337E5802C627AF8] [1544f5e0-613c-11d1-93df-00c04fd7bd09] MS Exchange Directory RFR Interface :YES

      \\servername[\pipe\7337E5802C627AF8] [f930c514-1215-11d3-99a5-00a0c9b61b04] MS Exchange System Attendant Cluster Interface :YES

      \\servername[\pipe\7337E5802C627AF8] [83d72bf0-0d89-11ce-b13f-00aa003bac6c] MS Exchange System Attendant Private Interface :YES

      \\servername[\pipe\7337E5802C627AF8] [469d6ec0-0d87-11ce-b13f-00aa003bac6c] MS Exchange System Attendant Public Interface :YES

      \\servername[\PIPE\MTASVC] [38a94e72-a9bc-11d2-8faf-00c04fa378ff] MS Exchange MTA 'QAdmin' Interface :YES

      \\servername[\pipe\A08C3AA835424C22] [38a94e72-a9bc-11d2-8faf-00c04fa378ff] MS Exchange MTA 'QAdmin' Interface :YES

      \\servername[\pipe\A08C3AA835424C22] [9e8ee830-4459-11ce-979b-00aa005ffebe] MS Exchange MTA 'Mta' Interface :YES

      \\servername[\pipe\E508ACDF33DD8E7F] [a4f1db00-ca47-1067-b31f-00dd010662da] Exchange 2003 Server STORE EMSMDB Interface :YES

      \\servername[\pipe\E508ACDF33DD8E7F] [0e4a0156-dd5d-11d2-8c2f-00c04fb6bcde] Microsoft Information Store :YES

      \\servername[\pipe\E508ACDF33DD8E7F] [1453c42c-0fa6-11d2-a910-00c04f990f3b] Microsoft Information Store :YES

      \\servername[\pipe\E508ACDF33DD8E7F] [10f24e8e-0fa6-11d2-a910-00c04f990f3b] Microsoft Information Store :YES

      \\servername[\pipe\E508ACDF33DD8E7F] [99e64010-b032-11d0-97a4-00c04fd6551d] Exchange Server STORE ADMIN Interface :YES

      \\servername[\pipe\E508ACDF33DD8E7F] [99e64010-b032-11d0-97a4-00c04fd6551d] Exchange Server STORE ADMIN Interface :YES

      \\servername[\pipe\E508ACDF33DD8E7F] [89742ace-a9ed-11cf-9c0c-08002be7ae86] Exchange Server STORE ADMIN Interface :YES

      \\servername[\pipe\E508ACDF33DD8E7F] [a4f1db00-ca47-1067-b31e-00dd010662da] Exchange Server STORE ADMIN Interface :YES

      \\servername[\pipe\tapsrv] [2f5f6521-cb55-1059-b446-00df0bce31db] Unimodem LRPC Endpoint :YES

     

    ncalrpc(Local Rpc)

      [DNSResolver] [3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5] DHCP Client LRPC Endpoint :YES

      [OLEF71DB2E0CD424B40A6BDFAC24EA9] [0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53]  :YES

      [wzcsvc] [0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53]  :YES

      [OLEF71DB2E0CD424B40A6BDFAC24EA9] [378e52b0-c0a9-11cf-822d-00aa0051e40f]  :YES

      [wzcsvc] [378e52b0-c0a9-11cf-822d-00aa0051e40f]  :YES

      [OLEF71DB2E0CD424B40A6BDFAC24EA9] [1ff70682-0a51-30e8-076d-740be8cee98b]  :YES

      [wzcsvc] [1ff70682-0a51-30e8-076d-740be8cee98b]  :YES

      [LRPC000003e0.00000001] [906b0ce0-c70b-1067-b317-00dd010662da]  :YES

      [LRPC000003e0.00000001] [906b0ce0-c70b-1067-b317-00dd010662da]  :YES

      [LRPC000003e0.00000001] [906b0ce0-c70b-1067-b317-00dd010662da]  :YES

      [LRPC000003e0.00000001] [906b0ce0-c70b-1067-b317-00dd010662da]  :YES

      [dsrole] [12345678-1234-abcd-ef00-0123456789ab] IPSec Policy agent endpoint :YES

      [protected_storage] [12345678-1234-abcd-ef00-0123456789ab] IPSec Policy agent endpoint :YES

      [securityevent] [12345678-1234-abcd-ef00-0123456789ab] IPSec Policy agent endpoint :YES

      [audit] [12345678-1234-abcd-ef00-0123456789ab] IPSec Policy agent endpoint :YES

      [dsrole] [12345778-1234-abcd-ef00-0123456789ac]  :YES

      [protected_storage] [12345778-1234-abcd-ef00-0123456789ac]  :YES

      [securityevent] [12345778-1234-abcd-ef00-0123456789ac]  :YES

      [audit] [12345778-1234-abcd-ef00-0123456789ac]  :YES

      [LRPC000004d0.00000001] [bfa951d1-2f0e-11d3-bfd1-00c04fa3490a]  :YES

      [RESVC_LPC] [bfa951d1-2f0e-11d3-bfd1-00c04fa3490a]  :YES

      [SMTPSVC_LPC] [bfa951d1-2f0e-11d3-bfd1-00c04fa3490a]  :YES

      [POP3SVC_LPC] [bfa951d1-2f0e-11d3-bfd1-00c04fa3490a]  :YES

      [KNETINFO_LPC] [bfa951d1-2f0e-11d3-bfd1-00c04fa3490a]  :YES

      [INETINFO_LPC] [bfa951d1-2f0e-11d3-bfd1-00c04fa3490a]  :YES

      [OLED5F4E5388D7F487A8A96689589AA] [bfa951d1-2f0e-11d3-bfd1-00c04fa3490a]  :YES

      [RESVC_LPC] [a520d06e-11de-11d2-ab59-00c04fa3590c]  :YES

      [SMTPSVC_LPC] [a520d06e-11de-11d2-ab59-00c04fa3590c]  :YES

      [POP3SVC_LPC] [a520d06e-11de-11d2-ab59-00c04fa3590c]  :YES

      [KNETINFO_LPC] [a520d06e-11de-11d2-ab59-00c04fa3590c]  :YES

      [INETINFO_LPC] [a520d06e-11de-11d2-ab59-00c04fa3590c]  :YES

      [OLED5F4E5388D7F487A8A96689589AA] [a520d06e-11de-11d2-ab59-00c04fa3590c]  :YES

      [SMTPSVC_LPC] [8cfb5d70-31a4-11cf-a7d8-00805f48a135]  :YES

      [POP3SVC_LPC] [8cfb5d70-31a4-11cf-a7d8-00805f48a135]  :YES

      [KNETINFO_LPC] [8cfb5d70-31a4-11cf-a7d8-00805f48a135]  :YES

      [INETINFO_LPC] [8cfb5d70-31a4-11cf-a7d8-00805f48a135]  :YES

      [OLED5F4E5388D7F487A8A96689589AA] [8cfb5d70-31a4-11cf-a7d8-00805f48a135]  :YES

      [POP3SVC_LPC] [1be617c0-31a5-11cf-a7d8-00805f48a135]  :YES

      [KNETINFO_LPC] [1be617c0-31a5-11cf-a7d8-00805f48a135]  :YES

      [INETINFO_LPC] [1be617c0-31a5-11cf-a7d8-00805f48a135]  :YES

      [OLED5F4E5388D7F487A8A96689589AA] [1be617c0-31a5-11cf-a7d8-00805f48a135]  :YES

      [KNETINFO_LPC] [97f83d5c-1994-11d1-a90d-00c04fb960f8]  :YES

      [INETINFO_LPC] [97f83d5c-1994-11d1-a90d-00c04fb960f8]  :YES

      [OLED5F4E5388D7F487A8A96689589AA] [97f83d5c-1994-11d1-a90d-00c04fb960f8]  :YES

      [INETINFO_LPC] [82ad4280-036b-11cf-972c-00aa006887b0]  :YES

      [OLED5F4E5388D7F487A8A96689589AA] [82ad4280-036b-11cf-972c-00aa006887b0]  :YES

      [OLEC98558706145477F816A963DC4EB] [1544f5e0-613c-11d1-93df-00c04fd7bd09] MS Exchange Directory RFR Interface :YES

      [LRPC000009f4.00000001] [1544f5e0-613c-11d1-93df-00c04fd7bd09] MS Exchange Directory RFR Interface :YES

      [LRPC000009f4.00000001] [f930c514-1215-11d3-99a5-00a0c9b61b04] MS Exchange System Attendant Cluster Interface :YES

      [LRPC000009f4.00000001] [83d72bf0-0d89-11ce-b13f-00aa003bac6c] MS Exchange System Attendant Private Interface :YES

      [LRPC000009f4.00000001] [469d6ec0-0d87-11ce-b13f-00aa003bac6c] MS Exchange System Attendant Public Interface :YES

      [MTASVC_LPC] [38a94e72-a9bc-11d2-8faf-00c04fa378ff] MS Exchange MTA 'QAdmin' Interface :YES

      [LRPC00000bc8.00000001] [38a94e72-a9bc-11d2-8faf-00c04fa378ff] MS Exchange MTA 'QAdmin' Interface :YES

      [LRPC00000bc8.00000001] [9e8ee830-4459-11ce-979b-00aa005ffebe] MS Exchange MTA 'Mta' Interface :YES

      [OLEDB2C9448A34B4E0A9E5E6A80E561] [a4f1db00-ca47-1067-b31f-00dd010662da] Exchange 2003 Server STORE EMSMDB Interface :YES

      [MSExchangeIS_LPC] [a4f1db00-ca47-1067-b31f-00dd010662da] Exchange 2003 Server STORE EMSMDB Interface :YES

      [OLEDB2C9448A34B4E0A9E5E6A80E561] [0e4a0156-dd5d-11d2-8c2f-00c04fb6bcde] Microsoft Information Store :YES

      [MSExchangeIS_LPC] [0e4a0156-dd5d-11d2-8c2f-00c04fb6bcde] Microsoft Information Store :YES

      [OLEDB2C9448A34B4E0A9E5E6A80E561] [1453c42c-0fa6-11d2-a910-00c04f990f3b] Microsoft Information Store :YES

      [MSExchangeIS_LPC] [1453c42c-0fa6-11d2-a910-00c04f990f3b] Microsoft Information Store :YES

      [OLEDB2C9448A34B4E0A9E5E6A80E561] [10f24e8e-0fa6-11d2-a910-00c04f990f3b] Microsoft Information Store :YES

      [MSExchangeIS_LPC] [10f24e8e-0fa6-11d2-a910-00c04f990f3b] Microsoft Information Store :YES

      [MSExchangeIS_LPC] [99e64010-b032-11d0-97a4-00c04fd6551d] Exchange Server STORE ADMIN Interface :YES

      [MSExchangeIS_LPC] [99e64010-b032-11d0-97a4-00c04fd6551d] Exchange Server STORE ADMIN Interface :YES

      [MSExchangeIS_LPC] [89742ace-a9ed-11cf-9c0c-08002be7ae86] Exchange Server STORE ADMIN Interface :YES

      [MSExchangeIS_LPC] [a4f1db00-ca47-1067-b31e-00dd010662da] Exchange Server STORE ADMIN Interface :YES

      [unimdmsvc] [2f5f6521-cb55-1059-b446-00df0bce31db] Unimodem LRPC Endpoint :YES

      [tapsrvlpc] [2f5f6521-cb55-1059-b446-00df0bce31db] Unimodem LRPC Endpoint :YES

      [OLE69D6542E1307487984F0DB988910] [3473dd4d-2e88-4006-9cba-22570909dd10] WinHttp Auto-Proxy Service :NO

      [LRPC00000318.00000001] [3473dd4d-2e88-4006-9cba-22570909dd10] WinHttp Auto-Proxy Service :NO

      [dhcpcsvc] [3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5] DHCP Client LRPC Endpoint :YES

     

    rpcdump completed sucessfully after 1 seconds

    __________________________________________________________

    I'm planning to upgrade Windows AD 2000 to 2003 the coming weekend at the latest so both GCs will be 2003. Then I will let you know if this resolves the problem. Can you see anything in the rpcdum /I?

    Thank you!

     
  • Tuesday, September 15, 2009 3:03 AMMike ShenMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hi,

    The RPCDump result looks good. Under the ncacn_http, we can get following entries:

    172.16.1.30[6002] [1544f5e0-613c-11d1-93df-00c04fd7bd09] MS Exchange Directory RFR Interface :NO
    172.16.1.30[6004] [f5cc5a18-4264-101a-8c59-08002b2f8426] MS Exchange Directory NSPI Proxy :NO
    172.16.1.30[6001] [a4f1db00-ca47-1067-b31f-00dd010662da] Exchange 2003 Server STORE EMSMDB Interface :NO

    At this time, please upgrae the GC from 2000 to 2003 to check whether the issue can be solved. After upgrating GC servers, please check whether the Outlook is able to connects to Exchange through RPC over HTTPs in internal network
    (Please check connection status).

    If the issue persists, please run RPCPing tool to test the connection again and post result here.

    Thanks,
    Mike


     
  • Tuesday, September 15, 2009 6:51 PMMTLER1 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Thank you. Will post an update in few days when I upgrade GC.
     
  • Tuesday, September 22, 2009 7:08 AMMike ShenMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    Hi,

    Any update regarding the issue?

    Whether the Outlook is able to connects to Exchange through Https in internal network after upgrading GC to 2003?

    Thanks,
    Mike
    • Marked As Answer byMTLER1 Monday, September 28, 2009 3:14 PM
    •  
     
  • Monday, September 28, 2009 3:22 PMMTLER1 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Mike,
    After upgrading AD to Windows 2003, RPC over HTTPs worked. Than you!
    What I noticed is that when one DC is down, RPC over HTTPs doesn't work. It's not a big deal, I thought that if at least one DC is up then RPC over HTTPs should be fine. I'm curious. Do you have any suggestions?
    Thank you.
     
  • Tuesday, September 29, 2009 3:44 AMMike ShenMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Hi,

     

    Thanks for your response.

     

    I am glad to know that the ROH issue could be solved after upgrading to server 2003. Regarding your current issue, would you please let me know?

     

    1. Whether both the two GCs  have been upgrading to Windows 2003?

    2. Whether the issue only occurs when specific GC is down or the issue occurs when one of the two GCs is down?

    3. I would like to explain by default, after Exchange 2003 SP1, for ROH, the Outlook client uses the local Exchange server for requests for directory information. The client computer uses the DSProxy proxy service port (6004) on the Exchange server for requests for directory information. The Exchange server forwards the request to the global catalog server. Nevertheless, if the following registry key is configured, the Outlook will connect to GC directly and you may encounter the problem

     

    How to control the DSProxy process for RPC over HTTP connections in Exchange Server 2003 SP1

    http://support.microsoft.com/default.aspx/kb/872897

     

    4. Please also check whether the “NSPI Target Server” is configured:

     

    http://technet.microsoft.com/en-us/library/aa998557.aspx

     

    5. Please review 2080 event on the server to check whether the Exchange Server is able to detect both two GCs:

     

    Event ID 2080 from MSExchangeDSAccess

    http://support.microsoft.com/kb/316300


    Mike Shen 

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfb@microsoft.com