Windows Server 2000/2003 Thread, Firewall at last... in Technical; Server 2003 R2 32/64Bit
I'm SLLLOWLY turning on the firewall for my servers (leaving the DCs for last) I was ...
3rd March 2011, 02:46 PM #1
Firewall at last...
Server 2003 R2 32/64Bit
I'm SLLLOWLY turning on the firewall for my servers (leaving the DCs for last) I was wondering if I should block 135 and 139 (and or disable NetBIOS) I've blocked it on my backup server with no ill affects (yet)...
I get a little confused with the windows firewall, if I block file and print sharing it doesn't stop me accessing another servers files but does stop my files from being shared. So do I need port 25 open for a server to send an email through to exchange? (for local alerts and the such...)
IDG Tech News
6th March 2011, 06:08 PM #2
You are disabling file and print on that server, not for that user logged on that server accessing other servers files and share if this isn't disabled.
For exchange you need 25 for communication via SMTP. If use POP3 or IMAP or http for exchange then you have to open these too. In addition to a number of others ports for DNS, LDAP, replication etc...there are a few.
Why are you deploying a firewall on your server internally?
6th March 2011, 10:20 PM #3
I have to ask this aswell?
Originally Posted by sukh
I simply just keep a firewall between my network and the wan - i have linux boxs outside the firewall (As they arn't much risk with secure passwords etc).
But internally i leave them off as most virus's etc just spread using ports that are open (i.e file and printer sharing ports 135/139) so not much point
By kevin_lane in forum Windows Server 2008 R2
Last Post: 27th October 2010, 02:49 PM
By Chuckster in forum Windows Server 2000/2003
Last Post: 27th July 2009, 11:42 AM
By networkmanager in forum Wireless Networks
Last Post: 1st August 2008, 06:47 PM
By ptrainor1 in forum Wireless Networks
Last Post: 22nd October 2006, 10:34 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)