URGENT > Pinging server name tries to ping wrong IP

[mattianuk]

Hi

 

Probably a n00b error ... BUT...

 

When I try to ping my two DC servers by name they try to resolve to an IP address that is not their main network one - IE they try to resolve to 10.0.15.1 which is one of their cluster IPs as they are setup as a failover cluster.

 

How can I make sure when something tries to get to them, they go to the right IP?

 

Tia

 

[glennda]

You need to look in your DNS and remove the wrong IP. On your cluster network interface you need to remove DNS Servers I believe (never used MS clustering so not sure).

[DavidIrwin]

These "incorrect" IPs are probably there as a result of automatic registration with the DNS servers. To resolve this on the NIC used for the cluster open the properties window, click IP v4 Properties, Click Advanced button, select DNS tab. At the bottom there is a setting "Register this connection's address in DNS" which should NOT be selected.

 

I have also seen this problem where servers have separate NIC for iSCSI and other networks.

 

Regards,

 

Dave

[TronXP]

Do You have Cluster services on a domain controller???

[mattianuk]

yes, that's the way novatech set it up?

[TronXP]

By cluster IP do you mean the IP of the ISCSI or a cluster resource IP?

[mattianuk]

The actual cluster ip is appearing on one of the hosts local area connections when I do an ipconfig - but not the other one. When I do an nslookup from any PC it lists all the iscsi and cluster service ips and the LAN ip. I'm thinking it may be causing this http://www.edugeek.net/forums/windows-7/100567-win-7-64x-hangs-login-waiting-group-policy.html ??

[mattianuk]

And I did the removal from dns and I did the tick box in the port properties.

[DavidIrwin]

The actual cluster ip is appearing on one of the hosts local area connections when I do an ipconfig - but not the other one. When I do an nslookup from any PC it lists all the iscsi and cluster service ips and the LAN ip. I'm thinking it may be causing this http://www.edugeek.net/forums/windows-7/100567-win-7-64x-hangs-login-waiting-group-policy.html ??

 

It is quite likely that if there are incorrect IP addresses for domain controllers in DNS then client machines will pause for long periods while booting or trying to log in. the best bet for this is to manually control the DNS entruies as detailed above. All being well now you have done that you should not see any problems :-)

 

Dave