RE: Help with Configuration of Accessing OWA 2003
- From: Tee Darling <tee.darling77@xxxxxxxxx>
- To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
- Date: Tue, 11 Jan 2005 13:47:15 -0500
Well, to put it in the simplest term, my Exchange server is inside the
private network. That means it's behind the Routing and Remote Access
(RRAS) machine. No one can hit it direct from the Internet.
NAT has been setup on the RRAS interface and as you may know, NAT
allows you to redirect a particular port from the router to a
particular port on a particular computer on the internal network. I
have configured the NAT in such a way to refer any SMTP (25) and any
HTTP (80) incoming communications on the router's port 25 and 80 to
port 25 and 80 on my Exchange server. I can send and receive emails
fine and that tells me that port 25 is working like a champ.
The problem again is I cannot connect through OWA. OWA works fine
inside the internal network. How do I configure it to work from
outside the network? Thanks again for any help out there...
T
On Tue, 11 Jan 2005 11:27:03 +0200, Dolly Bareqet <dolly@xxxxxxxxxxxx> wrote:
> http://www.MSExchange.org/
>
> Hi,
>
> What exactly is your network architecture?
> Exchange inside the LAN? IP address (internal?)
> Sometimes opening port 80 on the FW is not enough.
>
> Dolly
>
> -----Original Message-----
> From: Tee Darling [mailto:tee.darling77@xxxxxxxxx]
> Sent: Tuesday, January 11, 2005 4:40 AM
> To: [ExchangeList]
> Subject: [exchangelist] RE: Help with Configuration of Accessing OWA
> 2003
>
> http://www.MSExchange.org/
>
> My firewall has been configured to allow access to port 80 on the
> Exchange server and that's how I am able to receive emails and send
> emails out. But when I try to connect from the outside my network to my
> server through http://email.mycompany.net/exchange, that's when I
> receive the message I talked about. I haven't configured SSL yet on my
> Exchange server yet.
>
> Is there any step by step instructions to configure IIS for OWA to work?
> If anyone knows about any link for this information, please help out.
> Thanks.
>
> T
>
> On Tue, 11 Jan 2005 11:35:59 +1100, AdrianB
> <adrianb@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
> > http://www.MSExchange.org/
> >
> >
> > > -----Original Message-----
> > > From: Tony.Afriyie [mailto:Tony.Afriyie@xxxxxxxxxxxx]
> > > Sent: Tuesday, 11 January 2005 9:59 AM
> > > To: [ExchangeList]
> > > Subject: [exchangelist] Help with Configuration of Accessing OWA
> > > 2003
> > >
> > > http://www.MSExchange.org/
> > >
> > > I am currently running Exchange 2003 on Windows Server 2003.
> > > Routing and Remote Access has been configured on my Windows Server
> > > 2003 that is connected to my cable modem. Installed on this gateway
> > > server is DynSite for Windows version 1.11. As you may know, this
> > > DynSite for Windows application captures my dynamic IP address from
> > > my cable company and send it to EsayDNS DNS servers and make it look
>
> > > like I have a static IP address. I have no problem sending and
> > > receiving emails. My Exchange Server 2003 server has a private IP
> > > address
> > > (192.168.1.8) and sits inside my internal network.
> > >
> > > Now my problem is, how do I configure Outlook Web Access
> > > (OWA) to work on this Exchange server so that users can connect to
> > > it from the outside. OWA works fine within the internal network but
> > > every time I try to connect from the outside to the Exchange Server
> > > 2003 I get "Error 502.. remote server is not responding or down".
> > > Microsoft Knowledge Base and some other areas on the Internet
> > > haven't been able to help configure or troubleshoot this incident.
> > > Has anyone out ther been able to make this kind of configuration
> > > work before and how? Also I would like to map
> > > http://email.mycompany.net/exchange to my Exchange server so I can
> > > type that in whenever I try to access the OWA from outside. How do I
>
> > > configure that in Excahnge 2003?
> > >
> > > Any help will be appreciated. Thanks.
> > >
> > > T
> > >
> >
> > Hi Tony,
> >
> > Does your firewall allow access, and port forward, to the ports 80 and
>
> > 443, to the Exchange server?
> > When connecting from the outside, what URL are you using to connect to
> OWA?
> >
> > If that URL is valid and if the firewall is not blocking access to
> > Exchange and ports 80/443 are forwarded correctly, then it sounds like
>
> > IIS is not configured correctly for OWA.
> >
> > Cheers.
> > Adrian
> >
> >
> > ------------------------------------------------------
> > List Archives:
> > http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
> > Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
> > Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
> > ------------------------------------------------------
> > Other Internet Software Marketing Sites:
> > World of Windows Networking: http://www.windowsnetworking.com Leading
> > Network Software Directory: http://www.serverfiles.com
> > No.1 ISA Server Resource Site: http://www.isaserver.org Windows
> > Security Resource Site: http://www.windowsecurity.com/ Network
> > Security Library: http://www.secinf.net/ Windows 2000/NT Fax
> > Solutions: http://www.ntfaxfaq.com
> > ------------------------------------------------------
> > You are currently subscribed to this MSEXchange.org Discussion List
> > as: Tee.Darling77@xxxxxxxxx To unsubscribe visit
> > http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
> > Report abuse to listadmin@xxxxxxxxxxxxxx
> >
>
> ------------------------------------------------------
> List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
> Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
> Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
> ------------------------------------------------------
> Other Internet Software Marketing Sites:
> World of Windows Networking: http://www.windowsnetworking.com Leading
> Network Software Directory: http://www.serverfiles.com
> No.1 ISA Server Resource Site: http://www.isaserver.org Windows Security
> Resource Site: http://www.windowsecurity.com/ Network Security Library:
> http://www.secinf.net/ Windows 2000/NT Fax Solutions:
> http://www.ntfaxfaq.com
> ------------------------------------------------------
> You are currently subscribed to this MSEXchange.org Discussion List as:
> dolly@xxxxxxxxxxxx To unsubscribe visit
> http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
> Report abuse to listadmin@xxxxxxxxxxxxxx
>
> ------------------------------------------------------
> List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
> Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
> Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
> ------------------------------------------------------
> Other Internet Software Marketing Sites:
> World of Windows Networking: http://www.windowsnetworking.com
> Leading Network Software Directory: http://www.serverfiles.com
> No.1 ISA Server Resource Site: http://www.isaserver.org
> Windows Security Resource Site: http://www.windowsecurity.com/
> Network Security Library: http://www.secinf.net/
> Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
> ------------------------------------------------------
> You are currently subscribed to this MSEXchange.org Discussion List as:
> Tee.Darling77@xxxxxxxxx
> To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
> Report abuse to listadmin@xxxxxxxxxxxxxx
>
Other related posts:
