S
Steve
On one of our test servers we have been getting strange networking behaviour
from it. This has occured since we moved location (and therefore changed
switch/cables etc.).
Basically the first thing we noticed was that it didn't connect to certain
computers devices on our network properly. It wouldn't connect to one of our
database servers and won't connect to one printer (but will connect to
another printer of the same model). Then we tried to ping these devices and
I get (for example) the following results:
Pinging serv-db3 [172.16.3.60] with 32 bytes of data:
Reply from 172.16.3.60: bytes=32 time=50708ms TTL=127
Reply from 172.16.3.60: bytes=32 time=50708ms TTL=127
Reply from 172.16.3.60: bytes=32 time<10ms TTL=127
Reply from 172.16.3.60: bytes=32 time=-57169ms TTL=127
Ping statistics for 172.16.3.60:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = -57169ms, Average = 11061ms
Notice the huge latency when connecting to this server, not to mention the
negative fourth result. If I ping serv-db3 from my desktop PC I get a time
of <1ms i.e. correct.
Any ideas what is wrong with our test server and how to correct it?
from it. This has occured since we moved location (and therefore changed
switch/cables etc.).
Basically the first thing we noticed was that it didn't connect to certain
computers devices on our network properly. It wouldn't connect to one of our
database servers and won't connect to one printer (but will connect to
another printer of the same model). Then we tried to ping these devices and
I get (for example) the following results:
Pinging serv-db3 [172.16.3.60] with 32 bytes of data:
Reply from 172.16.3.60: bytes=32 time=50708ms TTL=127
Reply from 172.16.3.60: bytes=32 time=50708ms TTL=127
Reply from 172.16.3.60: bytes=32 time<10ms TTL=127
Reply from 172.16.3.60: bytes=32 time=-57169ms TTL=127
Ping statistics for 172.16.3.60:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = -57169ms, Average = 11061ms
Notice the huge latency when connecting to this server, not to mention the
negative fourth result. If I ping serv-db3 from my desktop PC I get a time
of <1ms i.e. correct.
Any ideas what is wrong with our test server and how to correct it?