FR> Even if the userid's are the same, a domain account and 
 FR> a local account use different security identifiers. 
 FR> Without some type of privs, or modifications to the 
 FR> workstation's permissions, and assuming you're using 
 FR> roaming profiles, not mandatory ones, the doman account 
 FR> and local account will not share the same profile. 
 FR> Basically, if a DC is not available, you're hosed until it comes up.
 CH> Hmm...It doesn't -seem- to happen this way on my setup 
 CH> domain account, but when I log in I log into the domain, 
 CH> not the local account. If the DC is down, I get a message 
 CH> about the domain controller not being available and that 
 CH> the system is using cached settings, which is the desktop 
 CH> Frank. As you mention, I have the same local user and 
 CH> I get when I log into the domain (IE chris from 
 CH> CowboyCountry Domain). If I log in using the local account 
 CH> (IE Chris from Old Red) then I get different desktop.  The 
 CH> local user and the domain user are the same name with the 
 CH> way it works here.
 FR> When you log into the doamin, you are authenticated to 
 FR> a domain controller. If a DC is not available, there is 
 FR> no means of validating the user id and password. Hence, 
 FR> you cannot log into the domain.
NT 4.0, domain controller or not, after giving you an error message about not 
being able to find the domain controller, will indeed give you a cached user 
from  profile. It will also tell you that is is using a cached 
profile since the domain controller is not available along with the warning 
that changes to your profile won't be saved (or something to that effect).
 FR> Since you say you still can log into the domain, I have 
 FR> to ask if the domain has both a primary and backup 
 FR> domain controller. If yes, then all domain controllers 
 FR> would have to be down for the login to fail.
I didn't say I could log into the domain where there isn't a domain 
controller (PCD or BDC) available. I said that NT workstation will give you 
an error message about not being able to find a domain controller and will 
use a cached user profile (desktop settings etc). When a DC (-any dc- PDC or 
BDC) comes back on line, you will then have network access. The original 
thread of this message alluded that you couldn't even operate the computer 
locally with a domain user name and profile. I just wanted to point out that 
that isn't true. It should be obvious that without a domain controller you 
can't have access to network domain resources.
--- Maximus/NT 3.01b1
---------------