Hi Hemanth,
One of our systems administrators ran the following commands on the two servers in our QAS cluster:
netsh interface ipv6 set prefix ::1/128 50 5
netsh interface ipv6 set prefix ::1/96 40 4
netsh interface ipv6 set prefix ::ffff:0:0/96 30 3
netsh interface ipv6 set prefix ::/0 20 2
netsh interface ipv6 add prefix ::ffff:169.254.0.0/112 10 1
After that, when we did "ping -4 <HOSTNAME>, it comes back with a 10.xxx.xxx.40 IP address. This isn't the "primary IP" of the server (10.xxx.xxx.5). I asked the systems administrator what the 10.xxx.xxx.40 address was and he said it is used by a private network that connects the two servers in the cluster. When we tried to logon to QAS with the Logon Group, it tells us "partner '10.xxx.xxx.40' not reached". The systems administrator then added the two clustered servers with their primary IP addresses to the c:\windows\System32\drivers\etc\hosts file.
Adding the servers to the hosts files seems to have fixed the problem. Now "ping -4 <HOSTNAME>" returns the primary IP address. I don't know if this is the only or best solution. It seems like a workaround that could somehow get undone sometime in the future. Do you have any other advise?
Thanks,
Jerry