LadySlinger
IS-IT--Management
I have a backup admin that recently received a new laptop. He changed the account name on his old laptop so that it can be recycled to a new person (i.e. x-laptop become y-laptop).
His new laptop was given the same name that the old laptop originally had (x-laptop).
Now when he attempts to connect to the domain his new laptop gives him error messages, saying that it cannot authenticate him to the domain because he is not trusted. We are on a DHCP network.
Does this have something to do with him having recycled the name x-laptop? I know he setup his new laptop before changing out the old laptop. I have a feeling that doing the setups out of order is confusing the heck out of the DC. If its something else, please let me know. He's certain that the issue is all on the server and that there is nothing to be done on his local machine.
Thanks
His new laptop was given the same name that the old laptop originally had (x-laptop).
Now when he attempts to connect to the domain his new laptop gives him error messages, saying that it cannot authenticate him to the domain because he is not trusted. We are on a DHCP network.
Does this have something to do with him having recycled the name x-laptop? I know he setup his new laptop before changing out the old laptop. I have a feeling that doing the setups out of order is confusing the heck out of the DC. If its something else, please let me know. He's certain that the issue is all on the server and that there is nothing to be done on his local machine.
Thanks