Odd IP issue

[HydroSqueegee]

So we have a server on the network. it works great, no problems. That server is connected to a switch which goes to a SAN.

you can ping SERVER from any client PC and get the correct domain IP in reply. if you log into the Server and ping SERVER, you get the private IP of the switch in reply. Not a problem, except its running an oracle database and its causing issues.

if you disable the NIC that goes to the switch (Switch1) the IP will resolve a ping to itself from itself just fine.


So for example, from a client PC:

Pinging SERVER [137.245.165.247] with 32 bytes of data:
Reply from 137.245.165.247: bytes=32 time<1ms TTL=128
Reply from 137.245.165.247: bytes=32 time<1ms TTL=128
Reply from 137.245.165.247: bytes=32 time<1ms TTL=128
Reply from 137.245.165.247: bytes=32 time<1ms TTL=128



From the Server:

Pinging SERVER [192.168.131.4] with 32 bytes of data:
Reply from 192.168.131.4: bytes=32 time<1ms TTL=128
Reply from 192.168.131.4: bytes=32 time<1ms TTL=128
Reply from 192.168.131.4: bytes=32 time<1ms TTL=128
Reply from 192.168.131.4: bytes=32 time<1ms TTL=128



NIC configurations:

Ethernet adapter Team 1:

Connection-specific DNS Suffix . :
IPv4 Address. . . . . . . . . . . : 137.245.165.247
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 137.245.165.254

Ethernet adapter Switch1:

Connection-specific DNS Suffix . :
IPv4 Address. . . . . . . . . . . : 192.168.131.4
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

 

[VirtualLarry]

It appears to be because you are multi-homed, and the NIC with the 192.x.x.x address is the default adaptor.

 

[HydroSqueegee]

HAH! Multi-homed. Changed the interface metric on the 2 adapters to the correct adapter number. Working on 2 of 4 servers with the problem. Fix isnt working on the other 2 that dont have a pair of NICs teamed...

 

[imagoon]

Unregister the SAN nics in DNS. You do this in the adapter settings, not the DNS server.