Computers On The Network Revert To A Computer Name That No Longer Exists
As the message explains we have a problem on our environment that machines will revert back to a computer name that no longer exists on our network. For example, we setup a new computer and it's completely random it will just revert back to a computer
name that was removed from our network close to a year ago. This affects computer running both Windows XP and Windows 7 regardless. This is extremely frustrating because it will hit random computers around the network, people will attempt to login
to their machines and will get the trust relationship error, at which point we need to remote in, change the computer name back to what it should be, reboot the computer and then they can continue to work. Has anyone had this problem? Any suggestions?
I'm not the one managing the server but I should be able to answer any questions about the environment. If any of you have seen this and can point me in the right direction it would be extremely helpful.
Thank you everyone!
June 11th, 2012 10:04am
You have not given some important data:
1. Generally there is cache on each computer.
2. There are name assign mechanisms on network: DNS, WINS and some information is hidden in Active Directory.
3. What names do you mean? FQDN, netbios names,....
When you setup a computer, you assing "internal" name that is registered by internal system after reboot. If you set suffix and DNS in NIC properties and DNS can create A records automatically, then new record can be created without doing it manually. Analogically,
when you have reservations in DHCP, DHCP assignes correct IP address, DNS settings and default gateway. I can describe more scenarious that have one common aspect, namely that there are mechanisms that can do what you describe.
Start your forensics with simple command
ipconfig /all
and report your findings here.
Regards
Milos
Free Windows Admin Tool Kit Click here and download it now
June 11th, 2012 11:54am
You have not given some important data:
1. Generally there is cache on each computer.
2. There are name assign mechanisms on network: DNS, WINS and some information is hidden in Active Directory.
3. What names do you mean? FQDN, netbios names,....
When you setup a computer, you assing "internal" name that is registered by internal system after reboot. If you set suffix and DNS in NIC properties and DNS can create A records automatically, then new record can be created without doing it manually. Analogically,
when you have reservations in DHCP, DHCP assignes correct IP address, DNS settings and default gateway. I can describe more scenarious that have one common aspect, namely that there are mechanisms that can do what you describe.
Start your forensics with simple command
ipconfig /all
and report your findings here.
Regards
Milos
June 11th, 2012 12:04pm
Alx886 wrote:
As the message explains we have a problem on our environment that
machines will revert back to a computer name that no longer exists on
our network. For example, we setup a new computer and it's
completely random it will just revert back to a computer name that
was removed from our network close to a year ago. This affects
computer running both Windows XP and Windows 7 regardless. This is
extremely frustrating because it will hit random computers around the
network, people will attempt to login to their machines and will get
the trust relationship error, at which point we need to remote in,
change the computer name back to what it should be, reboot the
computer and then they can continue to work. Has anyone had this
problem? Any suggestions? I'm not the one managing the server but I
should be able to answer any questions about the environment. If any
of you have seen this and can point me in the right direction it
would be extremely helpful.
Thank you everyone!
There must be something else changing the computername as Windows
itself does not change a preset computername at random. Are you using
images, which are deployed to PCs under certain circumstances?
Wolfgang
Free Windows Admin Tool Kit Click here and download it now
June 11th, 2012 12:16pm
Alx886 wrote:
As the message explains we have a problem on our environment that
machines will revert back to a computer name that no longer exists on
our network. For example, we setup a new computer and it's
completely random it will just revert back to a computer name that
was removed from our network close to a year ago. This affects
computer running both Windows XP and Windows 7 regardless. This is
extremely frustrating because it will hit random computers around the
network, people will attempt to login to their machines and will get
the trust relationship error, at which point we need to remote in,
change the computer name back to what it should be, reboot the
computer and then they can continue to work. Has anyone had this
problem? Any suggestions? I'm not the one managing the server but I
should be able to answer any questions about the environment. If any
of you have seen this and can point me in the right direction it
would be extremely helpful.
Thank you everyone!
There must be something else changing the computername as Windows
itself does not change a preset computername at random. Are you using
images, which are deployed to PCs under certain circumstances?
Wolfgang
June 11th, 2012 12:27pm