Link to home
Start Free TrialLog in
Avatar of Computerguy107
Computerguy107

asked on

Public IP for RPC/HTTP Exchange Server 2003

can I use the public ip address of my exchange server as the server address in the client setup for RPC/HTTP

Thanks
Avatar of Irwin Santos
Irwin Santos
Flag of United States of America image

Yes that is the preferred method.
check that...  "Yes.. that is a method"

that's if you are NOT using DNS or don't wish to.  Ideally you want a FQDN (fully qualified domain name)
SOLUTION
Avatar of Sembee
Sembee
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Computerguy107
Computerguy107

ASKER

I will admit I am a little confused. We have our mail coming to our exchange server and so we have mail.company.net but is that a FQDN? I can get to our Outlook Web Mail by typing in the https://mail.company.net/exchange without a problem and can access RPC/HTTP locally. When I try to access remotely it tells me it can't find the exchange server. For testing purposes how would I set up the server not to use a SSL certificate so I can use the IP address or is my problem that I have not issed a certificate for mail.company.net. How do I create a certificate for mail.XXXXXX.net?

Thanks :-)
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Where did the SSL certificate come from?
If was purchased then you are fine.
If it was created by the installation of the server, via SelfSSL or Certificate services, then you need to import the certificate on the client.

The rule is that if you browse to https://mail.domain.com/rpc (where mail.domain.com is the name on the certificate) and get a security warning, then RPC over HTTPS will NOT work. Outlook cannot cope with the security warning.
You either need to purchase a commercial certificate - something like RapidSSL StarterSSL will be fine, or import the certificate in to each device.

Unlike the poster above, I do NOT recommend the use of self signed certificates outside of lab/test environments. Production deployments should use a commercial certificate - and at the cost of US$70/year, they are small investment to make, to avoid the disruption and hassle of deploying a self signed certificate.

As you have a certificate in place, I would not recommend going through the extensive hoops to disable the SSL support in the feature. It was primarily designed to work with SSL, so that is what you should concentrate on.

Simon.
side note.. my recommendations were for FREE stuff...but Sembee pointed that a commercial certificate would be a good investment.
I always love the free stuff and will look into it furthur when I have more time. Right now I needed to get it running so I created a VPN. Thanks for all your help, this has been a learning experience. Thanks Simon and irwinpks. One last question for now. How do I split up the points.?

Thanks

Roger
locate above the comment box for "SPLIT POINTS"

:-)

thanks in advance!

Aloha from Hawaii,

Irwin
cool.. thank you!