Exchange Server Forums

Enabling Firewall

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2003] >> Server Security >> Enabling Firewall

Page: [1]

Message

<< Older Topic Newer Topic >>

Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM

TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!

Enabling Firewall - 9.May2008 5:52:55 PM

xgumbyx

Posts: 14
Joined: 1.Feb.2008
Status: offline

Hi all, I am trying to enable windows firewall on windows server 2003 with exchange 2003 and still talk to my exchange server from local computers running outlook 2003/2007. I've searched and searched and enabled all the ports I can think of but as soon as I turn on the firewall I lose connection with the exchange server. I've also tried to send an email with the firewall up and again the clients (outlook) can not connect to the server.

I've tried allowing tcp connections on the following ports 25, 110, 143, 379, 389, 390, 465, 636, 691, 993, 995, 1025, 1026, 1225, 1226, 1228, 3268, 3269. I'm sure not all of these are needed but these are the ports of interest that google has returned.

I've also went into the Advanced tab in windows firewall and checked off the IMAP3/4, SMTP, POP3 services but still no connections.

Can anyone suggest what I might be doing wrong and also which ports and protocols need to be allowed through? Thanks to anyone who responds.

Post #: 1

Featured Links*

RE: Enabling Firewall - 13.May2008 7:55:11 PM

Sembee

Posts: 3612
Joined: 17.Jan.2008
From: Somewhere near London, UK
Status: offline

Why are you trying to enable the firewall? I work on the principle if someone gets inside and can attack the server then you have bigger problems to worry about.

Exchange uses dynamic ports, so unless you have hacked around with that configuration then you will not get it to work. You also haven't enabled port 135, and with that port open you may as well not bother.

Simon.

_____________________________

Simon Butler,
Exchange MVP
Blog: http://www.sembee.co.uk/
Web: http://www.amset.info/
In the UK? Hire me: http://www.amset.co.uk/

(in reply to xgumbyx)

Post #: 2