Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!aplcen!haven!udel!udccvax1!sun.acs.udel.edu!danderer
From: danderer@sun.acs.udel.edu (Dave Anderer)
Newsgroups: comp.dcom.lans
Subject: Re: In Novell 2.15, How do I Set the Default Server?
Message-ID: <6350@sun.acs.udel.edu>
Date: 4 Jan 90 00:59:03 GMT
References: <6895@pdn.paradyne.com>
Reply-To: danderer@sun.acs.udel.edu (Dave Anderer)
Organization: University of Delaware
Lines: 27


When a Novell workstation boots, it broadcasts looking for servers.  It 
attaches to the first server to reply.  The problems in this scheme are 
obvious, especially given that Novell name domains are server-specific.

The best workaround we've come up with here is to specify the server
explicitly as part of the login (LOGIN.EXE) execution.  For example,
to make sure I login on server athena, I do a:

		login athena/dave

Of course, there are ways to hide this so it looks invisible to the
user.  Off the top of my head, you might rename LOGIN.EXE to something
like STDLOGIN.EXE, and then create a batch file called LOGIN.BAT:

	@echo off
	stdlogin athena/%1

Not elegant, but something like that should work.

It doesn't really matter which server you get the SYS:\LOGIN directory
mapped from.  They should all be the same.
-- 
Dave Anderer
Academic Computing and Instructional Technology/Research and Development
University of Delaware
		"Sinners can repent; stupid is forever."