port 135 open

[Verwijderd]

Sinds gistren heb ik W2k pro draaien als gateway. Via grc.com ben ik erachter gekomen dat mijn port 135 open is. Ik heb Norton personal Firewall 2000 draaien, maar die port blijft open. Ik heb daarna handamtig een rule aangemaakt : Action : block
Direction : either
Protocol : TCP or UDP

Single sevice : 135

Maar helaas blijft port 135 open staan. Ik heb in de search gezocht in de hoop op antwoord, maar kon niks vinden. Kunnen jullie me helpen?

[Y0ur1]

linkje weg.

[Remco]

disable al je bindings op die bepaalde netwerkkaart.
(na ja, niet alle, maar, dhcp,server,wins enz...)

[Sick Nick]

Poort 135 word gebruikt door 'DCE Endpoint Resolution'

Dit heeft dus te maken met NetBIOS, schakel je windows bestandsdeling uit op je externe netwerkkaart en je problemen zouden weg moeten zijn.

[edit]

The default configuration of NT (Server and Workstation) starts a service on TCP port 135. It is widely known that connecting to this port and entering garbage characters can cause the machine to develop a high load average. After further experimentation, it was discovered that multiple connections of a similar type will eventually cause the service on this port to refuse further connections. The number of connections required to cause this denial of service varies. Our experiments found that as little as seventeen connections were all that were needed

Of te wel, op die poort kunnen ze je pc simpel dDossen

Nog wat info:

135 TCP loc-srv
Defined as a "Location Service" in RFC1060, pre-SP3 versions of Windows NT were susceptible to a denial of service attack on this port that would cause NT's rpcss.exe process to consume all available CPU cycles. The (easiest) recovery from this attack is to reboot your machine.
You should do one of several things: a) upgrade/patch your operating system to make sure it is not susceptible to this attack; b) firewall your system so that port 135 is not visible from the internet (check the Firewall section under the Security Zone for examples of good PC based firewall products). c) configure your router to block port 135; d) Install one of several monitoring packages on your PC that block this denial of service.

[Verwijderd]

Op donderdag 21 februari 2002 14:06 schreef Sick Nick het volgende:
Of te wel, op die poort kunnen ze je pc simpel dDossen

alleen op port 135 ja... overige porten reageert je machine nog wel op... dus alleen in een netwerk een issue... (aangezien je toch geen connectie wilt op port 135 vanaf internet... )

de tweede ja ach ik denk niet dat er nog iemand is met nt4 met sp2 of eerder!!! (en zo ja shame on you )

[Prozaq]

umm, wat een klote firewall? Ierdereen noemt wel leuke oplossing, maar je hebt toch een firewall om poorten te blokken zodat je ze niet op een andere manier hoeft uit te schakelen?

[Verwijderd]

_______________________________________________________
//Poort 135 word gebruikt door 'DCE Endpoint Resolution'
Dit heeft dus te maken met NetBIOS, schakel je windows bestandsdeling uit op je externe netwerkkaart en je roblemen zouden weg moeten zijn.//
_______________________________________________________

Hmm, ik ben nog erg onbekend met Win2k. Ik heb bij Local Area Connection bij TCP/IP properties de NetBios disabled. Is dit de bedoeling? Na disabled is port 135 nog steeds open.

[Captor]

Beetje klote layout maargoed.....

# Port 135 #
# #
# Run C:\WinNT\System32\Dcomcnfg.exe And Turn It Off. #
# #
# This can also be done with the registry key: #
# #
# HKEY_LOCAL_MACHINE\Software\Microsoft\OLE - The value "EnableDCOM" may be set to Y change this value to N to disable DCOM. #
# #
# Many programs "support" Distributed Communication (DCOM) but hardly ever use it. This includes such programs as Windows Media #
# #
# and Wordpad, which are designed to be used across a network. As you scan this tab, look for third-party applications that might #
# #
# actually require network support, as opposed to those that simply support it. To determine if these programs really require #
# #
# DCOM, you must disable it, run those programs, and see what happens. Note that it is probably only necessary to look at #
# #
# third-party programs here; Microsoft programs designed to run on a non-networked, stand-a-lone computer (Office, etc.) #
# #
# are usually written to support but not require DCOM. To disable DCOM, go to the Default Properties tab and uncheck the box #
# #
# labeled Enable Distributed COM on this computer. #
# #
# Reboot, and try running the third-party programs noted as above. Chances are good that everything will still run correctly. #
# #
# If not, go back and enable DCOM again. As you re-enable it, also go to the Default Protocols tab and remove all protocols except #
# #
# Connection-oriented TCP/IP. This won't make your system much safer, but it will reduce the number of connection methods #
# #
# you have to keep an eye on. #
# #
# If you do not have to re-enable DCOM again, then on the Default Protocols tab remove all protocols. You won't need them, #
# #
# and that should stop the OS from listening on Port 135 (unless you have other programs that are forcing it open; #
# #
# for example Task Scheduler. #
# #
# If your port 135 is still open try opening services, stopping Task Scheduler and Disabling it. #
# #
# Also go to your Ethernet Connection Protocols and Untick File And Printer Sharing for Microsoft Networks.

[F_J_K]

Captor schreef op 27 september 2002 @ 12:22:
Beetje klote layout maargoed.....

Beetje late reactie maar toch bedankt

Nuttige informatie, maar ik ben bang dat mensen niet door hebben dat het een beetje oud topic is en weer druk verder gaan posten. Slotje dus, ik hoor het wel via ICQ als mensen er wel door mee willen gaan.