asked on

OWA in Exchange 2003 Using Different Port

I have an exchange server 2003 running. I setup the default website in IIS on the exchange server to accept requests on inbound port 81. When i type the address of the exchange server (http://www.domain.com/exchange) i get the password challenge screen. I enter the user ID and password but it does not accept it. It keeps comming back and asking me to input the password and user id for access. I know the user and password are correct.

What am I doing wrong? Do I need to setup something different on the user profile in order to get this to work?

help.

Thanks,

Ray

redseatechnologies

Changing the port is not recommended, exchange relies on it for more than OWA.

Also, now would be a good time to enable SSL and use FBA

-red

redseatechnologies

mcgowray,

I was looking around for a link that supports the above, and here it is;

http:Q_21669471.html#15514261

-red

Ray McGowan

ASKER

I am using a Sonicwall tz-170 firewall with standard OS. I have been testing the system from outside. From outside or inside, 81 works, 444 does not.

redseatechnologies

Do you have sharepoint on that server?

Try a different port for SSL - such as 446.

Also, have a look in your rotuer and see if you can change the target port - I will look for a guide on it now

-red

Ray McGowan

ASKER

Thanks Red but I dont have an option, the broadband service they are using blocks port 80,25 and 110. I will try the SSL port. Can I use a different one than 443. I use 443 to forward for secure firewall access.

Thanks,
Ray

redseatechnologies

If your ISP are blocking port 80, then you need to pay the difference and get a business account, or change ISPs.

Changing the SSL port should be OK, just don't tick the box that "requires SSL", as you will have the same problem as above.

-red

Ray McGowan

ASKER

No good on port 446. Same error (Page cannot be displayed). I cannot redirect the target port on this firewall running the standard OS. I believe the Enhance version of the firewall OS can do that.

Ray McGowan

ASKER

If I use port 81 it works fine. If I use the SSL Port 444 and type https://<domain.name>:444/exchange I get Page cannot be displayed.

ASKER CERTIFIED SOLUTION

redseatechnologies

membership

This solution is only available to members.

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

Start Free Trial

redseatechnologies

Are you testing this from inside the network first?

redseatechnologies

What router are you using?

You may also be able to configure port redirection. Then you could forward port 81 (or 444) to port 80 on the server (or 443).

Then you could still bypass the ISP restriction, without damaging Exchange and IIS

-red

Sembee

How many times do you need to access the firewall? My personal preference would be to move the firewall access off port 443 so that you can use the well known SSL port and not inflict the :444 requirement on the users. Admin access to the firewall should be infrequent, so use an uncommon port.

OWA is probably the most complex web application ever built and it was designed to operate on port 80 and 443 only. I have had very little success using other ports and don't recommend that other ports are used. I also find that its use by the users is limited when they have to put other things in to the URL - as soon as you remove the port number requirement the use goes up.

Simon.

crawfordits

I have used a SSL port other than 443 for years and have had no problem with that. I agree on the port 80 however. We have never used the shortcut to OWA directly. We always just put it as a link on a web page therefore eliminating the frustation from a user having to remember the port #.

Ray McGowan

ASKER

Red,

Thanks for all the help.