I believe there is another way around this. If the DC is in fact, not available, simply disconnect the network cord and it will automatically use the local cached copy of the profile. It should [at the least] get him into the system. Rick -----Original Message----- From: windows2000-bounce@xxxxxxxxxxxxx [mailto:windows2000-bounce@xxxxxxxxxxxxx] On Behalf Of SEspeseth@xxxxxxxx Sent: Thursday, October 02, 2003 5:24 PM To: windows2000@xxxxxxxxxxxxx Subject: [windows2000] Re: Domain not available You get that message when the account you are using does not have a locally cached copy and the computer cannot connect to the domain controller. The local cached profile can't be helped at that point so make sure it has a connection to the dc. Make sure the machine is on the network(look in the local dhcp server and ping the address from another machine), look in the dns server to see if it is registering properly(this verifys that the computer has the correct dns settings and can resolve the dc), and then check to see if global catalog server is up. You really should have a local admin account setup on those machines. -----Original Message----- From: Jonathan Kadoo [mailto:jkadoo@xxxxxxxxxxxxxx] Sent: Thursday, October 02, 2003 2:38 PM To: Windows2000@xxxxxxxxxxxxx Subject: [windows2000] Domain not available I've got an issue I haven't seen before. I have a Windows 2k Pro machine that is giving an error when you try to sign in "The system cannot log you on now because the domain "DOMAINNAME" is not available." Unfortunately there is no option to log onto the local machine like you would normally have. I have looked on Ms's site but I haven't found anything that helpful. Anyone seen this? Any ideas would be greatly appreciated. Jonathan