asked on

Unable to access RPC over HTTP through Firewall accessing a DC running Exchange 2003

I first must say I cannot put my frustration into words. That being said here is the scenario:

DC running Server 2003 and Exchange 2003, and Certificate Services
Global Catolog on other DC running Server 2000
Added to Global Catalog server registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters
REG_MULTI_SZ
Name: NSPI Interface protocol sequences
Value: ncacn_http:6004

Added to Exchange DC registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\RpcProxy
Key:ValidPorts

exchange01:100-5000;
exchange01:6001-6002;
exchange01:6004;
exchange01.domain.local:6001-6002;
exchange01.domain.local:6004;
mail.publicdomain.com:6001-6002;
mail.publicdomain.com:6004;

I forwarded all these ports on our router to the Exchange Server

I can connect through OWA no problem

When attempting to connect using Outlook 2003

I get NOTHING? Not even a login box?

Thanks in advance for any assistance.

mvvinod

First of all,
You dont need to forward all the ports on the router. These ports are used internally in the server. RPC over http only uses port 443 till the server. Follow this document to test the rpc proxy first...

http://support.microsoft.com/default.aspx?scid=kb;en-us;833401

And from my experience, 100-5000 ports are not required.... Did you also install rpc proxy in add/remove windows components....

Are you correctly configuring the clients???
Does your clients trust your CA ??

There are several links in the above page to troubleshoot setp by step. Try them and let me know...

Vinod.

mvvinod

This might be useful too:

http://www.microsoft.com/technet/prodtechnol/exchange/guides/E2k3RPCHTTPDep/92f1a371-86dc-4839-9732-5a85525a0874.mspx?mfr=true

Vinod

INetX

ASKER

Thank you,

I'll check out the links.

If Exchange is only running on one server does it need to be configured as the "RPC-HTTP back-end server"?

ASKER CERTIFIED SOLUTION

mvvinod

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

INetX

ASKER

It's working!

The problem was there were two similar SSL certificates in the same folder I happened to install the wrong one. Right now I have RPC configured to require SSL but not the OWA. That is until I figure out a way to seemlessly install the certificate on remote clients. Do you know of a way to automate this process?

THANKS!

mvvinod

Domain members always trust the enterprise ca in your domain...

If your laptops are not domain mebers, i strongly suggest you buy a certificate form thawte, verisign etc which all windows clients trust. It will be a lot easier than putting in trusted root ca in each laptop.

Vinod.

INetX

ASKER

Thanks,

So what you're saying if I first install my laptops in the domain then take them out to the field I shouldn't have a problem, correct?