Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17


Port 135 opened on Windows Server 2003

Posted on 2007-03-18
Medium Priority
Last Modified: 2013-12-04

I'm running a Windows Server 2003 with Windows Firewall. It runs IIS as FTP and HTTP server.

Instead of opening ports 21 and 80 at the firewall, I decided to add "inetinfo.exe" (IIS) to the exception list - which should be about the same.

However, I noticed that when I do that and run Shields up test (at, the system has port 135 opened. If I take inetinfo.exe out of the exception list, the port closes.

What I'd like to know is: is there a problem in leaving port 135 opened on the server? Are there any security issues related to that?

Thanks in advance,

Question by:HelderConde
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
LVL 33

Expert Comment

ID: 18744546
Remove the Microsoft network client from the connection on the external interface of the server. you don;t need it any way
LVL 15

Accepted Solution

JimboEfx earned 2000 total points
ID: 18744549
Lots of issues (google this to find lots of results).

A high profile one was blaster virus:

Follow best practices and only open what you absolutely need too, even if it requires a bit more effort.

Author Comment

ID: 18744594

BusBar suggested: "Remove the Microsoft network client from the connection on the external interface of the server. you don;t need it any way"

How can I do  that?


Cyber Threats to Small Businesses (Part 1)

This past May, Webroot surveyed more than 600 IT decision-makers at medium-sized companies to see how these small businesses perceived new threats facing their organizations.  Read what Webroot CISO, Gary Hayslip, has to say about the survey in part 1 of this 2-part blog series.

LVL 33

Expert Comment

ID: 18744602
open control panel
open network connection
click on the external interface
lick properties
then remove the client of microsoft network and file and print sharing

Author Comment

ID: 18744630

I did that. But the port remaind opened after I re-run Shields Up.
LVL 33

Expert Comment

ID: 18744650

Featured Post

On Demand Webinar - Networking for the Cloud Era

This webinar discusses:
-Common barriers companies experience when moving to the cloud
-How SD-WAN changes the way we look at networks
-Best practices customers should employ moving forward with cloud migration
-What happens behind the scenes of SteelConnect’s one-click button

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

On July 14th 2015, Windows Server 2003 will become End of Support, leaving hundreds of thousands of servers around the world that still run this 12 year old operating system vulnerable and potentially out of compliance in many organisations around t…
SHARE your personal details only on a NEED to basis. Take CHARGE and SECURE your IDENTITY. How do I then PROTECT myself and stay in charge of my own Personal details (and) - MY own WAY...
This course is ideal for IT System Administrators working with VMware vSphere and its associated products in their company infrastructure. This course teaches you how to install and maintain this virtualization technology to store data, prevent vuln…
In this video, Percona Director of Solution Engineering Jon Tobin discusses the function and features of Percona Server for MongoDB. How Percona can help Percona can help you determine if Percona Server for MongoDB is the right solution for …
Suggested Courses

670 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question