From: John Cuccia 

On Sun, 24 Oct 2004 12:06:03 -0500, "Glenn Meadows"
 wrote:

>Really?  Whenever I've tried that, not connected to the lan at boot time,  I
>get an error message such as Domain Controller Not found, or something such
>as that.

You need to login with the computer connected to the LAN first, to get the
credentials cached locally.

Here's a rather obtuse explanation from Microsoft:
http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/De
fault.asp?url=/resources/documentation/windows/xp/all/reskit/en-us/prcg_cnd_pom
w.asp
Logging On Using Domain Credentials The credentials that you use to
initially log on to your computer are also the credentials that are
presented to a domain when attempting to access a network resource.
Therefore, if your local logon and network authorization credentials
differ, you might be prompted to provide Windows 2000 domain credentials
each time you access a network resource. You can avoid this by logging on
to your computer by using your domain name, your domain user name, and your
domain password before you try to connect to a network resource. If you log
on without being connected to the network, Windows 2000 Server recognizes
that your credentials match a previous successful logon attempt, and you
receive the following message: "Windows cannot connect to a server to
confirm your logon settings. You have been logged on using previously
stored account information." Whenever you connect to your network,
your cached credentials are sent to your domain and you can access network
resources without having to provide your password again.




>I'll try that, after setting up a local account, where I've copied
>their desktops.

You shouldn't need a local account at all.

--- BBBS/NT v4.01 Flag-5