Link to home
Start Free TrialLog in
Avatar of HelderConde
HelderConde

asked on

Port 135 opened on Windows Server 2003

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
Avatar of Busbar
Busbar
Flag of Egypt image
Remove the Microsoft network client from the connection on the external interface of the server. you don;t need it any way
ASKER CERTIFIED SOLUTION
Avatar of James Montgomery
James Montgomery
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of HelderConde
HelderConde

ASKER

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
Avatar of Busbar
Busbar
Flag of Egypt image
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
Avatar of HelderConde
HelderConde

ASKER

Hi,

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