How to close port 135 in Windows 7?

[mant]

In XP, a small utilities Windows Worm Door Cleaner can close port 135 and others.
It still can be use in Win7 to close some port except port 135.

How do you close port 135, what software?

[CloneRanger]

I'm on XP too, but try this



http://grc.com/freepopular.htm

[mant]

You rock! It works thanks.

[Brummelchen]

DONT disable DCOM service on Win7 - epic fail

with a router its not important if incoming call.
and if outgoing it should only LAN.
if outgoing on WAN (Web) there is something wrong on your system
(means - you have another - maybe malware - problem - not port 135)

[mant]

Is that Becky! Internet Mail using port 135?

[Brummelchen]

No, why should it?

PORT 135

Remote Procedure Call ( RPC) is a protocol that is used by the Windows
operating system. RPC provides a mechanism for communication between
processes available to the programs that are used on a computer that allows
to seamlessly run code on a remote system. The protocol itself is by the RPC
protocol by OSF ( Open Software Foundation ) are derived. There were,
however, addition of some Microsoft specific extensions.

[CloneRanger]

@ mant

Hi, great glad it worked for you

@ Brummelchen

DONT disable DCOM service on Win7 - epic fail

Hi, can you explain Exactly why you say that ?

Even though i have closed Port 135 with the GRC tool, the Actual DCOM Server Process Launcher service is still running on start up.

[Cudni]

blocking port 135 was valid once upon a time and for awhile during last decade and on XP. For Win7 it is simply not necessary

edit: blocking meaning disabling

[Brummelchen]

@CloneRanger
Pls have a look into the dependencies - its "only" RPC.
but without RPC a bunch of really important services fail too
win7 need to run itself. i had a strange RPC failure with XP
and the only solution was to reinstall (restore).

[CloneRanger]

@ Cudni

For Win7 it is simply not necessary

But why ?

@ Brummelchen

Pls have a look into the dependencies - its "only" RPC.
but without RPC a bunch of really important services fail too
win7 need to run itself. i had a strange RPC failure with XP
and the only solution was to reinstall (restore).

OK, will do

[TOMxEU]

Disabling port 135 in Windows 7 will disable Task Scheduler and by that everything related to it like Windows Update and so on. I also had to reinstall to get it working again.

[J_L]

Why didn't you have a disk image?

[TOMxEU]

I do not like it, a clean install is faster, cleaner and better, since I will instal updated aplications, drivers and so on.

[J_L]

A clean install is definitely not faster. Cleaner depends on the image. Better is arguable.

[TOMxEU]

When you restore an image, you still have to install everything again, since you would have an outdated stuff in it, and you will restore all the errors and junk as well.

[Critter2]

you must not know how to do imaging

[TOMxEU]

It is just the choise (for performance), I prefer a clean setup in ~2 houres (including defrag), than to run an imaging software backing up nonstop, slowing down the PC.

[J_L]

The image is as outdated as your last one. Which can be yesterday if you scheduled so.

2 hours is way more than backing up and restoring an image (40 minutes for me). It's not non-stop, only ~15 minutes, and you can still use your computer.

You really do seem to lack imaging experience.

[TOMxEU]

I did too much imaging actually. You have to include ALL the time, not just a restore, but also backing up (15 min a week), which takes much more time, then a clean setup. Anyway, I would never go for an image, you can never tell, that it is a clean image, especially after an infection, an unknown rootkit might have backed up as well.

[HAN]

If you turn off File and Printer Sharing, won't it kill activity for port 135 and 445 in Win 7??

[J_L]

Originally Posted by TOMxEU

I did too much imaging actually. You have to include ALL the time, not just a restore, but also backing up (15 min a week), which takes much more time, then a clean setup. Anyway, I would never go for an image, you can never tell, that it is a clean image, especially after an infection, an unknown rootkit might have backed up as well.

The backup time doesn't really count, because you can still use your computer then. It all depends on how often you backup and restore.

[Heimdall]

Originally Posted by HAN

If you turn off File and Printer Sharing, won't it kill activity for port 135 and 445 in Win 7??

You're thinking of NetBIOS (TCP/UDP ports 137 -139) which can be turned off by disabling NetBIOS over TCP/IP on the network adapter. Doing this, however, doesn't disable SMB direct hosting over TCP/UDP on port 445.

Port 135 is DCOM/RPC and although, in theory, one could disable this under XP/2003, it should not be disable under Windows 7, as there are a great many more dependencies.

[CloneRanger]

@ Heimdall

Thanks for the extra info

*

Why does MS always screws things up, even in 2011 ? You would think that they could design an OS by now that can work without leaving ports open !

[Fly]

Originally Posted by TOMxEU

Anyway, I would never go for an image, you can never tell, that it is a clean image, especially after an infection, an unknown rootkit might have backed up as well.

Of course you can be sure.

Just create an image of a known clean install, with all necessary drivers and updates, trusted programs, configured to your preferences.

Once in a while you can create a new image, which you may or may not fully trust.

That's what I do.

Reformatting my XP workstation, installing all service packs, updates, configuring it to my preferences, that would drive me crazy.

Creating a backup and creating an image are two very different things.

Restoring an image to my Win XP system takes about 10 minutes ... how long does it take you to reformat and reinstall everything ?

[Barthez]

I would like to respectfully remind you that topic of this discussion is How to close port 135 in Windows 7? not Pros and cons of creating system images.