Many users would not even be aware there was a problem. But there are issues. The PC brings up the users' desktop and enables the user to work on the PC but the logon scripts were not run, the home directory on the server is probably not available, and group policies were not applied. This is the default behavior and it may be what you want done. For it to work:
A higher security choice would be to display the error message and block logons to the workstation with cached credentials. Not workable in some environments. A variation on the theme is to display the message and have your users logon to the workstation using a local workstation account. I like this option least. You have to maintain duplicate accounts, domain and local, and the local account is rarely used and to be workable has a password that does not change. Not good. But again it depends on your organizations operational and security needs. I do not recommend this option.
To find out whether you were logged on to the domain:
- Type set at a commandline.
- Check the LOGONSERVER environmental entry.
echo USERNAME %logonserver%
to get a quick look at the logonserver.
If you have rights to view the event log, check the System log. If you were logged on using cached credentials, you see the following event:
Event ID 5719
No Windows NT or Windows 2000 domain controller is available for domain domain_name the following error occurred: There are currently no logon servers available to service the logon request.