asked on

Outlook 2003 connect thru RPC over HTTPS error

I have received this error using OL2003 SP2 connecting via RPC thru HTTPS to Exchange 2003 SP2 Server. My firewall allows port 80, 443 and 444 to my server. I have tested my RPC/HTTPS OL2003 config in the office with success. My external tests have no proxy or firewall intervention from the sites that I have used. Logon seems to complete fine but the error occurs at Send/Recieve call.
Any ideas?

Coolie Sheppard

port 25. smtp.

firewall is most likely blocking that. thats used to send your email

Sembee

Port 25 has nothing to do with RPC over HTTPS.
When you tested it internally, did you verify the connection was being made over HTTPS? With Outlook connected, hold down SHIFT and right click on the Outlook icon and choose Connection Status. That will show whether it is connecting by TCP/IP or HTTPS.

Simon.

weareit

Are you able to access your server using OWA?

Are clients who are not using RPC over HTTPS able to connect to the server?

-saige-

tcurtispc2

ASKER

Sembee,
You are right...port 25 has nothing to do with this. Holding down the 'Ctrl' key and right clicking on the Outlook icon - choosing Connection Status, I found the conections to be TCP/IP. So my internal testing was not necessarily valid...good point. Any further ideas?

tcurtispc2

ASKER

OWA is working great (internal and externally) as well as internal connectivity to Exchange.

weareit

Well if connectivity to the server is good with OWA and Internally then something is wrong with your RPC configuration.

As Simon has stated so many times before:
Basically RPC over HTTPS fails on three points....

- SSL certificate acceptance
- Authentication
- Registry settings.

I'd say its time to double check the configuration of your RPC services. 8004011D makes me think SSL Certificate. What does the issued to statement in the certificate say?

-saige-

tcurtispc2

ASKER

I think that I may have it...upon review of the the article: Troubleshooting RPC over HTTPS (Part 2)
I checked the Auth at RPC under IIS. It was set to Anonymous, NT Auth and Basic. It should only be Basic. I reset it properly, restarted IIS and will be heading out for remote test. I will keep all posted.

weareit

Good luck

Sembee

The authentication settings can actually be basic and/or integrated. If you have basic only set then the clients will always prompt. If you have integrated set and set the relevant option in Outlook (NTLM) and the client is a member of the domain then pass through authentication will work.

Simon.

tcurtispc2

ASKER

Well I fixed it.

Great help from articles: Implementing RPC over HTTPS in a single Exchange Server 2003 environment, Troubleshooting RPC over HTTPS (Part 1), Troubleshooting RPC over HTTPS (Part 2) from MS Exchange.org.

Turned out to be the registry setting for:
HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\RPC\RPCPROXY.

Change the data to what is shown in the following picture. You must use Port Range 6001-6002 for the NetBIOS and DNS FQDN and Port 6004 also for the NetBIOS and DNS FQDN.

Here was my example:
[old-existing]
myserver:100-5000

[new-change to]
myserver:593;myserver:6001-6002;myserver:6004;myserver.mydomain.local:593;myserver.mydomain.local:6001-6002;myserver.mydomain.local:6004

Voila! - Works like a champ!
Thanks to all!

tcurtispc2

ASKER

That's all

ASKER CERTIFIED SOLUTION

Computer101

membership

This solution is only available to members.

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

Start Free Trial