Hi One of my servers is getting frequent ping failure.. Reply from 172.26.172.48: bytes=32 time=396ms TTL=125 Request timed out. Reply from 172.26.172.48: bytes=32 time=246ms TTL=125 Request timed out. Ping statistics for 172.26.172.48: Packets: Sent = 4, Received = 2, Lost = 2 (50% los Approximate round trip times in milli-seconds: Minimum = 246ms, Maximum = 396ms, Average = 321ms I have to resolve it remotely.. So pl anyone reply ASAP.

you have this problem with scom TCP Monitor or in general? could be a network issue, but you can ask this to windows server forum. SS.Net MCITP Enterprise Administrator - MCTS Virtualization - Operations Manager 2007 - Exchange Server 2007 - MCSE-M S.Net Blog WindowServer.it WindowServer.it Learning Portal

you have this problem with scom TCP Monitor or in general? could be a network issue, but you can ask this to windows server forum. SS.Net MCITP Enterprise Administrator - MCTS Virtualization - Operations Manager 2007 - Exchange Server 2007 - MCSE-M S.Net Blog WindowServer.it WindowServer.it Learning Portal

this is not related to SCOM... This is in general.. And what are the possible steps to resolve it remotely or what suggestions i can give...??

this is not related to SCOM... This is in general.. And what are the possible steps to resolve it remotely or what suggestions i can give...??

ask this answer to windows server general forum. here you are OT SS.Net MCITP Enterprise Administrator - MCTS Virtualization - Operations Manager 2007 - Exchange Server 2007 - MCSE-M S.Net Blog WindowServer.it WindowServer.it Learning Portal

ask this answer to windows server general forum. here you are OT SS.Net MCITP Enterprise Administrator - MCTS Virtualization - Operations Manager 2007 - Exchange Server 2007 - MCSE-M S.Net Blog WindowServer.it WindowServer.it Learning Portal

I would start asking the network guys what is going on in their network. It looks like a bad performing WAN link.Regards, Marc Klaver http://jama00.wordpress.com/

I would start asking the network guys what is going on in their network. It looks like a bad performing WAN link.Regards, Marc Klaver http://jama00.wordpress.com/

Hi, Thank you for your post. 1. Run command "tracert 172.26.172.48", check the high latency time hop device 2. Run ping from computer in the same lan which located server 3. Check the server if patch the latest updates or high performance load 4. Try to disable TCO,RSS (KB951037), Autotuning(KB935400) on your server netsh int tcp set global chimney=disabled netsh int tcp set global RSS=disabled netsh int tcp set global autotuninglevel=disabled netsh int ip set global taskoffload=disabled If there are more inquiries on this issue, please feel free to let us know. Regards, Rick Tan