Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: blocking some ports


08 Oct 2009   #1
beg4mercy

Windows 7 Rtm x64
 
 
blocking some ports

Hello all,

Im using windows 7 RTM x86
I want to close some opened ports.These ports are 135 and 445.
So, I try to close/block these ports using Windows Firewall. ( with advanced settings )


I created inbound rule for closing port 135(TCP) (as you can see attached screenshot )
Also I applied same step for UDP.

but , when I scan my pc's opened ports using Net Tools 5 program ( open port scanner tool ) , it found port 135 as open.
I created rule and blocked/closed port 135 but Net Tools says : Port 135 still open.

This is risky for me.
How can I close this port correctly ?

Note : Im using MSE for Antivirus security.

Thanks a lot




Attached Thumbnails
-capture.png  
My System SpecsSystem Spec
.

08 Oct 2009   #2
Antman

 

Test the tool.

Scan your ports at grc.com and see if they are reported open or closed.
My System SpecsSystem Spec
08 Oct 2009   #3
logicearth

Windows 8.1 Pro (x64)
 
 

Are you behind a router with a firewall?
My System SpecsSystem Spec
.


08 Oct 2009   #4
Jacee
Microsoft MVP

Windows 7 Ultimate 32bit SP1
 
 

Quote:
Ports 135 and 445 are used by Windows for sharing files and printers and finding each other in a Local Area Network.
Did you run Windows update after installing your version of Win7?
My System SpecsSystem Spec
09 Oct 2009   #5
beg4mercy

Windows 7 Rtm x64
 
 

Quote   Quote: Originally Posted by Jacee View Post
Quote:
Ports 135 and 445 are used by Windows for sharing files and printers and finding each other in a Local Area Network.
Did you run Windows update after installing your version of Win7?
Yes I installed all necessary updates from Windows Update.
I think , port 135 can be risky if it open because some worms using the port 135 for attack.

Quote   Quote: Originally Posted by logicearth View Post
Are you behind a router with a firewall?
no im not behind a router, im in home network.Only Windows Firewall working as a firewall.

Quote   Quote: Originally Posted by Antman View Post
Test the tool.

Scan your ports at grc.com and see if they are reported open or closed.
I didnt find a port scanner tool at this site.Also I scanned my open ports via another online port scanner.

Results are attached.
But Im confused.When I open cmd and type ''netstat -an'' it says : port 135 still open...
but I scanned the same port via another online port scanner , it says : ''your ip address isnt responding on port 135''


Thank you for your replies


Attached Images
  
My System SpecsSystem Spec
09 Oct 2009   #6
ccatlett1984

 

most online port scanning tools are for checking for http(or some other service) being active on a port, not just if its open.
My System SpecsSystem Spec
09 Oct 2009   #7
beg4mercy

Windows 7 Rtm x64
 
 

Quote   Quote: Originally Posted by ccatlett1984 View Post
most online port scanning tools are for checking for http(or some other service) being active on a port, not just if its open.
I scanned again the open ports via LANguard Port Scanner tool and Net Tools( these are application, not online tools ) , port 135 seems still open.

my Windows Firewall inbound rule does not work correctly.
Thanks
My System SpecsSystem Spec
09 Oct 2009   #8
logicearth

Windows 8.1 Pro (x64)
 
 

What does the port scan here: https://www.grc.com/x/ne.dll?bh0bkyd2 say?

Also are you sure the port is open to remote access? I.e., on a different computer does a port scan show the port is open? Because, from what I'm seeing in my own testing, the port is closed to remote clients.
My System SpecsSystem Spec
09 Oct 2009   #9
beg4mercy

Windows 7 Rtm x64
 
 

Quote   Quote: Originally Posted by logicearth View Post
What does the port scan here: https://www.grc.com/x/ne.dll?bh0bkyd2 say?

Also are you sure the port is open to remote access? I.e., on a different computer does a port scan show the port is open? Because, from what I'm seeing in my own testing, the port is closed to remote clients.
Hm ,I scanned my pc from my another machine with Nmap 5.0.It says : ''port 135 closed''

When I scan my pc from another machine , Im seeing the port 135 is closed but when I scan my pc from local port 135 seems like open.

I mean, port 135 closed to inbound connections.

but that is interesting because I deleted all port 135 blocking rules from my Windows Firewall before last port scan process.
port 135 is closed to inbound connections but there arent any rules for blocking port 135 in Windows Firewall right now

Does Windows Firewall automatically close all ports for inbound connections when it up ?
My System SpecsSystem Spec
09 Oct 2009   #10
logicearth

Windows 8.1 Pro (x64)
 
 

Yes all Inbound connection are denied, if there is no rule for allowing the port to be open. Inbound by default is blocked to unsolicited request.
My System SpecsSystem Spec
Reply

 blocking some ports




Thread Tools



Similar help and support threads for2: blocking some ports
Thread Forum
Solved Front USB ports not working, but rear USB ports work Hardware & Devices
USB 3.0 ports refuse to work as USB 3.0 ports Hardware & Devices
RSA Key Blocking is Here Security News
Help on blocking common trojan ports System Security
Solved IE9 - Blocking Ads? Browsers & Mail

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 08:36 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App