Question Locked

OWA and the outside world

0 helpful
10 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have an SBS 2003 server with OWA and RWW enabled. I forwarded ports 80 and 443 to the server through the firewall.

Internally the sites both work fine. But outside of the network neither of them work.

The firewall logs show the incoming request and what seems to be a response going out on a random port over 61000.

Any ideas why I can't get a connection with a remote client?

10 replies

by styches

I enabled OWA and RSS with the CEICW. Both pages work well inside the network. From outside however, the clients time out and get "page cannot be displayed." The server is behind a simple lynksis firewall with port forwarding enabled for ports 80 and 443.

by cg it

if your using a dual NIC SBS server, stick the external NIC on the Linksys enabled DMZ port. allow OWA and RWW in the SBS Server firewall.

then test it.

if it works on the DMZ but doesn't work with port forwarding, then its the router. This is typical of consumer level routers.

by styches

In addition, I moved the server to the DMZ and outside conections still fail. Internal connections still work.

by styches

Replaced the router with a new one but had no effect.

by don ticulate

Public static IP from ISP to Private static IP on network!

Then Configure Rules for ports 80 & 443 to and from!

by cg it

try this

https:// /remote

IE should prompt that the server certificate is not signed. click ok to accept unsigned server certificate.

the RWW SBS login screen should appear. May take some time to show depending upon your internet connection speed.

make sure that port 443 checkbox is checked in IIS on default web site.

If this does not work, then you have to start over from the beginning following the instructions in the transcript on this MS SBS technet link.

http://support.microsoft.com/kb/833983

once you have setup RWW and OWA retry to connect using your public IP address in the URL.

once you can connect using your public IP address, you can create an A record in your authorative DNS server for your public domain name which will resolve https domain name requests to your public IP address.

note: like http requests which are over port 80 and you don't have to use a port number with the IP address, you don't have to specify port 443 when using https in the URL.

by pinchequay2

You should check to make sure that your SSL certificate is properly installed on your serve. I would also check my IIS configuratioin and security at default web site>Exchange.

This discussion is closed to new replies.