Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1033
  • Last Modified:

Why does a Windows 2008 R2 Exchange 2010 cluster server give wrong address when pinging local hostname

I have a three node clustered Windows 2008 R2 virtual servers that host Exchange 2010.  When pinging their hostname locally on the server, a 169.254.x.x IP is given instead of the statically assigned IP.  When pinging the server from another server, you get the DNS registered IP.  Looks very funny and also gives problems in email headers when you see the name of the server with the 169.254.x.x IP.  I would like to fix this and make sure the system responds with the correct IP.  Thanks.
0
tdbaker329
Asked:
tdbaker329
  • 3
  • 2
2 Solutions
 
ckeshavSr. Infrastructure SpecialistCommented:
It might be the giving the IP of the Cluster IP(Virtual IP)
0
 
tdbaker329Author Commented:
I thought of this but the virtual IP of the node name is a static IP assigned with a different DNS registered name.
0
 
tdbaker329Author Commented:
Figured it out.  I had to enter a fully qualified name in a host file on each DAG server so that the Micrsoft Failover Virtual Adapter would see the correct name of the server and IP.  All is fixed now.  Thanks.
0
 
ckeshavSr. Infrastructure SpecialistCommented:
ok
0
 
tdbaker329Author Commented:
I determined what the problem was and corrected the situation.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

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