Jerblaine
asked on
Pings by old subnet IP address when pinging name.
We changed routers and now instead of 15.xxx we are 1.xxx. For some reason when I ping the name of my server it still looks for the old 15.xxx IP address.......but when i ping the server by the NEW 1.xxx address it finds it. How can I get the name resolution part of the ping to see the new 1.xxx?
Last Comment
ASKER
I ran the flush and it still looks for the 15.xxx when pinging by name.
As far as the A record goes, there is an A record for the server in the forward lookup zone. The A record contains the correct IP address with the new 1.xxx subnet.
Any other suggestions?
As far as the A record goes, there is an A record for the server in the forward lookup zone. The A record contains the correct IP address with the new 1.xxx subnet.
Any other suggestions?
After flushing DNS and verifying the record on the server, I'd make sure the machine you are pinging from has no entries in its HOSTS or LMHOSTS files.
ASKER
well it does have other A records. Should I delete the other A records from the Forward Zones in the DNS mgmt console? Should I just leave the A record for the server and that's it?
It has other A records for the same server???? The old one, then you got to remove that !!!
ASKER
no not for the same server. The other A records are for some of the clients. I am having some ping issues with a client too. One of the clients cannot be pinged by name or IP but there is an A record for that client......however other clients with A records ARE able to be pinged by name and IP...so I cant figure out why that one client cant be pinged and neither can the server. There must be some relationship between A records and pinging. Also why is it still looking for the 15.xxx instead of the new 1.xxx??
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
on your client run arp -d.
On DNS servers, run ipconfig /flushdns AND arp -d.
That should clear things up.
On DNS servers, run ipconfig /flushdns AND arp -d.
That should clear things up.
ASKER
I will check the host file list. How do I run arp-d? is it just that? a command on the command line as arp-d?
ASKER
Awesome! It was the host file! It still had the 15.xxx in it. I changed it and now it pings both ways.
Now I am still not able to ping just one of the clients. Maybe I will post another question for that.
Now I am still not able to ping just one of the clients. Maybe I will post another question for that.
Yes arp -d at the command line. you need a space between arp and -d.
try arp -d {ip address that you want to remove from the arp table}
to see what all is in your arp table do
arp -a
arp -d * will remove all arp entries from your computer. these will be populated again as your computer starts finding them out again
to see what all is in your arp table do
arp -a
arp -d * will remove all arp entries from your computer. these will be populated again as your computer starts finding them out again
Windows Server 2003
Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).
129K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
- Check your DNS Server to see if the A Record has been updated for that Server
- run ipconfig /flushdns on your desktop
Hope this helpsThanks
Nitin