Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!ittatc!dcdwest!sdcsvax!ucbvax!info-vax
From: SYSTEM@CRNLNS.BITNET
Newsgroups: mod.computers.vax
Subject: re: Another interesting one
Message-ID: <8602020716.AA29548@ucbvax.berkeley.edu>
Date: Sun, 2-Feb-86 02:16:16 EST
Article-I.D.: ucbvax.8602020716.AA29548
Posted: Sun Feb  2 02:16:16 1986
Date-Received: Sun, 2-Feb-86 11:58:47 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 27
Approved: info-vax@sri-kl.arpa

Subj:   re: Another interesting one

>
>... I've run across entries in netserver.log
>of the type '' connect request received from 1026::"0=USER" which turns
>out to be host 2. ...
>
>_H*

All DECnet node numbers are actually a 16 bit number.
The low order 10 bits are allocated to the node number within the area
(0-1023 decimal).
The high order 6 bits indicate the area number (0-61 decimal).
Unless you specify otherwise, under VMS v4.x all DECnet nodes are in area 1.
If you don't have a DECnet node in your local network database,
its node name will show up in log files as the area number multiplied
by 1024 added to the node number.

I trust that this explains what you are seeing.

Selden Ball

Cornell University, LNS        NYNEX: (607) 256-4882
Wilson Synchrotron Lab        BITNET: SYSTEM@CRNLNS
Judd Falls & Dryden Road        ARPA: SYSTEM%CRNLNS.BITNET@WISCVM.WISC.EDU
Ithaca, NY  14853                    (SYSTEM%CRNLNS.BITNET@WISCVM.ARPA)
                      PHYSnet/HEPnet: LNS61::SYSTEM (node 43.251/44283)