I have a QNX 6.2.1 product that opens a TCP socket to a Windows server and
exchanges messages. One of our customers is now using a Windows 2000 cluster
for the server. He is complaining that when the cluster switches to a
different machine, my product does not connect any more, but is still trying
to communicate with the previous machine. If they execute “arp -d” on my
product, it then operates correctly with the new machine. They would like
the transition to be fully automated.
I’m not particularly knowledgable about arp issues, nor about Windows
clusters. I believe what is happening is that the server’s IP address is
remaining constant, but the MAC address is changing when they switch. Is
there something that can be done in my product to automate the transition to
this new MAC address?
Thanks,
Marty Doane
Siemens Dematic
Many stacks send out a ‘gratutitous arp’ when an interface
is configured. If windows did this (not sure if it does),
the QNX box would learn the new mac addr and you’d see
something like the following in the sloginfo:
Mar 31 11:34:16 5 14 0 arp info overwritten for 10.0.0.163 by 00:c0:93:01:b4:d2
-seanb
Marty Doane <martin.doane@siemens.com> wrote:
I have a QNX 6.2.1 product that opens a TCP socket to a Windows server and
exchanges messages. One of our customers is now using a Windows 2000 cluster
for the server. He is complaining that when the cluster switches to a
different machine, my product does not connect any more, but is still trying
to communicate with the previous machine. If they execute “arp -d” on my
product, it then operates correctly with the new machine. They would like
the transition to be fully automated.
I’m not particularly knowledgable about arp issues, nor about Windows
clusters. I believe what is happening is that the server’s IP address is
remaining constant, but the MAC address is changing when they switch. Is
there something that can be done in my product to automate the transition to
this new MAC address?
Thanks,
Marty Doane
Siemens Dematic