sclam
asked on
Exchange 2003 RPC over HTTP (Exception 1722)
Scenario & Settings
=============
Front end server @ DMZ
Back end server and AD @ private network
ValidPorts Registry on FE server is set to "BE:6001-6002;be.xxx.com:6
CISCO PIX allows all ports between FE, BE and AD.
SSL published by the FE CA to the FQDN fe.xxx.com (OWA works fine)
RPC folder on FE IIS is set to use basic authentication
Everything's working fine for months (POP, IMAP, OWA, etc) except RPC over HTTP.
outlook.exe /rpcdiag shows local outlook are still using tcp/ip and remote outlook is unable to connect.
rpcping result in Exception 1722.
with the -E option
============
(ping from the front end server fe.xxx.com)
RPCPinging proxy server fe.xxx.com with Echo Request Packet
Checking IE setting...
The proxy setting is disabled.
Sending ping to server
Response from server received: 200
Pinging successfully completed in 94 ms
(ping from client PC in private network)
RPCPinging proxy server fe.xxx.com with Echo Request Packet
Checking IE setting...
The proxy setting is disabled.
Sending ping to server
Error 12175 returned in the WinHttpSendRequest.
Ping failed.
I think I have mess up a bit on the registry following the solution searched from the Internet. Once created the MSExchangeDSAccess and LdapKeepAliveSecs but removed already.
Is there a way to sort out where the problem is? Thanks a million!
=============
Front end server @ DMZ
Back end server and AD @ private network
ValidPorts Registry on FE server is set to "BE:6001-6002;be.xxx.com:6
CISCO PIX allows all ports between FE, BE and AD.
SSL published by the FE CA to the FQDN fe.xxx.com (OWA works fine)
RPC folder on FE IIS is set to use basic authentication
Everything's working fine for months (POP, IMAP, OWA, etc) except RPC over HTTP.
outlook.exe /rpcdiag shows local outlook are still using tcp/ip and remote outlook is unable to connect.
rpcping result in Exception 1722.
with the -E option
============
(ping from the front end server fe.xxx.com)
RPCPinging proxy server fe.xxx.com with Echo Request Packet
Checking IE setting...
The proxy setting is disabled.
Sending ping to server
Response from server received: 200
Pinging successfully completed in 94 ms
(ping from client PC in private network)
RPCPinging proxy server fe.xxx.com with Echo Request Packet
Checking IE setting...
The proxy setting is disabled.
Sending ping to server
Error 12175 returned in the WinHttpSendRequest.
Ping failed.
I think I have mess up a bit on the registry following the solution searched from the Internet. Once created the MSExchangeDSAccess and LdapKeepAliveSecs but removed already.
Is there a way to sort out where the problem is? Thanks a million!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks Matt! just managed to add the cert to trusted root CA in a client PC (located in private network).
the "Error 12175 returned in the WinHttpSendRequest" error is gone. but the proxy setting is still disabled. any idea?
(ping with -E from client PC in private network) - after trusted the root CA
RPCPinging proxy server fe.xxx.com with Echo Request Packet
Checking IE setting...
The proxy setting is disabled.
Sending ping to server
Response from server received: 200
Pinging successfully completed in 261 ms
the "Error 12175 returned in the WinHttpSendRequest" error is gone. but the proxy setting is still disabled. any idea?
(ping with -E from client PC in private network) - after trusted the root CA
RPCPinging proxy server fe.xxx.com with Echo Request Packet
Checking IE setting...
The proxy setting is disabled.
Sending ping to server
Response from server received: 200
Pinging successfully completed in 261 ms
if your client use windows xp, there was a hotfix for this issue but i cant remember the exact KB, search microsoft site & u will find it
ASKER
Thanks tshalim for ur suggestion, I've already done that at the beginning.
I gave a try on outlook (even it says proxy setting is disabled) and surprisingly it worked. Thanks Matt!
I gave a try on outlook (even it says proxy setting is disabled) and surprisingly it worked. Thanks Matt!
ASKER