You could also try enabling the "Cached Credentials" option on the W2K Clients, that way if the DC is down in the lab for any reason, they will be able to logon with the cached credentials and will have the same permissions that they had at the last successful login.
Dave -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Tony Murray Sent: Friday, January 04, 2002 10:07 AM To: [EMAIL PROTECTED] Subject: Re: [ActiveDir] NT4.0 authentication Yes you will need a DC for the Win2K clients to authenticate. Bring up the new DC and transfer the required FSMO roles before shutting down your other DC. Tony ---------- Original Message ---------------------------------- From: Scott Krall <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] Date: Fri, 4 Jan 2002 09:06:26 -0500 In my test lab I have (1) Win2k DC running AD, (1) NT 4.0 BDC, (2) Win2k clients and (1) NT 4.0 client. The Win2k clients are a part of AD and when I shutdown the Win2k DC my 2k clients can't log on. I've read where this is normal because the Win2k clients joined AD and now use Kerberos so I'm assuming I must have another Win2k server running so these clients can logon? If that's the case does this other Win2k server need AD running on it? List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
