• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 383
  • Last Modified:

Can't Connect to OWA 2003 server that is sitting behind an OpenBSD Firewall/Web server using port forwarding

Our company uses Exchange as it's groupware solution and apache webserver on openbsd unix as the firewall/web server for the company's web site.  We have an SBS 2003 server set up to host exchange. I can connect to OWA 2003 from any internal/private ip computer just fine.  However, I can't connect to OWA 2003 from the internet (i.e. at home).  Because I want requests to port 80 and 443 to be answered by the OpenBSD box (apache webserver) I have used port forwarding to forward requests for OWA/IIS access to ports 8080 (port 80) and 4430 (port 443) on the openbsd box.  These ports map as follows:

Port 8080 on Unix firewall maps to port 80 on SBS 2003 server
Port 4430 on Unix firewall maps to port 443 on SBS 2003 server

So for example to get to our corporate web site you would type http://www.corporatewebsite.com

However, to get to the IIS box and access remote web workplace, owa, etc, you would type https://www.corporatewebsite.com:4430

So far I have not been successful getting this to work.  I have searched and searched and searched.  Any help you can offer me would be great.  I can get to the remote web workplace screen where I have options to connect to a server, client, email etc, however, I can't get OWA to work...it just sits there and the screen goes blank.

Any ideas?
0
lowrycito
Asked:
lowrycito
1 Solution
 
chumpletCommented:
Do you have IIS on the Exchange/SBS server listening on those ports, or are they still set to listen on 80/443?
0
 
lowrycitoAuthor Commented:
I never changed the default settings of the Exchange/SBS server...I believe they have always been set to listen on 80/443.  The firewall rules on the unix box are set to forward port 8080 to port 80 on the SBS box and port 4430 to port 443 on the SBS box.  Does that answer your question or did I misunderstand.
0
 
SembeeCommented:
OWA doesn't like operating over other ports. I have seen nothing but problems with using other ports - go back to the ports it expects and everything works fine.
You must remember that OWA is a complex web application and there is a lot a communication between the client and the server. It is expecting that traffic to be on port 443 or 80.
Then you may get users on a site where port 80 and 443 are the only ports allowed out and they will not be able to use OWA at all.

If possible I would look at using another subdomain (mail.domain.com) and allowing the connection through on the ports that it expects - possibly 443 only to maintain security.

Simon.
0

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now