Exchange Server Forums

RPC over HTTP Issues (Status 200 in Logfile, Timeouts for Clients)

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2007] >> Installation >> RPC over HTTP Issues (Status 200 in Logfile, Timeouts for Clients)

Page: [1]

Message

<< Older Topic Newer Topic >>

RPC over HTTP Issues (Status 200 in Logfile, Timeouts f... - 15.Dec.2007 8:39:24 PM

fullman

Posts: 23
Joined: 26.Jul.2005
From: Fort Lauderdale, FL
Status: offline

I'm setting up my Exchange server and so far everything except RPC over HTTP is working fine:

The server can send/receive mail to/from the outside world without issue
OWA works just fine, our users can log in and see their mail, send it, receive it
Anti-Spam filters are working with blacklists, etc

Now, the last thing I need to do is get RPC working. Here's what I've done so far:

I installed the RPC over HTTP component in Add/Remove
I made sure it's set to Accept in the Web Extensions section of IIS
I made sure that "Basic Authentication" is set in the RPC virtual directory and Anonymous Access is unchecked (as it says in many site posts/MS knowledge base)
- For some reason, even when I uncheck "Integrated Windows authentication", it comes back after a few minutes all on its own, I think Exchange is resetting it?
Ports 6001, 6002 and 6004 are opened on our firewall and NetStat shows it as listening on those ports
I see listings in the IIS logfile showing a status of 200 (OK) for the rpcproxy.dll for our users

Yet, no matter what I do, our Outlook 2007 and 2003 clients will timeout.

Here's what I've ruled out:

"mail" CAS is invalid or unsigned -- nope, it's valid and works fine, no issues when connecting to https://mail.[companyname].com/owa for OWA
Ports blocked on client/remote end -- nope, worked with the previous server
Incorrect configuration for Outlook -- nope, "mailserver.[companyname].com" as the Exchange server and "mail.[companyname].com", both fast/slow checkboxes and basic authentication are configured correctly under the "Connect to Microsoft Exchange using HTTP"

Server Info:

Exchange 2007 on Server 2003 R2 62bit
Single-server deployment (no front-end + back-end configuration)
40 users

UPDATE: I just used the rpcping from the Server 2003 Resource Kit and got the following result:

rpcping -t ncacn_http -s mail.[companyname].com -o RpcProxy=mail.[companyname].com -P "chris,[domain],*" -I "chris,[domain],*" -H 1 -u 10 -a connect -F 3 -v 3 -E -R none

RPCPinging proxy server mail.agencynet.com with Echo Request Packet
Sending ping to server
Response from server received: 200
Pinging successfully completed in 281 ms