15 replies
by kyocum Accepted solution
by retro77 Accepted solution
by kyocum Accepted solution
by retro77 Accepted solution
Do you know what server is your WINS server and what server is your DNS server? If not go to the command prompt and type: ipconfig /all
This will tell you the IP of your WINS and DNS. Also make sure on that problem server that the DNS and WINS are configured correctly.
Just thought of this: from the problem server, do a tracert to the DNS and WINS servers. If it cant route there, then it cant register the new address.
To remove the entry in DNS: open DNS manager, expand your server, go to Foward Lookup Zones, then your domain name, then find the entry for the old server's IP address. you can delete it and make a new one or just edit the IP address to reflect the new one.
In WINS: open WINS Manager, expand your server, right click on Active Registrations, Display Records, click find now, find the old entries and delete them
by cg it Accepted solution
is this AD environment? if not do you run DNS and/or WINS?
if this is an NT environment and you run DNS/WINS you need to change the records in DNS/WINS.
by kyocum Accepted solution
by retro77 Accepted solution
Do you use host files? It might be in there. If not, its gotta be cached somewhere. How long ago did you remove the old name? Also when you ping the name, not the full DNS name, what is returned? Just the name or the full DNS name?
Reverse Lookup Zones: also change your PTR record for that server. They dont always update automagically.
by kyocum Accepted solution
by retro77 Accepted solution
Ok from your workstation, do an ipconfig /flushdns
See if you still get replies from your workstation.
by kyocum Accepted solution
by retro77 Accepted solution
It has to be cached somewhere or statically set somewhere.
Flushing the DNS on the DNS server wont hurt. I would do it after hours.
When you ping the IP from a workstation, what is returned? WINS name [just the name] or DNS FQDN?
by kyocum Accepted solution
just:
pinging yaddayadda [xxx.x.x.18] with 32 bytes
reply from xxx.x.x.18
now i did do a flush on the dc and restarted both dns services - when i do a displaydns the name isn't there at all, but i ping that specific name and it returns that same ip address. when i do a tracert on that ip it comes back as the correct server, the new one. so, i am coming to the conclusion that i can't get rid of that old name ever!
by retro77 Accepted solution
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending