Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!uwm.edu!ogicse!qiclab!techbook!kenh
From: kenh@techbook.com (Ken Haynes)
Newsgroups: comp.sys.novell
Subject: Re: How do you log in, really?
Message-ID: <1991Apr8.134751.14760@techbook.com>
Date: 8 Apr 91 13:47:51 GMT
References: <1991Apr4.102226.29452@kuhub.cc.ukans.edu>
Organization: TECHbooks of Beaverton Oregon - Public Access Unix
Lines: 38

In article <1991Apr4.102226.29452@kuhub.cc.ukans.edu> mcginnis@kuhub.cc.ukans.edu writes:
>Can someone tell me the process that is used followed when a workstation
>starts the network shell through the end of the process of a user
>logging in?  Or better yet, can you tell me a book that explains
>the processes?
>
>The workstation shell upon being loaded (net3 or net4) must send
>out a multicast packet looking for any fileserver.  The first one
>to respond must identify itself via the source address information
>in the reply packet.  At which time the shell would know where to
>go to find drive F: or whereever LOGIN.EXE is located.
>
You're right, when NETx is loaded it generates a GET NEAREST SERVER
broadcast packet and sends it out the wire.  All servers, & bridges
respond with a GIVE NEAREST SERVER packet directed to the sender. (You
can see this traffic if you set TRACK ON at the colon prompt on the
server.)  The attachment to the server takes place after the shell has
determined the nearest server. (Done by default as the first response
packet that reaches the workstation)  You can modify this in later versions
of the shell with the preferred server option.  The workstation determines
which drive to use for the first network drive by looking in the environment.
The LAST DRIVE= parameter in your config.sys file can modify this as well.
The workstation then sets up a logical drive attachment to the server at
the login subdir using this logical drive letter assignment.  Subsequent
running of the LOGIN.EXE program is done using standard DOS I/O from this
drive. (LOGIN subdir is allowed accessable by attached (not logged in) stations
Execution of the LOGIN.EXE program identifies the user to the server,
communicates the password, receives accept or deny from the server and
executes the system and user login scripts, to setup the drive mappings, etc.
.



-- 
******************************************************************************
* Ken Haynes, CNE                    | 1-900-PRO-HELP
* Technical Support Product Manager, 900 Support
* UUCP: {nosun, sequent, tessi} kenh@techbook