Re: nat/basic firewall
- From: "Ace Fekay [MVP]" <PleaseAskMe@xxxxxxxxxxxxxx>
- Date: Wed, 30 Apr 2008 17:29:50 -0400
In news:6A074D8B-A235-4BB9-A92B-AF15F2A2CFFF@xxxxxxxxxxxxx,
Leonard <Leonard@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
we are running 2 x std windows 2003 server
1 the domain controller (192.168.16.2) and the 2nd is the exchange
server 2003 (192.168.16.3)
we have open ports on NAT
80 is open and with ip address 192.168.16.2
443 is opena dn forwarded to the exchange server 192.168.16.3
remote desktop is pointing to 192.168.16.2
VPN is pointing to 192.168.16.2
we changed OWA fron port 80 to 443 as we know we cant forward to 2
different places
on our hard ware firewall, we have all the above ports open and they
are all forwarding to 192.168.16.2
we have only 1 external IP address
hope all that makes sence, if you need more info just ask
and
how do i turn of the NAT on my server is it just a simply of
unticking the box
thanks
Thanks for the extra info. I don't know why you have NAT on the server
enabled because your hardware firewall is handling that. You can remove it
in RRAS, assuming that is how it was configured, unless you used ICS? But if
you used ICS, you wouldn't have been able to setup RRAS for VPN. Just remove
the NAT instance in RRAS because you want to keep RRAS for the VPN
services. Assuming the DC only has one IP, good.
Remote Desktop (RDP) requires TCP 3389 opened to 192.168.16.2. I assume you
mapped port 3389 TCP on the hardware firewall?
As for the CRM, it sounds like something in the app is causing the issue.
Ace
.
- Follow-Ups:
- Re: nat/basic firewall
- From: Leonard
- Re: nat/basic firewall
- Next by Date: Re: nat/basic firewall
- Next by thread: Re: nat/basic firewall
- Index(es):
Relevant Pages
|