Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

No access to OWA on Win2003 SBS

Status
Not open for further replies.

GFAlexander

IS-IT--Management
Nov 12, 2001
68
GB
Hi all,

I have a single Exchange server installed on a client site, and before I added a new hardware firewall (Netgear FVS114) I could access OWA from both the internal network and via the Internet.

After istalling and configuring the above firewall, whilst I can still access OWA using the internal private address whilst on the network, I can no longer access it via the internet.

By process of elimination, I'm thinking it's the firewall (as it worked before), but I have incoming http and https traffic always allowed and forwarded to the first (static) internal address of the server NIC (it has 3 different static IP addresses).

Can anyone offer any help on what I might be missing? I've read about port 443 and SSL, but I shouldn't need to do this for a non FE / BE install should I?

Thanx

Gary Alexander
 
First make sure that your WAN address is the address of your netgear and exchaneg server mx records and A records. The Netgear does not allow you to use multiple addresses it can only forward on its address to a local address.

Then go into the router and under security go into rules, click on the down arrow of services and choose http: then clisk action, by default it will always BLOCK, choose to always allow.
then choose the LAN Server address, type your exchange server local address. Then click apply.

Do the same for https

This should Solve your Problem.
 
I've read about port 443 and SSL, but I shouldn't need to do this for a non FE / BE install should I?
========

YES, you should since u only have one server ur exposing AD and Exch...if all possible try to setup FE but if not then you should use SSL and patch up IIS.

I fyour NAT is ok then check to see which Nic/IP is assigned to OWA, you need to set it manually.(u can do it through IIS ADmin)

All the best!

:--------------------------------------:
fugitive.gif

[URL unfurl="true"]http://mostarnet.com[/url]

All around in my home town,
They tryin' to track me down...
 
As lebisol said, you should use 443 as that encrypts the communications with the server.

Verify port 80 is forwarded to the Exchange box if you're not going to use SSL. Verify port 443 is forwarded to the Exchange box if you ARE going to use SSL.

Pat Richard, MCSE MCSA:Messaging CNA
Want to know how email works? Read for yourself -
 
Hi Guys,

Thanx for the responses.

Firstly dpwsmw, even when I try to reach owa from the Internet using the external IP address, which worked before the firewall was installed, I still get "the page cannot be displayed".

Under the rules section, I have http and https incoming traffic allowed, and directed to the internal IP address of the Exchange server.

I can't however see which Nic/IP is assigned to OWA, or where to check it manually through IIS ADmin. Can you advise where I can find it Leibisol?

Thanx

Gary
 
Start-->Admin Tools-->IIS Admin
Expand "Webites Folders" and right-click on "Default Website" and your IP should be listed
All the best!

:--------------------------------------:
fugitive.gif

[URL unfurl="true"]http://mostarnet.com[/url]

All around in my home town,
They tryin' to track me down...
 
Alexander, try GRC security test to provide you with more details: This test will verify your external IP and open ports. Run this security scan from your Exchange server, if it shows your ports 80 and 443 are open than your firewall is configured properly and you should be able to connect using the external IP identified during the test. If it shows ports 80 and 443 closed your firewall config is at fault.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top