>FYI, the so-called DMZ of the Netscreen doesn't mean that it's wide open. >You can set rules and NAT addressing on that port as well, and we have. >Only Email-related traffic is allowed through this port
I believe all firewall DMZ zones are not wide open. You must configure rules. >That strange thing about this is that this server has been running for >several months without issue. I half wonder if one of Microsoft's patches >didn't re-enable the service. Why wouldn't it have caused a problem before >if it was never disabled?! We've installed all but Windows 2000 SP3...as we >have been leary about this service. I've had mixed results in >updating...problems with services not starting due to incorrect passwords >for the service start. Any problems from others with SP3? A client of ours had TrendMicro InterScan installed on the same server as Exchange. Exchange was working great for about 6 months with many restarts. Then, on one restart, no mail was moving in or out. Turns out that the company that installed the server and configured it, (they are no longer providing support to that client,) had Exchange and InterScan both listening on port 25. Only thing we, TrendMicro and Microsoft came up with is that all the other times the Exchange SMTP server always started before InterScan, and therefore worked. This time, some how InterScan started first and therefore would not let Exchange SMTP server start. John Tolmachoff IT Manager, Network Engineer RelianceSoft, Inc. Fullerton, CA 92835 www.reliancesoft.com To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
