Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm currently tightening up our Windows 2008 R2 Web server's software firewall rules. There are 4 open ports which I am not sure whether I need them or not:

Name: Windows Backup (RPC), Port: RPC Dynamic Ports
Name: Windows Backup (RPC-EPMAP), Port: RPC Endpoint Mapper
Name: Windows System Resource Manager (DCOM-In), Port: 135
Name: Windows System Resource Manager (TCP-In), Port: RPC Dynamic Ports
  • Regarding windows backup ports: I guess I don't need these since the server simply backups itself onto a local hard disk and management of backups is done through remote desktop
  • Regarding Windows System Resource Manager: I am not sure what this is or why I would need open ports to it.

Should I leave the ports open, or should I close them?



share|improve this question
which firewall? the built in one that comes with the OS? or a hardware fw thats public facing? – Nick Kavadias Jan 26 '11 at 12:57
@Nick Kavadias: The one that comes with the OS. – Adrian Grigore Jan 26 '11 at 13:21
up vote 1 down vote accepted

If your server is a part of a LAN network with other trusted Microsoft computers, allowing these ports on the LAN side is safe. But if it's your only server and if this firewall is the only one between you and Internet, keeping them opened is a kind of security flaw.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.