RE: OT (sort of): Setting up an OWA server in a DMZ

  • From: "Thomas W Shinder" <tshinder@xxxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Fri, 22 Apr 2005 07:01:14 -0500

Hi Adrian,

Are you using an ISA firewall? If so, the entire step by step details
are in the ISA/Exchange Deployment Kit at


Tom and Deb Shinder's Configuring ISA Server 2004
MVP -- ISA Firewalls

-----Original Message-----
From: adrian bolzan [mailto:abolzan@xxxxxxxxxxxxxxxxxxxxxxxxx] 
Sent: Thursday, April 21, 2005 10:04 PM
To: [ExchangeList]
Subject: [exchangelist] OT (sort of): Setting up an OWA server in a DMZ


This is sort of off-topic as I am stuck at setp 1 of building an OWA

I am trying to configure a new server to act as an OWA server.  It is
located in our DMZ.
We do not use ISA server...

IP address of 'OWA' server =
IP address of Exchange server, which is also a DC =

The way our firewall works is to set an alias on the DMZ interface, and
use IP address and Port forwarding.
The alias on the DMZ interface =

Thus, communications from the 'OWA' server to the exchange server is
sent to, with IP address and port forwarding to

'OWA' server --> IP Alias on DMZ interface --> DC (with Exchange) --> -->

My first problem is that when I try to join the OWA server to the domain
across the firewall I receive an error stating that I am trying to
connect to a closed port (presumably on the exchange DC).  All of the
appropriate filters are in place on the firewall to allow the
communication.  The closed port is 138/UDP.  This suggests that I need
to configure the DC to allow connections from the DMZ subnet.

Any pointers on where I would find info on how to allow this
communication would be appreciated. 


IMPORTANT - This email and any attachments is confidential.
If received in error, please contact the sender and delete
all copies of this email. Please note that any use,
dissemination, further distribution or reproduction of this
message in any form is strictly prohibited. Before opening or
using attachments, check them for viruses and defects.
Regardless of any loss, damage or consequence, whether caused
by the negligence of the sender or not, resulting directly or
indirectly from the use of any attached files, our liability
is limited to resupplying any affected attachments. 

Any representations or opinions expressed in this email are
those of the individual sender, and not necessarily those
of the Capital Transport Services.

List Archives:
Exchange Newsletters:
Exchange FAQ:
Other Internet Software Marketing Sites:
World of Windows Networking:
Leading Network Software Directory:
No.1 ISA Server Resource Site:
Windows Security Resource Site:
Network Security Library:
Windows 2000/NT Fax Solutions:
You are currently subscribed to this Discussion List as:
To unsubscribe visit
Report abuse to listadmin@xxxxxxxxxxxxxx

Other related posts: