List Charter and FAQ at:-----Original Message-----
From: Briggs, Bruce [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 19, 2001 10:53 AM
To: MS-Exchange Admin Issues
Subject: RE: Firewall ConfigurationMany firewalls have 3 NICs. Often the 3rd NIC is referred to as the DMZ and it is protected by the firewall too. The inside NIC is often referred to as the trusted interface.Do you have users outside the firewall trying to access Exchange? If so, it is strongly recommended to not open Exchange up for direct access through a firewall. Consider using OWA or VPN clients to provide this access.Bruce-----Original Message-----
From: Zamanian, Behzad [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 19, 2001 12:25 PM
To: MS-Exchange Admin Issues
Subject: RE: Firewall ConfigurationHi Bruce,My Exchange is in my inside network and I use illegal IP address on the exchange and use a rule to change requests for the routable address to the illegal address behind the firewall. another word, it is in my DMZ network. What do you mean by moving it to the trusted interface? I have 2 NICs on the firewall, external one and internal card. my exchange's IP is 192.168.1.10 and the routable address for it is 128.200.129.10.Thanks,List Charter and FAQ at:-----Original Message-----
From: Briggs, Bruce [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 19, 2001 8:22 AM
To: MS-Exchange Admin Issues
Subject: RE: Firewall ConfigurationWhere is your Exchange server and your Outlook clients with respect to the firewall?If you have your Exchange server on the DMZ interface, consider moving it to your trusted interface.Most people feel that having Exchange on the DMZ is worse than having it on the trusted interface because of the ports, including RPC that need to be opened.Bruce Briggs
System Administration
State University of NY-----Original Message-----
From: Zamanian, Behzad [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 18, 2001 6:50 PM
To: MS-Exchange Admin Issues
Subject: Firewall ConfigurationHi everyone,
We use Raptor firewall on NT4 SP6. We also have Exchange 5.5 and outlook users for MAC and PC clients. Outlook uses RPC port 135 to handshake with exchange and as you may know, RPC port is a reserved port for any NT based firewall and Outlook conflicts with the firewall server on port 135.
Microsoft's solution to this is to create 3 registries for predefined ports so that outlook tries to connect on port 135 and automatically select the port you assigned. This solution still creates a few major problems:
MAC Outlook users can never connect
Sometimes remote users can not connect
Exchange connectivity is not stable. we had to reboot the server 2 times in one week with this setting.Any ideas?
Thanks,
Behzad Zamanian
List Charter and FAQ at:
Advancement Systems Architect
University Advancement, UCI
(949)824-8041 x. 48041
[EMAIL PROTECTED]
http://www.sunbelt-software.com/exchange_list_charter.htm
List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm
http://www.sunbelt-software.com/exchange_list_charter.htm
List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm
http://www.sunbelt-software.com/exchange_list_charter.htm
