Link to home
Start Free TrialLog in
Avatar of Shando1971
Shando1971

asked on

owa exchange 2003 for 2nd server using different port

I'm trying to have owa user for my 2nd exchange 2003 to access their mailboxes, using a 2nd url (https://mail.yourdomain.com:444/exchange) to avoid having a front end server, I already did the port forwarding on the firewall, but when I tried to connect I got page could not be displayed,
-Do I need to do anything on the 2nd server to get this to work?
-I only have a self cert on the main server, do I need to do one on the 2nd one as well?
Avatar of ikshf143
ikshf143
Flag of India image

Hi,

Yes, You will have to install a new cert with the 2nd URL on the second server and under default web site where you have the ports 80 and 443 change it to 444 for SSL and then try.

Imran
i have another question for you, or is it that we are using the same URL and just changing the ports
Avatar of Narayan_singh
Are you using the same uRL to access the mailbox in different server ?

You will need a certificate on the second server. This is what allows it to create an SSL session.

The second Exchange Server will be installed to work by default on port 443 for secured OWA communications. You need to change this setting to port 444 in IIS Manager. In IIS Manager, edit the properties of the website, go to Advanced and then edit the HTTPS declaration to read port 444. Alternatively, you can leave the server-side port configuration as-is, and use the Port Address Translation (PAT) feature of your firewall, if it has it, to map port 444 outside onto port 443 on the internal server.

-Matt
Avatar of Shando1971
Shando1971

ASKER

Sorry for the delay to answer guys, I wasn't able to work for the past few days after my post.
Yes I'm using a 2nd url, it is the same as the one for the first server except that I'm adding the port to it.
I'll do what you suggested and will let you know..
I have been trying to get it to work for the past 2 days, but I try to login locally to test the success of the cert installation using https://servername/exchange I get internet explorer cannot display the page, if I go to iis default site>right click>browse I get "The page must be viewed over a secure channel" error.
I try to login from outside using "https://mail.yourdomain.com:444/exchange" I get the cert warrning, click continue, then I get the login screen, I put the user name and password, it flashes and same screen come back again with the credintials I had just input.

The first test is whether it works internally without SSL. Remove the "SSL is required" option from the site object in IIS and then attempt to browse to OWA using http://servername/exchange.

-Matt
I got it working, except that the public folder only displays for users on the main serve, but when a user on the server I just installed the cert on try to get to it they get internet explorer cannot display the web page.

When does that happen? When the user attempts to browse to https://servername/public?

We don't use public folders, but I believe unless the back-end server you are accessing OWA via holds a replica of the Public Folder, attempting to access it through OWA will not work.

-Matt
They try to access it from outside the network, and I belive the server has a replication enabled so it will replicate with the server that has the public folder. I don't have a backend/fronend configuration, all this was to avoid having a frond end server.

You need to check the Public Folder(s) are indeed in sync between the two Exchange Servers. If they are not, you will have problems.

-Matt
They are in sync, otherwise how come the outlook clients inside the network are able to see them (unless they accessing it by going to the main server)?
Can I delete the older sync relationship and recreate a new one?
if so what is the best way to do that in steps?
ASKER CERTIFIED SOLUTION
Avatar of tigermatt
tigermatt
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
You were correct, the sync wasn't configured on the new server, once I enabled it I was able to get to the public folders...thank you for all your help...
No problem. Glad to hear you got it working.