I have a network of 50 clients running XP Pro with 2, Windows 2003 servers on a single domain.

I have no duplicate IP address errors on the servers BUT I have 5 pairs of PC's that return the same IP address when I ping them by name. When I go to the PC's themselves and run IPConfig they return a different (correct?) IP address.

An example:
Ping d217 gives IP address of 192.168.100.177
Ping d325 gives IP address of 192.168.100.177

If I run IPConfig at d217 I get IP address of 192.168.100.157.
If I run IPConfig at d325 I get IP address of 192.168.100.177.

Other info:
The PC's affected were cloned using sysprep.
From the servers I am getting Kerberos Event ID 4 errors reported against 1 PC in each affected pair. "The kerberos client received a KRB_AP_ERR_MODIFIED error from server d325$. THe target name was cifs/d217.hps.local.

I have tried all the usual things like releasing and renewing IP; flushing dnscache; flushing arp but have had no success.

The problem it gives me is that I can't connect remotely to 1 pc in each affected pair and the affected PC's have spells of running very slowly as though they are seeking something that they can't find.

All help gratefully received!

I wonder if you Have tried pinging the computer from the IP address i.e, instead of pinging the computername, try pinging using command "ping 10.x.x.x". if that gives u reply, than ur computer is replying. run nbtstat -a 10.x.x.x to find the computername of that IP It should be matching with the one u have configured.

If that doesn't of any help.

try restarting the machine or

adding machine to the domain again.

If that doesn't help the only thing left is re-imaging the PC from my view.

Many thanks for your help.

If I ping using IP address or nbtstat with an IP address it will return just the one PC from each "Pair".

I think you have confirmed that in your view it is a client PC issue rather than a server issue.

I will try detaching the PC's from the network and re-joining as you suggest.

Thanks again!

Cloned = same SID = problems
run NewSid from sysinternals so each sid is unique on the network.

Without doing so you will just recreate the problem rejoining the domain.

Give a person a fish you feed them for a day.
Ask a person to internet search and they learn a skill for a lifetime.