RPC over HTTP problem - IIS gives 503 error (exchange 2003)
I am running exchange 2003 on sbs and trying to deploy rpc over http, I have done one deployment in the past but this one has my at a loss.
When I attempt to access /rpc I am continuously prompted for credentials
When I attempt to access /rpc/rpcproxy.dll I get prompted for credentials, and I can authenticate then I get a 503 service unavailable page.
Not sure what to do at this point ..
August 10th, 2011 9:29pm
Regarding authentication.
How is /RPC directory configured?
Verify settings and value of validpiorts http://technet.microsoft.com/en-us/library/aa997495(EXCHG.65).aspx
At the end of this article there is links to several other places, follow them for more steps to verify.
lasse at humandata dot se, http://anewmessagehasarrived.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
August 11th, 2011 3:43am
Hi,
Please use the RPCping to test the
RPC over HTTP :
1. Download the and install RPCping on your external client.
http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&DisplayLang=en
2. Run the following command to verify if the the client is able to connect to proxy server without problem:
rpcping -t ncacn_http -s YourExchMBXServer -o RpcProxy=YourRPCProxyServer -P "user,domain,PASSWORD" -I "user,domain,PASSWORD" -H 1 -u 10 -a connect -F 3 -v
3 -E -R none
Note:
Replace
YourExchMBXServer with the FQDN of your exchange server , replace
YourRPCProxyServer with the FQDN of your IIS proxy server.
-H, This argument is the authentication type that is used for the RPC Proxy server. Use the value 1 for basic authentication, and use the value 2 for NTLM authentication.
- F, These arguments are the flags that pass for RPC/HTTP front end authentication. The No SSL flag is 2, and the Use SSL flag is 3.
the RPC Ping Utility test was successful, you will receive the following reply:
RPCPinging proxy server ExchServer with Echo Request Packet
Sending ping to server
Response from server received: 200
Pinging successfully completed in Response_Time ms
Then move to next step to test if the external client can connect to the validports on the mailbox server:
3. Type:
rpcping -t ncacn_http -s YourExchMBXServer -o RpcProxy=YourRPCProxyServer -P "user,domain,PASSWORD" -I "user,domain,PASSWORD" -H 1 -u 10 -a connect -F 3 -v
3 -e:6001
rpcping -t ncacn_http -s YourExchMBXServer -o RpcProxy=YourRPCProxyServer -P "user,domain,PASSWORD" -I "user,domain,PASSWORD" -H 1 -u 10 -a connect -F 3 -v
3 -e:6002
rpcping -t ncacn_http -s YourExchMBXServer -o RpcProxy=YourRPCProxyServer -P "user,domain,PASSWORD" -I "user,domain,PASSWORD" -H 1 -u 10 -a connect -F 3 -v
3 -e:6004
If the RPC Ping Utility test was successful, you will receive the following reply:
Completed 1 calls in xxx ms
If you receive any errors, please post it here for further research.
More information about the usage of RPCping, please refer the following article:
http://support.microsoft.com/kb/831051
August 11th, 2011 4:19am
Any update on the issue?Gulab | MCITP: Exchange 2010-2007 | Lync Server 2010 | Windows Server 2008 | Skype: Exchange.Ranger | Blog: www.ExchangeRanger.Blogspot.com
Free Windows Admin Tool Kit Click here and download it now
August 12th, 2011 1:40am