• Status: Solved
  • Priority: Low
  • Security: Public
  • Views: 51
  • Last Modified:

Server returning incorrect ip address when the hostname is pinged

Hi, I have a Server 2016 built on a VM. When I ping the host name I get an incorrect ip address (which is my existing server in another VM). I read somewhere it was due to Credentials Manager. Tried removing it but still same. I flushed the dns but still the same. I even removed the server from domain and added it back. I also tried to map the folder on this server using hostname but unable to locate it but when I use ip it can locate. Not sure what else to try.
0
Ashok Kandavel
Asked:
Ashok Kandavel
2 Solutions
 
Hello ThereSystem AdministratorCommented:
On client:
ipconfig /flushdns
ipconfig /registerdns

Open in new window

Wait 15mins...

Server should point to DNS server (yourself) with static IP.

Also go to DNS server and check for any DNS mismatch.
0
 
Siegfried SbrzesnyCommented:
Set up a Nat network on your host - instructions on WinServer host can be found here: https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/user-guide/setup -nat-network or here https://www.experiencingit.net/windows/windows-server-2016-nat-router/

 Which host system do you use ?
0
 
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
Both servers have different names, of course?
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
Sam Simon NasserIT Support ProfessionalCommented:
Server A should have IP 192.168.1.10 with Name ServerA
Server B should have IP 192.168.1.20 with Name ServerB

this is a simple scenario, when you ping ServerA, it will point you to 1.10 not 1.20
check if you have static IPs, or try this trick: go to device manager and delete the Ethernet card, and refresh, it should bring a clean clear Ethernet card with no customization
0
 
Zaheer IqbalTechnical Assurance & ImplementationCommented:
Do you have conflicting MAC Addresses by any chance ?
1
 
Sam Simon NasserIT Support ProfessionalCommented:
another question, do you have a DHCP Server?
0
 
Mark BillExchange, AD, SQL, VMware, HPE, 3PAR, FUD, Anti MS Tekhnet, Pro EE, #1Commented:
Have a look at all the DNS records in Active Directory in the forward lookup zone for that servers hostname, remove the duplicates.

Also have a look in the reverse lookup zones same steps as above.

Then flush and register dns from the server.

I learned that the best way to do all of this stuff is by DHCP registration via active directory using DNS admins and DNS Proxy Admins groups in AD for the DHCP servers, there are also all kinds of other fancy options under DHCP advanced.
0
 
Ashok KandavelSr. Service Operation EngineerAuthor Commented:
I had to go to the DNS server. The new file server has the hostname FileServer1 with the ip 10.244.5.8. An existing CNAME record FileServer1 was pointing to FileServer2 (A record 10.244.5.10). I've deleted it and created an A record for FileServer1 pointing to 10.244.5.8. This solved the issue.
0
 
Sam Simon NasserIT Support ProfessionalCommented:
my answer was not marked as assisted answer, thus i did not get my points. kindly check.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now