TCP/IP error in event viewer

  • Thread starter Thread starter Tommy
  • Start date Start date
T

Tommy

I am receiving an error in my event viewer that I have
more than one registered machine on the network with the
same IP address. When I type in nbtstat -n from the Cmd
prompt, there are 3 systems with the same name and IP
address showing. What would cause this and how do I fix
it?
 
Tommy said:
I am receiving an error in my event viewer that I have
more than one registered machine on the network with the
same IP address. When I type in nbtstat -n from the Cmd
prompt, there are 3 systems with the same name and IP
address showing. What would cause this and how do I fix
it?
Click to expand...

Perhaps there are actually 3 systems using the same computer name
and IP address running in the LAN. Know where these computers are
located? If yes, were they cloned using the same image file using
Symantec Ghost? The fix is easy... change the computer name and
[static] IP address.
 
-----Original Message-----
I am receiving an error in my event viewer that I have
more than one registered machine on the network with the
same IP address. When I type in nbtstat -n from the Cmd
prompt, there are 3 systems with the same name and IP
address showing. What would cause this and how do I fix
it?
Click to expand...

Perhaps there are actually 3 systems using the same computer name
and IP address running in the LAN. Know where these computers are
located? If yes, were they cloned using the same image file using
Symantec Ghost? The fix is easy... change the computer name and
[static] IP address.

.
Yes, the computers were cloned using a version of Ghost,
Click to expand...
but the computer names are not the same, the hostnames
have been changed as well as the IP addresses.

Could this be a registry or SID problems since the
machines were imaged from the same machine?
 
Tommy said:
Could this be a registry or SID problems since the
machines were imaged from the same machine?
Click to expand...

This would normally be the cause although the name changes and IP
changes alluded to by Mistoffolees should have taken care of the
problem. And using Ghost should have taken care of the SID unless
the version of Ghost is an older one.
 
Back
Top