site Search:


 
    All Forums Hot Topics Gallery






how-to block ads


 
Search Topic:
Uniqs:
366
Share Topic
Post a:
Post a:
AuthorAll Replies


Philmatic
Premium
join:2000-07-15
Elk Grove, CA

Port 135 is not netbios.

The article is wrong, port 135 is not NetBIOS, those are reserved for 137-139.

Port 135: Microsoft's DCOM (Distributed, i.e. networked, COM) Service Control Manager (also known as the RPC Endpoint Mapper) uses this port in a manner similar to SUN's UNIX use of port 111. The SCM server running on the user's computer opens port 135 and listens for incoming requests from clients wishing to locate the ports where DCOM services can be found on that machine.


nil
Java Geek
join:2000-11-27
kudos:1
Host:
Webmasters and Dev..
Forum Feature Requ..

The article isn't wrong.. it's just not as detailed as your post.. most security people lump 135/tcp in with NETBIOS even though it's not strictly the same thing.
--
Life is too short to be boring



Philmatic
Premium
join:2000-07-15
Elk Grove, CA

Oh okay, I take it it's now part of the NetBIOS suite?



Steve
I know your IP address
Consultant
join:2001-03-10
Yorba Linda, CA
kudos:5

said by Philmatic:
Oh okay, I take it it's now part of the NetBIOS suite?
It's "close enough" - though it's not strictly part of NETBIOS in the sense of file mapping and the like, it's so intricately related to "windows networking" that most of us have long considered RPC portmapper to be part of NETBIOS. Perhaps this is sloppy, but not much.

Steve
--
Stephen J. Friedl * Security Consultant * Tustin, California USA * my web site

Monday, 04-Jun 19:09:48 Terms of Use & Privacy | feedback | contact | Hosting by nac.net - DSL,Hosting & Co-lo
over 12.5 years online © 1999-2012 dslreports.com.
Most commented news this week
Hot Topics