Re: RPC over HTTP Connection Problem
- From: "Nick Gillott [MVP]" <nick@xxxxxxxxxxxxx>
- Date: Sun, 4 Feb 2007 18:00:04 -0000
SO hang on, it connects but you want to fix that?
TCP/IP is a suite of protocols. HTTPS is a port. If you are connecting you are either using port 80 or port 143.
Check netstat.
"Netadmin" <Netadmin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:1C9204A9-093F-41D4-868A-AD457F78E4B1@xxxxxxxxxxxxxxxx
I have a single server environment and I setup RPC over HTTP on the server
with no Front-End Server. I'm able to connect using my Outlook Client,
however, its uing TCP/IP not HTTPS (per the outlook.exe /rpc). My server is
Exchange 2003 SP2 on Windows 2003 SP1
I followed the TID to add the correct port # in the registry for the key
RPCProxy. I also followed the TID to test the RPC connectivity via a web
browser and all of that went well. I checked to make sure the rpcproxy.dll
file is being loaded and it is.
Now when I run "RPCDump /s <server name> /p ncacn_http "
I get the following error:
Querying Endpoint Mapper Database...
RpcMgmtEpEltInqNext:(Access is denied). ).
Anyone know how I can get this corrected?
.
- Prev by Date: RPC over HTTP inside Network
- Next by Date: Re: RPC over HTTP inside Network
- Previous by thread: RPC over HTTP inside Network
- Next by thread: Re: RPC over HTTP Connection Problem
- Index(es):
Relevant Pages
|