unable to ping secondary ip from second server

[uggle]

Hi,

Bit of a weird one this, but if anyone has some ideas, it would be appreciated.

Since my 3 Windows servers have been moved to the new DC in SAT, i am unable to ping the secondary ip addresses of any of the servers from a different server within the same DC. Works fine from outside the DC. Worked ok in the old DC.

with no firewall, ipsec, filtering etc.

I've had a support ticket in for a couple of days, which hasn't helped at all, stating that the routing tables look ok on the router and that it must be a server configuration (which has been checked and verified as ok)....... sounds a bit strange that it is affecting all 3 of my servers... one I could accept, but not three.

I'm at a lose, any ideas?

[knightfoo]

Are your secondary IP addresses in the same /24 subnet?

[uggle]

Hi,

Yes all secondary ip's are using the same subnet mask of 255.255.255.0 .

This is only affecting some secondary ip's not all.

Found this out when a secondary dns server was unable to connect to primary (no problems previously before the move).

Regards,

CD

[uggle]

Strange....

This morning the primary ip could not be pinged from within the DC or remotely (I could access the server using one of the secondary ip's). No change to the setup of the server had been carried out.

Network guys have solved this problem in record time!.... Still awaiting to hear back as to what the problem was, as this may give a clue as to the secondary ip issues..... fingers crossed.

Regards,

Chris

[uggle]

It appears that it was a stale arp record on one of the edge routers. I have requested that cache of arp of my other ip's be cleared from internal routers as I am certain it is not a problem on the servers themselves as I have done thorough testing.