TIP: Click on subject to list as thread! ANSI
echo: nthelp
to: Gregg N
from: Rich
date: 2004-05-28 14:34:02
subject: Re: Default network ports for Windows XP

From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_05DB_01C444C0.D2ED1960
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   I looked them up in the sources.  There are other ways but that was =
the quickest for me.

Rich

  "Gregg N"  wrote in message =
news:40b7a815$1{at}w3.nls.net...
  So "ncacn_ip_tcp" is just the protocol used over the particular port. =
But how did you resolve the UUIDs into services? I could not find, e.g.,
    0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53
  in the registry.

  Gregg

    "Rich"  wrote in message news:40b7a32f{at}w3.nls.net...
       The UUIDs below identify the endpoints.  The port 1025 instances =
are associated with the task scheduler service.

    Rich

      "Gregg N"  wrote in message =
news:40b76b8f$1{at}w3.nls.net...
      I am not sure if I am running with the best arguments and =
switches, but the output of rpcdump and portqry are listed below. It =
looks like port 1025 is being used by something called NCACN

      RPCDUMP

-------------------------------------------------------------------------=
-

      C:\Program Files\Resource Kit>rpcdump /i /v
      Querying Endpoint Mapper Database...

      9 registered endpoints found.

      Collecting Data....  This may take a while.

                0    10   20   30   40   50   60   70   80   90  100
                |----|----|----|----|----|----|----|----|----|----|
                ...................................................

      ProtSeq:ncacn_ip_tcp
      Endpoint:1025
      NetOpt:
      Annotation:
      IsListening:YES
      StringBinding:ncacn_ip_tcp:192.168.50.99[1025]
      UUID:0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53
      ComTimeOutValue:RPC_C_BINDING_DEFAULT_TIMEOUT
      VersMajor 1  VersMinor 0
------=_NextPart_000_05DB_01C444C0.D2ED1960
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   I looked
them up in the =
sources. =20
There are other ways but that was the quickest for me.
 
Rich
 
"Gregg N" <greggn{at}invalid.invalid>">mailto:greggn{at}invalid.invalid">greggn{at}invalid.invalid> = wrote in=20 message news:40b7a815$1{at}w3.nls.net... So "ncacn_ip_tcp" is just the = protocol used over=20 the particular port. But how did you resolve the UUIDs into services? = I could=20 not find, e.g., 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53 in the registry. Gregg
"Rich" <{at}> wrote in message news:40b7a32f{at}w3.nls.net... The UUIDs below = identify the=20 endpoints. The port 1025 instances are associated with the = task=20 scheduler service. Rich
"Gregg N" <greggn{at}invalid.invalid>">mailto:greggn{at}invalid.invalid">greggn{at}invalid.invalid> = wrote=20 in message news:40b76b8f$1{at}w3.nls.net... I am not sure if I am running with the best arguments and = switches,=20 but the output of rpcdump and portqry are listed below. It looks = like port=20 1025 is being used by something called=20 NCACNRPCDUMP C:\Program Files\Resource = Kit>rpcdump /i=20 /vQuerying Endpoint Mapper Database... 9 registered endpoints = found. Collecting=20 Data.... This may take a while. =20 0 10 20 30 =20 40 50 60 70 = 80 =20 90 = 100 =20 = |----|----|----|----|----|----|----|----|----|----| = =20 ................................................... ProtSeq:ncacn_ip_tcp Endpoint:1025 NetOpt: Annotation: IsListening:YES StringBinding:ncacn_ip_tcp:192.168.50.99[1025] UUID:0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53 ComTimeOutValue:RPC_C_BINDING_DEFAULT_TIMEOUT VersMajor 1 VersMinor=20 0 ------=_NextPart_000_05DB_01C444C0.D2ED1960-- --- BBBS/NT v4.01 Flag-5
* Origin: Barktopia BBS Site http://HarborWebs.com:8081 (1:379/45)
SEEN-BY: 633/267 270
@PATH: 379/45 1 633/267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.