Hardware connection issue or drivers?

[paperfist]

I'm working on a network with 10 XP Pro machines which connect to a Windows 2003 Server machine.

For one user using an outdated laptop I cloned (w/Acronis) her setup to a newer desktop, updated all the drivers and off she went running.

Now for some reason she has to disconnect the CAT6 cable from the back of the desktop, reboot and reconnect cable in-order to be able to log-in. I replaced the CAT6 cable thinking that was the issue, but that didn't solve it.

On the server end I forgot to write it down, but the Event Viewer was saying something about her not having correct credentials to log-in with.

The other odd thing, or it seems odd for a n00b like me is her IP switched 20 when it was 18 before. Same with another user who went from 15 to 21. In the year I've been working on them none of the 10 machines ever switched IPs.

Any idea would be greatly appreciated!

 

[ch33zw1z]

I'm working on a network with 10 XP Pro machines which connect to a Windows 2003 Server machine.

For one user using an outdated laptop I cloned (w/Acronis) her setup to a newer desktop, updated all the drivers and off she went running.

Now for some reason she has to disconnect the CAT6 cable from the back of the desktop, reboot and reconnect cable in-order to be able to log-in. I replaced the CAT6 cable thinking that was the issue, but that didn't solve it.

1. On the server end I forgot to write it down, but the Event Viewer was saying something about her not having correct credentials to log-in with.

2. The other odd thing, or it seems odd for a n00b like me is her IP switched 20 when it was 18 before. Same with another user who went from 15 to 21. In the year I've been working on them none of the 10 machines ever switched IPs.

Any idea would be greatly appreciated!

1. Investigate that error thoroughly.
2. Is the second user having any issues logging in (I'm assuming to a domain?). I wouldn't worry about the switching IP's unless other users beging to having problems as well.

Cloning from a laptop to a desktop is a big change for Windows. If all else fails...reinstall. In my experience, drivers cause weird issues.

 

[imagoon]

Cloning a machine changed things like the GUID which can break windows authentication. The machine itself has an account with some information in it that is used so it can log in to the domain. If the machine can't log in, the user can't log in. Cloning is generally not recommended in domain environment. You *may* be able to remove the machine from the domain and rejoin it to clear the security issues. As a note though, put cloning domain computers down on your list of "bad IT, don't do it!"

Also new MAC address = new DHCP address.

 

[JackMDS]

http://kb.acronis.com/content/1616

 

[paperfist]

Thanks for the feedback guys.

The error I get in the Event viewer for system is this:

Source: NETLOGIN
Event ID 5722

The session setup from the computer EDUCATION01 failed to authenticate. The name(s) of the account(s) referenced in the security database is EDUCATION01$. The following error occurred:
Access is denied.
---------------------------

She is able to log-in once the Ethernet cable is unplugged and plugged back in.

The other clone was desktop to desktop and produced zero issues other then her IP change.

 

[paperfist]

http://kb.acronis.com/content/1616

Thanks Jack, this is what I was afraid the issue is. I'm using Acronis with the PlusPack for restoring to dissimilar hardware, which I thought would do the same thing your link does. I guess I'll have to re-clone with sysprep and keep my fingers crossed

 

[imagoon]

Thanks Jack, this is what I was afraid the issue is. I'm using Acronis with the PlusPack for restoring to dissimilar hardware, which I thought would do the same thing your link does. I guess I'll have to re-clone with sysprep and keep my fingers crossed

Sysprep will blow away the domain security identifiers as well. You will need to remove the machine account in the domain as well.

 

[paperfist]

Sysprep will blow away the domain security identifiers as well. You will need to remove the machine account in the domain as well.

Ah great, we then enter 'over my head territory'

I will try to disjoin it from the domain first and see how that goes. What's puzzling to me is why she is cleared to log-in after unplugging from the NIC and plugging back in.

Out of curiosity if I did to a fresh install can I simply just re-create her account on the new install and re-join it to the network?

 

[imagoon]

Ah great, we then enter 'over my head territory'

I will try to disjoin it from the domain first and see how that goes. What's puzzling to me is why she is cleared to log-in after unplugging from the NIC and plugging back in.

Out of curiosity if I did to a fresh install can I simply just re-create her account on the new install and re-join it to the network?

Local cached credentials.

 

[paperfist]

Local cached credentials.

Those three words gave me quite an education

So if I understand correctly there's an issue with the security channel and I'm going to use Nltest.exe to test out the issue and Netdom.exe to fix it?

 

[imagoon]

Those three words gave me quite an education

So if I understand correctly there's an issue with the security channel and I'm going to use Nltest.exe to test out the issue and Netdom.exe to fix it?

Honestly the easiest way to fix it is to remove and rejoin the computer from the Domain. The other method does work (netdom) but you can cause a lot more issues (like a typo resetting all of computer accounts etc.)

 

[RadiclDreamer]

Go to AD and delete the pc account
Remove the machine from the domain
Add the machine back to the domain.

Should resolve the issue

 

[paperfist]

Thanks everyone for all your help, hopefully I'll be able to give the remove/add solution a try this weekend.

 

[paperfist]

EDIT: N/M

Thanks again everyone, I was able to delete the computer from Active Director then log-in on the local computer's Admin account and rejoin the network. Problem solved!