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> Frank. As you mention, I have the same local user and 
 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> 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> same password. S'why I know the user profile (desktop 
 CH> settings) are cached. Don't know how it would work with 
 CH> different passwords or users names that aren't in the 
 CH> local user database. But as described above, that is the 
 CH> way it works here.
When you log into the doamin, you are authenticated to a domain controller. 
If a DC is not available, there is no means of validating the user id and 
password. Hence, you cannot log into the domain.
Since you say you still can log into the domain, I have to ask if the domain 
has both a primary and backup domain controller. If yes, then all domain 
controllers would have to be down for the login to fail.
Even tho the "userid" is the same, a domain and local account have different 
SID's.  The differing SID's is the reason each account has it's own desktop 
... .
framsey@goodyear.com; frank.ramsey@fallsbbs.com;CNA;CNE;MCSE;PE
--- EZPoint V2.2
---------------