home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!cs.utexas.edu!qt.cs.utexas.edu!yale.edu!think.com!spool.mu.edu!agate!ucbvax!CARLETON.EDU!DDIEHL
- From: DDIEHL@CARLETON.EDU ("Systems/Network Technician, x4281")
- Newsgroups: comp.os.vms
- Subject: Re: TT_AccPorNam field remains null on a SHOW USERS output ?
- Message-ID: <01GSXBC488QQ8ZDWNC@carleton.edu>
- Date: 30 Dec 92 17:24:24 GMT
- Sender: daemon@ucbvax.BERKELEY.EDU
- Distribution: world
- Organization: The Internet
- Lines: 24
-
- Carl@SOL1.GPS.CALTECH.EDU writes
- >In article <gurman.725601335@umbra.gsfc.nasa.gov>,
- >gurman@umbra.gsfc.nasa.gov (Joseph B. Gurman) writes:
- >> For what it's worth, logged onto a VMS V5.5-2 system with UCX V2.0
- >>via
- >>Telnet, my TT_ACCPORNAM is (quotes included as delimiters) "Host:
- >>128.183.57.149 Port: 47473" Your mileage may vary.
- >
- >Hmmm. 47473 doesn't sound much like any port name I've ever heard of. Maybe
- >the "47473" is the beginning of the hexadecimal representation of the port
- >name? That'd be GGsomething. Just a wild-assed guess.
-
- 47473 here is the number of the TCP port on the remote host. While the port on
- the local host is, of necessity, port 23 (the Well Known Service port for
- telnet), the port on the remote host can be anything between 1024 (the top of
- the reserved WKS range) and 2^16. It is not unusual for port numbers under
- certain implementations of TCP/IP to fall high in this range, although
- barkochba.gsfc.nasa.gov (the DNS name for 128.183.57.149) is not responding to
- queries right now, making it hard to tell which TCP/IP they are running.
-
- -Dave Diehl
- Systems/Network Technician
- Carleton College
-
-