Windows 2000 and NT 4.0
Hi all, I have a NT 4. 0 PDc running in our network. Recently, we acquire a 2000 svr. I plan to install Active Directory because I need to install SQL 2000 on it. I understand that once the W2k svr with AD is up , the users will have problems authenticating with the network because NT 4.
Hi all,
I have a NT 4.0 PDc running in our network. Recently, we acquire a 2000 svr. I plan to install Active Directory because I need to install SQL 2000 on it. I understand that once the W2k svr with AD is up , the users will have problems authenticating with the network because NT 4.0 is running too. One of the problems I could think of is Windows 2k will supercedes NT 4.0 during user authentication.
Is there a way where the users will log into and get authenticated by the NT 4.0 PDC and concurrently use the SQL 2000 server's resources?
Thanks.
I have a NT 4.0 PDc running in our network. Recently, we acquire a 2000 svr. I plan to install Active Directory because I need to install SQL 2000 on it. I understand that once the W2k svr with AD is up , the users will have problems authenticating with the network because NT 4.0 is running too. One of the problems I could think of is Windows 2k will supercedes NT 4.0 during user authentication.
Is there a way where the users will log into and get authenticated by the NT 4.0 PDC and concurrently use the SQL 2000 server's resources?
Thanks.
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
OK, you shouldn't need Win2K server/AD to use SQL 2000. Now, if you are setting up an AD anyway on one server, and you plan on keeping the existing NT 4 domain for the rest of the servers, you could *try* setting up a trust (I only fiddled with it once and it didn't work, but I didn't put a lot of effort into it) so the clients can authenticate from the NT Domain and pass into the AD. However, if a client is told to join the NT Domain, it won't just decide to force the user into logging on to the AD domain because it's there, so don't worry about that.
One other option is to just use mixed-mode authentication in SQL, and then give the users SQL logons rather than assigning logons to NTLM accounts. This would be even easier to setup, and you could use either DSNs on the client boxes or compile the authentication (consult local security protocols) into the application; such as an include in ASP.
One other option is to just use mixed-mode authentication in SQL, and then give the users SQL logons rather than assigning logons to NTLM accounts. This would be even easier to setup, and you could use either DSNs on the client boxes or compile the authentication (consult local security protocols) into the application; such as an include in ASP.
