Ping is resolving to wrong IP

September 15, 2005 at 10:44:53
Specs: Server 2003, p4/512

We have just switched over to 2003 server. We have AD, DNS, and Wins running on this DC. Before we switched it over we had it running in a test environment using the IP 192.168.1.89 (assigned by DHCP) it ran fine. On the day of the switch over I had to assign it a static Ip address 192.168.1.37. Ever since then we have been having permision problems, users losing their mapped drives, servers not being able connect to one another. The weird thing about it is that if I ping the server it comes back with the 192.168.1.89 address. I should be coming back with 192.168.1.37 I checked the tcp/ip settings and it is assigned 37 for the ip. I found some DNS entries on the server still pointing to 89. I did change those to use the .37 . Any Ideas on what might be happening?

Thanks in advance.


See More: Ping is resolving to wrong IP

Report •


#1
September 15, 2005 at 11:06:46

If it was a DC before the IP address changed, it is borked. You can't just change the IP address of a DC. DC's have service records and what not in DNS that need to be changed.

"It happens."


Report •

#2
September 15, 2005 at 11:38:41

I was hoping that answer wouldn't come up. Is there any way to fix it? I'd hate to reconfigure it.

Report •

#3
September 15, 2005 at 12:40:36

If you're not familiar with the all the DNS records required for a DC and other config stuff, easiest way is put it back to the old PC, dcpromo it down, change the IP back to the right one, and DC Promo it back up.

"It happens."


Report •

Related Solutions

#4
September 15, 2005 at 15:13:55

There is no reason to go thru all that just to get DNS working correctly.

First things first. Did you delete the entries out of the Wins database. Do so.

Do you have a hosts file on this server? if so delete it or rename it.

This will eliminate those as sources to the bad name resolution.

On your primary DNS server delete the host and ptr entries for the server. Recreate the entries with the correct ip address.

Under Forward lookup zone click on the SOA entry and go to properties. Click on the Name Servers tab. Edit the entry for this server to the correct ip address.

Click on the NS entry and go to properties. Go to the Name servers tab and change the entry to the correct ip address.

Exit DNS. Go to Services and stop and restart the DNS service. Look at event viewer for errors. Try pinging the server by name from a different machine and see if this didn't resolve your issue.

Golly gee wilerkers everyone. Learn to Internet Search


Report •

#5
September 15, 2005 at 15:38:30

"There is no reason to go thru all that just to get DNS working correctly."

LOL...have fun.

BTW, when you're finished, run DCDiag on it to make sure everything is right, which btw, it probably won't be. Seen enough people try to correct DNS and fail to know if you're not sure what you're doing, don't bother correcting the DNS records.

Please help survivors of Hurricane Katrina.

www.redcross.org


Report •

#6
September 15, 2005 at 15:52:02

Always try the simple thing first. No sense using a tank on a fly if the newspaper will work :-)

Golly gee wilerkers everyone. Learn to Internet Search


Report •

#7
September 16, 2005 at 15:35:51

hey ,
try ipconfig/flushdns on all clients.
I suspect all clients have the old IP address of the DC still in cache.
and now that the dc has a new IP its giving errors.


Report •

#8
September 16, 2005 at 15:41:37

That's not gonna do anything until he corrects all the DNS records that are wrong. Otherwise, the clients are simply going to cache the borked DNS records again.

Please help survivors of Hurricane Katrina.

www.redcross.org


Report •

#9
September 20, 2005 at 11:15:19

Make sure you don't have any funky entries in your hosts files.


Report •

#10
October 1, 2005 at 12:34:16

I had the samr thing happen... I just reset the router and it did the job.... there was a ghost floating in the router

Report •


Ask Question