Link to home
Start Free TrialLog in
Avatar of fecklessness
fecklessnessFlag for United States of America

asked on

Windows Server 2008 Domain Controller DHCP Server shows old name?

I have inherited a client with a new situation than I have faced before and all the research I've done has made no progress so I come to you guys for advice so I can learn what I do not know.

The DC is named "COMPANYNAMESERVER" ... When I opened the DHCP console it shows a server with a different name than that of this server. It says something like "WIN-Z8X67" or whatever. The server has a big red stop sign icon over it and you cannot click on it or expand it for more information. If you delete the server it disappears then if you go to add an authorized server and enter my own IP address or "COMPANYNAMESERVER" it takes you to the next window and shows Server Name as "WIN-Z8X67" again!

So somewhere in here it thinks this server is named "WIN-Z8X67" - but I went into ADSI Container, Services, Net Services, checked DHCP root and it does not show this old computer name.... I have checked DNS for old entries.... I don't know what to do to add this DC as an authorized DHCP server can anyone guide me how to troubleshoot this? Did I provide enough details to make the problem clear?
Avatar of Flipp
Flipp
Flag of Australia image

If you run a nslookup on IP what are the results?
Avatar of Lionel MM
If you go to control panel, system, advanced settings and then the name tab what is the server name there?
Avatar of fecklessness

ASKER

@Flipp - nslookup on IP shows COMPANYNAMESERVER.FQDN

@lionelmm - name tab in advanced settings shows COMPANYNAMESERVER.FQDN also
SOLUTION
Avatar of Flipp
Flipp
Flag of Australia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Yes it is DNS server, it is the only one. I see the new computer name.
Have you tried removing dhcp role then re-adding?
Yes in fact that was the first thing I did.
What happens if you add an mmc console with dhcp on another pc?
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Yes, host file on the server did at some redirects for the strange computer name to point back to its own IP address. We did not clear the cache. And also your post did not include the link.

We didn't add MMC console with DHCP on another machine yet but will post this back soon. We did notice the NetBIOS name is still the old computer name. Is that the reason for this?? The person who set this server up I think had very little idea what they were doing. It is a hodge podge of weird settings in wrong locations.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
If you run netdom computername <new_name> /enum from an administrative command prompt, is the old name included in the results?
"COMPANYNAMESERVER" is the only result when running the netdom command, It's not showing the old name. But if I use an IP scanner, the Hostname results back to "WIN-Z8X67" which is another indication that something is wrong.
We did notice the NetBIOS name is still the old computer name.
Where do you see this?

But if I use an IP scanner, the Hostname results back to "WIN-Z8X67" which is another indication that something is wrong.
An IP scanner would probably get that name from DNS. Check the reverse lookup zone that corresponds to your subnet. It sounds like the PTR record for the server's IP address still has the old name.
We did notice the NetBIOS name is still the old computer name.

Where do you see this?
From the IP scanner.

An IP scanner would probably get that name from DNS. Check the reverse lookup zone that corresponds to your subnet. It sounds like the PTR record for the server's IP address still has the old name.
Thats what I was originally thought and didnt find anything in there. I just checked again, looked every record in the DNS and not one this is referring to "WIN-Z8X67".
Do you have a WINS server in your environment? Maybe there's an old WINS-R record in there with the wrong name.
Avatar of compdigit44
compdigit44

At this point  I would recommend install Network MOnitor to capture the network traffic
So... we are grateful for all the helpful input. In the end, we went back into the HOSTS file and found that the entries we had removed were somehow back in the HOSTS file... we deleted again. Saved again. And rebooted. Voila, the correct name appears everywhere. I'm not sure why this change didn't stick in the first place, as it happened there was even another witness watching the action to confirm the first time.

Either way seems to be named correctly now and back on track. I'm watching to see if HOSTS file is modified back to it's previous state after another reboot or something, but there's nothing to indicate that it should do that again. Thanks to all contributors.