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

Test the tool.

Scan your ports at grc.com and see if they are reported open or closed.

Are you behind a router with a firewall?

Jacee said:

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.

logicearth said:

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.

Antman said:

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

ccatlett1984 said:

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

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.

logicearth said:

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 ?

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.