Solved

Port 135 opened on Windows Server 2003

Posted on 2007-03-18
6
1,380 Views
Last Modified: 2013-12-04
Hi,

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 www.grc.com), 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,

Helder
0
Comment
Question by:HelderConde
[X]
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
6 Comments
 
LVL 33

Expert Comment

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

Accepted Solution

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

A high profile one was blaster virus:

http://www.computerhope.com/vinfo/blaster.htm

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

Author Comment

by:HelderConde
ID: 18744594
Hi,

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?

Thanks,

Helder
0
Get 15 Days FREE Full-Featured Trial

Benefit from a mission critical IT monitoring with Monitis Premium or get it FREE for your entry level monitoring needs.
-Over 200,000 users
-More than 300,000 websites monitored
-Used in 197 countries
-Recommended by 98% of users

 
LVL 33

Expert Comment

by:Busbar
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
0
 

Author Comment

by:HelderConde
ID: 18744630
Hi,

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

Expert Comment

by:Busbar
ID: 18744650
0

Featured Post

2017 Webroot Threat Report

MSPs: Get the facts you need to protect your clients.
The 2017 Webroot Threat Report provides a uniquely insightful global view into the analysis and discoveries made by the Webroot® Threat Intelligence Platform to provide insights on key trends and risks as seen by our users.

Question has a verified solution.

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

Security measures require Windows be logged in using Standard User login (not Administrator).  Yet, sometimes an application has to be run “As Administrator” from a Standard User login.  This paper describes how to create a shortcut icon to launch a…
OfficeMate Freezes on login or does not load after login credentials are input.
In this video we outline the Physical Segments view of NetCrunch network monitor. By following this brief how-to video, you will be able to learn how NetCrunch visualizes your network, how granular is the information collected, as well as where to f…
In this brief tutorial Pawel from AdRem Software explains how you can quickly find out which services are running on your network, or what are the IP addresses of servers responsible for each service. Software used is freeware NetCrunch Tools (https…
Suggested Courses

627 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