Exchange Server Forums

OWA configuration on Windows 2003 SBS

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2003] >> Outlook Web Access >> OWA configuration on Windows 2003 SBS

Page: [1]

Message

<< Older Topic Newer Topic >>

Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM

TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!

OWA configuration on Windows 2003 SBS - 3.Jul.2008 7:07:01 AM

ftcom

Posts: 3
Joined: 20.Feb.2006
Status: offline

Hi, we have Microsoft Windows 2003 SBS Standard Edition on our only file server. I'm trying to setup access for Outlook Web Access so that it can be used externally. We also have a Draytek 2800+ Router, that we use for internet access and VPN.

At the moment I have Microsoft Exchange Installed, and also IIS6.0, however I've so far been unable to publish OWA to the outside world. I've been reading up different guides, but am a bit confused. Do I need to set our single server as a front end server to allow it to publish OWA? at the moment i'm assuming the server is a back end server by default during the Windows 2003 Server installation. we have SSL encryption setup. Is there a good guide we can follow on this website that allows easy configuration?

I'm also assuming this needs to be setup before we can start using Microsoft Exchange Activesync for using Microsoft Push on our Windows Mobile 6.0 Smartphones...

Any help would be greatly appreciated

Post #: 1

Featured Links*

RE: OWA configuration on Windows 2003 SBS - 4.Jul.2008 6:49:10 PM

Sembee

Posts: 3574
Joined: 17.Jan.2008
From: Somewhere near London, UK
Status: offline

You don't need a frontend server - although Microsoft's docs seem to read that way.

You only need to do three things to deploy it correctly.

1. Swap the self generated SSL certificate for a commercial certificate. This ensures there are no prompts for the SSL certificate from remote hosts. http://DomainsForExchange.net/ are currently doing trusted certificates for US$24/year.

2. Run the Connect to the Internet and Email wizard and ensure that the OWA and other settings that you need are enabled for public access.

3. Either enable uPNP on the router so that SBS can open the ports for you, or open the required ports on the device manually. The ports you need for full functionality are 25 (SMTP), 443 (HTTPS), 4125 for RWW and 1723 for VPN.
http://www.microsoft.com/technet/prodtechnol/sbs/2003/plan/gsg/appx_c.mspx

The above is presuming that you already have the DNS settings for your preferred host name setup. If not then you will need to do that first.

Simon.

_____________________________

Simon Butler,
Exchange MVP
Blog: http://www.sembee.co.uk/
Web: http://www.amset.info/
In the UK? Hire me: http://www.amset.co.uk/

(in reply to ftcom)

Post #: 2