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

  • From: "adrian bolzan" <abolzan@xxxxxxxxxxxxxxxxxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Fri, 22 Apr 2005 16:41:30 +1000

Hi,

Thanks for the reply.
Of course!  I was not forwarding UDP packets, just TCP...

Now I just have to get the DNS/WINS config right and away I go...

Cheers,
Adrian
 

> -----Original Message-----
> From: Kamire, Thomas [mailto:Thomas.Kamire@xxxxxxxxxxxxxxxxx]
> Sent: Friday, 22 April 2005 3:48 PM
> To: [ExchangeList]
> Subject: [exchangelist] RE: OT (sort of): Setting up an OWA
> server in a DM Z
>
> http://www.MSExchange.org/
>
>  Why don't you open the 138/udp port in order for you to get
> to the DC?
>
> Regards
>
>
> -----Original Message-----
> From: adrian bolzan [mailto:abolzan@xxxxxxxxxxxxxxxxxxxxxxxxx]
> Sent: Friday, April 22, 2005 6:04 AM
> To: [ExchangeList]
> Subject: [exchangelist] OT (sort of): Setting up an OWA
> server in a DMZ
>
> http://www.MSExchange.org/
>
>
> Hi,
>
> This is sort of off-topic as I am stuck at setp 1 of building
> an OWA server.
>
> 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 = 192.168.2.2 IP address of
> Exchange server, which is also a DC = 192.168.1.5
>
> 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 = 192.168.2.5.
>
> Thus, communications from the 'OWA' server to the exchange
> server is sent to 192.168.2.5, with IP address and port
> forwarding to 192.168.1.5
> :
>
> 'OWA' server --> IP Alias on DMZ interface --> DC (with Exchange)
> 192.168.2.2 --> 192.168.2.5 --> 192.168.1.5
>
>
> 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.
>
>
>
> Cheers,
> Adrian
>
> ============================================================
> 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:
> 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:
> thomas.kamire@xxxxxxxxxxxxxxxxx To unsubscribe visit
> http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
> Report abuse to listadmin@xxxxxxxxxxxxxx
>
>
> DISCLAIMER:
> This message and any attachments are confidential and may be
> legally privileged or otherwise protected from disclosure.
> Although the necessary precautions have been taken, Kenya
> Airways does not accept legal responsibility for any damage
> whatsoever that is caused by viruses being passed or for the
> contents of this message.
> This message, and any attachments, are intended solely for
> use by the named addressee. If you are not the intended
> recipient, you must not copy them or disclose their contents
> to any other person. If you have received this message in
> error, please notify the sender by return e-mail and delete
> any attachments accompanying it immediately. "PLEASE NOTE
> THAT OUR OPERATOR NUMBER HAS CHANGED TO - +254-20-642 2000"
>
>
> ------------------------------------------------------
> 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: abolzan@xxxxxxxxxxxxxxxxxxxxxxxxx To
> unsubscribe visit
> http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
> Report abuse to listadmin@xxxxxxxxxxxxxx
>

============================================================
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.
============================================================


Other related posts: