My exchange DAG with 2 nodes. noticing this weird IP address 169.254.1.97 (MS failover Cluster Adapter) on both nodes when I run IPCONFIG/all.  Time to time I see this address in the msg headers too.  I can ping this address from either nodes but cannot ping from the lan.  I am not sure where is this coming from .. Any !deaz.

thanks

your VM either has ghost nics or winsock needs a flush.

take ample downtime on the nodes:

1. for ghost adapters

http://www.tech-recipes.com/rx/504/how-to-uninstall-hidden-devices-drivers-and-services/ or http://support.microsoft.com/kb/315539

2. For Winsock Reset

netsh int ip reset c:\resetlog.txt

netsh winsock reset

reboot, ipconfig will be lost, after the server comes up give correct IPs and reboot.

Go to Advanced Settings in Network connection properties and change the order of NICs. That should resolve displaying 169* IP in message headers.

If these are VMs then check the VLAN configured on these VMs and vSwitch configuration on VMware.

If these are physical machines then check if they are connected directly to each other or via switch.

My exchange DAG with 2 nodes. noticing this weird IP address 169.254.1.97 (MS failover Cluster Adapter) on both nodes when I run IPCONFIG/all.  Time to time I see this address in the msg headers too.  I can ping this address from either nodes but cannot ping from the lan.  I am not sure where is this coming from .. Any !deaz.

thanks

Hi,

Download nvspbind from MSDN Gallery and change the bindings order.
"The Microsoft Failover Cluster Virtual Adapter" should be moved down in the list.

See information about this in http://technet.microsoft.com/en-us/magazine/gg314976.aspx

Thanks All.

Martina ......... It appears taht we don't need a restart of the mailbox servers in DAG after we change the binding order with NVSPBind???? Correct?

Thanks All.

Martina ......... It appears taht we don't need a restart of the mailbox servers in DAG after we change the binding order with NVSPBind???? Correct?

martina .... I ran the command against my active node in the dag and sent few test email messages itnernally and I still see this 169 ... IP address though it has moved to the bottom of the list ....   any ideas?  thanks

thanks Sharique.

These are 2 physical servers

so I run the following ...

netsh int ip reset c:\resetlog.txt

netsh winsock reset

and reboot the node ...   so when the node comes up it will have no IPs > I will have to re-assign the IPs and reboot again?????

Correct?

thanks Sharique.

These are 2 physical servers

so I run the following ...

netsh int ip reset c:\resetlog.txt

netsh winsock reset

and reboot the node ...   so when the node comes up it will have no IPs > I will have to re-assign the IPs and reboot again?????

Correct?