Unable to login to network when using back up domain
We recently test the network setup of our DR site. Our DR site has the same domain name like the one in main office, we also have active directory although both are not updated or does not have similar entry to those server that we have in main office. Im using windows 7 pro and also 2 of my colleagues who went in DR site. We are able to login to ur machine using cache credentials, but once we get connected to the network of the DR site and then we restart our machine, we can no longer connect. But one of my colleague who uses windows xp is still able to log in using his cache credentials and i remember last year when we do the same test, we didnt have any problem like this and all of us are using windows xp during that time I just want to know how is the cache credentials of windows XP and windows 7 behave in this scenario or in general. Is there a way that we can force windows 7 to use its cache credential when authenticating? Can i reconfigure it?
July 26th, 2011 1:33am

Just to clarify few things, on the DR site the user is connecting to a different physical DC but the same domain name like the one in the main office. The users are able to login however when they locked their computers and unlock it and type in the password they cant login anymore. This happens to machine that uses windows 7 but, we have not encountered the issue from users who users who is using windows XP.
Free Windows Admin Tool Kit Click here and download it now
July 26th, 2011 2:53am

Hi, You can try to open credential manager: Click start and input credential manager in search box and press enter. Then modify or edit the credential of domain. Hope that helps. Regards, Leo Huang Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
July 28th, 2011 3:19am

Hi Leo, Thanks for the reply, it has nothing to do with the credential details, because even if i have the correct details, im still not able to authenticate on the other DC, one reason could be that even though this DC is the same as the one that we have from our main office it may not contain the same logon details with the one being use in the main office, or it could be that a particular user is not yet created on the DC located in the DR site. the thing that puzzles me is how come the users that uses XP was able to log in to their machine and i assume it uses its cache profile, while the users using windows 7 was not able to use its cache profile. To illustrate further: *****Main office Domain is abc.com abc\user1 abc\user2 *****DR site Domain is abc.com abc\user1 Physically we have 2 domain controller having identical domain name. Here is the scenario: When abc\user2 (using windows XP) login on the DR site. he was able to log in using the id and password he/she uses in the main site i assume that even though he can see the abc.com domain present in the DR site XP somehow able to identify that it is not the same DC it uses to authenticate when it is connected on the main site but user still able to login to machine using the cache credentials. However when abc\user2(using windows 7) tries to login, the user is not able to connect, i can only assume that the windows 7 treated the DC that is present in the DR as the same as the one in the main site and since windows 7 recognizes the the DC in the DR site as valid DC, abc\user2 still not ablw to login to the domain since abc\user2 is not present or created in the AD of DR site. ** both DC is windows 2000
Free Windows Admin Tool Kit Click here and download it now
August 6th, 2011 7:37pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics