Intermittent networking issue between 2003 and *one* IP at a time
The issue first occurred between a server 2003 (SP2 32bits) and an XP client (SP3 32bits). Communications started to get lost between the two. Pinging each other would show both machines loosing connectivity in sync for short periods and then recovering it for short periods too.The issue lasted for several hours and then it all would get fixed by itself just to start again the next day.This problem went for a couple of weeks. Troubleshooting included: flushing DNS -> didn't helploggin off and on again -> didn't helprestarting computer -> helped for some time.reinstalling NIC hardware -> helped for some time.reinstalling NIC drivers -> helped for some time.reinstalling OS -> helped for some timechanging switch port -> helped for some timeconnecting to another switch -> helped for some time Nothing could get it fixed permanently until we changed the computer's IP, then it went away. We left it changed in the hope of troubleshooting the bad IP later. But now it has happened again but between the server and another IP since yesterday. This time i could get some more info: The issue started yesterday around 6.00 a.m. and today around 8:00 a.m. and lasted several hours.Pinging each other shows conectivity changing on and off in around a minute with 66% packet loss total.It happens using either IP or computer name.No other machine has any connectivity issue with any of the two machines (i can be rdp'ing/ssh'ing for hours without problems to both) I honestly have no idea what could be happening. Any help would meet milk and cokies and be appreciated =) "When something is not working as it is supposed to, then it is working as expected" -R
July 19th, 2012 12:22pm

Hi Iker, Thanks for posting here. > Pinging each other would show both machines loosing connectivity in sync for short periods So did we capture the traffic when issue is occurring ? if so could you show us sample here ? Was this issue only occur on only particular hosts with particular OS installed or others? Could you also verify the version of file TCPIP.SYS on this Windows server 2003 host ? TCP connections fail intermittently when both endpoints are on the same computer in Windows Server 2003 SP2 http://support.microsoft.com/kb/979230/ For more please refer to the article below: List of Network related hotfixes post Service Pack 2 for Windows Server 2003 SP2 http://blogs.technet.com/b/yongrhee/archive/2012/04/01/list-of-network-related-hotfixes-post-service-pack-2-for-windows-server-2003-sp2.aspx Thanks. Tiger LiTiger Li TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
July 20th, 2012 3:10am

Hi Iker, Thanks for posting here. > Pinging each other would show both machines loosing connectivity in sync for short periods So did we capture the traffic when issue is occurring ? if so could you show us sample here ? Was this issue only occur on only particular hosts with particular OS installed or others? Could you also verify the version of file TCPIP.SYS on this Windows server 2003 host ? TCP connections fail intermittently when both endpoints are on the same computer in Windows Server 2003 SP2 http://support.microsoft.com/kb/979230/ For more please refer to the article below: List of Network related hotfixes post Service Pack 2 for Windows Server 2003 SP2 http://blogs.technet.com/b/yongrhee/archive/2012/04/01/list-of-network-related-hotfixes-post-service-pack-2-for-windows-server-2003-sp2.aspx Thanks. Tiger LiTiger Li TechNet Community Support
July 20th, 2012 3:10am

Hi Tiger, thanks for your reply. 1. Part ot the capture (server's IP is 192.168.2.5): 2012/07/19 10:53:02.609 : Reply[1] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:53:03.609 : Reply[2] from 192.168.2.4: bytes=32 time=0.3 ms TTL=64 2012/07/19 10:53:04.609 : Reply[3] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:53:05.609 : Reply[4] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:53:06.609 : Reply[5] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:53:07.609 : Reply[6] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:53:08.609 : Reply[7] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:53:09.609 : Reply[8] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:53:10.609 : Reply[9] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:53:11.609 : Reply[10] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:53:12.609 : Reply[11] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:53:13.609 : Reply[12] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:53:14.609 : Reply[13] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:53:15.608 : Reply[14] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:53:16.608 : Reply[15] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:53:17.608 : Reply[16] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:53:19.452 : 192.168.2.4: request timed out 2012/07/19 10:53:20.452 : 192.168.2.4: request timed out 2012/07/19 10:53:21.452 : 192.168.2.4: request timed out 2012/07/19 10:53:22.452 : 192.168.2.4: request timed out 2012/07/19 10:53:23.452 : 192.168.2.4: request timed out 2012/07/19 10:53:24.452 : 192.168.2.4: request timed out 2012/07/19 10:53:25.452 : 192.168.2.4: request timed out 2012/07/19 10:53:26.452 : 192.168.2.4: request timed out 2012/07/19 10:53:27.452 : 192.168.2.4: request timed out 2012/07/19 10:53:28.451 : 192.168.2.4: request timed out 2012/07/19 10:53:29.451 : 192.168.2.4: request timed out 2012/07/19 10:53:30.451 : 192.168.2.4: request timed out 2012/07/19 10:53:31.451 : 192.168.2.4: request timed out 2012/07/19 10:53:32.451 : 192.168.2.4: request timed out 2012/07/19 10:53:33.451 : 192.168.2.4: request timed out 2012/07/19 10:53:34.451 : 192.168.2.4: request timed out 2012/07/19 10:53:35.451 : 192.168.2.4: request timed out 2012/07/19 10:53:36.451 : 192.168.2.4: request timed out 2012/07/19 10:53:37.451 : 192.168.2.4: request timed out 2012/07/19 10:53:38.451 : 192.168.2.4: request timed out 2012/07/19 10:53:39.451 : 192.168.2.4: request timed out 2012/07/19 10:53:40.451 : 192.168.2.4: request timed out 2012/07/19 10:53:41.451 : 192.168.2.4: request timed out 2012/07/19 10:53:42.451 : 192.168.2.4: request timed out 2012/07/19 10:53:43.451 : 192.168.2.4: request timed out 2012/07/19 10:53:44.451 : 192.168.2.4: request timed out 2012/07/19 10:53:45.450 : 192.168.2.4: request timed out 2012/07/19 10:53:46.450 : 192.168.2.4: request timed out 2012/07/19 10:53:47.450 : 192.168.2.4: request timed out 2012/07/19 10:53:47.450 : Reply[46] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:53:48.450 : Reply[47] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:53:49.450 : Reply[48] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:53:50.450 : Reply[49] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:53:51.450 : Reply[50] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:53:52.450 : Reply[51] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:53:53.450 : Reply[52] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:53:54.450 : Reply[53] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:53:55.450 : Reply[54] from 192.168.2.4: bytes=32 time=1.0 ms TTL=64 2012/07/19 10:53:56.450 : Reply[55] from 192.168.2.4: bytes=32 time=0.3 ms TTL=64 2012/07/19 10:53:57.450 : Reply[56] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:53:58.450 : Reply[57] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:53:59.450 : Reply[58] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:54:00.450 : Reply[59] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:54:01.450 : Reply[60] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:54:02.450 : Reply[61] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:54:03.449 : Reply[62] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:54:04.449 : Reply[63] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:54:05.449 : Reply[64] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:54:06.449 : Reply[65] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:54:07.449 : Reply[66] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:54:08.449 : Reply[67] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:54:09.449 : Reply[68] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:54:10.449 : Reply[69] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:54:11.449 : Reply[70] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:54:12.449 : Reply[71] from 192.168.2.4: bytes=32 time=2.0 ms TTL=64 2012/07/19 10:54:13.449 : Reply[72] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:54:14.449 : Reply[73] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:54:15.449 : Reply[74] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:54:16.449 : Reply[75] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:54:17.449 : Reply[76] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:54:18.449 : Reply[77] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:54:19.449 : Reply[78] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:54:21.448 : 192.168.2.4: request timed out 2012/07/19 10:54:22.448 : 192.168.2.4: request timed out 2012/07/19 10:54:23.448 : 192.168.2.4: request timed out 2012/07/19 10:54:24.448 : 192.168.2.4: request timed out 2012/07/19 10:54:25.448 : 192.168.2.4: request timed out 2012/07/19 10:54:26.448 : 192.168.2.4: request timed out 2012/07/19 10:54:27.448 : 192.168.2.4: request timed out 2012/07/19 10:54:28.448 : 192.168.2.4: request timed out 2012/07/19 10:54:29.448 : 192.168.2.4: request timed out 2012/07/19 10:54:30.448 : 192.168.2.4: request timed out 2012/07/19 10:54:31.448 : 192.168.2.4: request timed out 2012/07/19 10:54:32.448 : 192.168.2.4: request timed out 2012/07/19 10:54:33.448 : 192.168.2.4: request timed out 2012/07/19 10:54:34.448 : 192.168.2.4: request timed out 2012/07/19 10:54:35.448 : 192.168.2.4: request timed out 2012/07/19 10:54:36.448 : 192.168.2.4: request timed out 2012/07/19 10:54:37.447 : 192.168.2.4: request timed out 2012/07/19 10:54:38.447 : 192.168.2.4: request timed out 2012/07/19 10:54:39.447 : 192.168.2.4: request timed out 2012/07/19 10:54:40.447 : 192.168.2.4: request timed out 2012/07/19 10:54:41.447 : 192.168.2.4: request timed out 2012/07/19 10:54:42.447 : 192.168.2.4: request timed out 2012/07/19 10:54:43.447 : 192.168.2.4: request timed out 2012/07/19 10:54:44.447 : 192.168.2.4: request timed out 2012/07/19 10:54:45.447 : 192.168.2.4: request timed out 2012/07/19 10:54:46.447 : 192.168.2.4: request timed out 2012/07/19 10:54:47.447 : 192.168.2.4: request timed out 2012/07/19 10:54:48.447 : 192.168.2.4: request timed out 2012/07/19 10:54:49.447 : 192.168.2.4: request timed out 2012/07/19 10:54:49.447 : Reply[108] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:54:50.447 : Reply[109] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:54:51.447 : Reply[110] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:54:52.447 : Reply[111] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:54:53.447 : Reply[112] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:54:54.447 : Reply[113] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:54:55.446 : Reply[114] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:54:56.446 : Reply[115] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:54:57.446 : Reply[116] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:54:58.446 : Reply[117] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:54:59.446 : Reply[118] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:55:00.446 : Reply[119] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:55:01.446 : Reply[120] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:55:02.446 : Reply[121] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:55:03.446 : Reply[122] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:55:04.446 : Reply[123] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:55:05.446 : Reply[124] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:55:06.446 : Reply[125] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:55:07.446 : Reply[126] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:55:08.446 : Reply[127] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:55:09.446 : Reply[128] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:55:10.446 : Reply[129] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:55:11.446 : Reply[130] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:55:12.445 : Reply[131] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:55:13.445 : Reply[132] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:55:14.445 : Reply[133] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:55:15.445 : Reply[134] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:55:16.445 : Reply[135] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:55:17.445 : Reply[136] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:55:18.445 : Reply[137] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:55:19.445 : Reply[138] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:55:20.445 : Reply[139] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 2012/07/19 10:55:21.445 : Reply[140] from 192.168.2.4: bytes=32 time=0.2 ms TTL=64 Same time period from the other host: Thu Jul 19 10:53:02 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5362 ttl=128 time=0.198 ms Thu Jul 19 10:53:03 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5363 ttl=128 time=0.169 ms Thu Jul 19 10:53:04 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5364 ttl=128 time=0.158 ms Thu Jul 19 10:53:05 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5365 ttl=128 time=0.187 ms Thu Jul 19 10:53:06 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5366 ttl=128 time=0.155 ms Thu Jul 19 10:53:07 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5367 ttl=128 time=0.189 ms Thu Jul 19 10:53:08 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5368 ttl=128 time=0.147 ms Thu Jul 19 10:53:09 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5369 ttl=128 time=0.184 ms Thu Jul 19 10:53:10 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5370 ttl=128 time=0.189 ms Thu Jul 19 10:53:11 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5371 ttl=128 time=0.164 ms Thu Jul 19 10:53:12 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5372 ttl=128 time=0.144 ms Thu Jul 19 10:53:13 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5373 ttl=128 time=0.145 ms Thu Jul 19 10:53:14 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5374 ttl=128 time=0.213 ms Thu Jul 19 10:53:15 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5375 ttl=128 time=0.211 ms Thu Jul 19 10:53:16 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5376 ttl=128 time=0.173 ms Thu Jul 19 10:53:17 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5377 ttl=128 time=0.163 ms Thu Jul 19 10:53:18 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5378 ttl=128 time=0.179 ms Thu Jul 19 10:53:19 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5379 ttl=128 time=0.182 ms Thu Jul 19 10:53:20 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5380 ttl=128 time=0.154 ms Thu Jul 19 10:53:21 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5381 ttl=128 time=0.168 ms Thu Jul 19 10:53:22 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5382 ttl=128 time=0.154 ms Thu Jul 19 10:53:23 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5383 ttl=128 time=0.159 ms Thu Jul 19 10:53:24 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5384 ttl=128 time=0.239 ms Thu Jul 19 10:53:25 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5385 ttl=128 time=0.166 ms Thu Jul 19 10:53:26 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5386 ttl=128 time=0.154 ms Thu Jul 19 10:53:27 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5387 ttl=128 time=0.146 ms Thu Jul 19 10:53:28 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5388 ttl=128 time=0.156 ms Thu Jul 19 10:53:29 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5389 ttl=128 time=0.187 ms Thu Jul 19 10:53:30 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5390 ttl=128 time=0.141 ms Thu Jul 19 10:53:31 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5391 ttl=128 time=0.142 ms Thu Jul 19 10:53:32 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5392 ttl=128 time=0.159 ms Thu Jul 19 10:53:33 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5393 ttl=128 time=0.191 ms Thu Jul 19 10:53:34 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5394 ttl=128 time=0.230 ms Thu Jul 19 10:53:35 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5395 ttl=128 time=0.199 ms Thu Jul 19 10:54:00 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5420 ttl=128 time=0.187 ms Thu Jul 19 10:54:01 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5421 ttl=128 time=0.193 ms Thu Jul 19 10:54:02 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5422 ttl=128 time=0.175 ms Thu Jul 19 10:54:03 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5423 ttl=128 time=0.199 ms Thu Jul 19 10:54:04 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5424 ttl=128 time=0.182 ms Thu Jul 19 10:54:05 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5425 ttl=128 time=0.178 ms Thu Jul 19 10:54:06 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5426 ttl=128 time=0.148 ms Thu Jul 19 10:54:07 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5427 ttl=128 time=0.200 ms Thu Jul 19 10:54:08 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5428 ttl=128 time=0.183 ms Thu Jul 19 10:54:09 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5429 ttl=128 time=0.160 ms Thu Jul 19 10:54:10 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5430 ttl=128 time=0.187 ms Thu Jul 19 10:54:11 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5431 ttl=128 time=0.192 ms Thu Jul 19 10:54:12 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5432 ttl=128 time=0.154 ms Thu Jul 19 10:54:13 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5433 ttl=128 time=0.163 ms Thu Jul 19 10:54:14 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5434 ttl=128 time=0.173 ms Thu Jul 19 10:54:15 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5435 ttl=128 time=0.200 ms Thu Jul 19 10:54:16 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5436 ttl=128 time=0.165 ms Thu Jul 19 10:54:17 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5437 ttl=128 time=0.180 ms Thu Jul 19 10:54:18 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5438 ttl=128 time=0.159 ms Thu Jul 19 10:54:19 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5439 ttl=128 time=0.203 ms Thu Jul 19 10:54:20 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5440 ttl=128 time=0.159 ms Thu Jul 19 10:54:21 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5441 ttl=128 time=0.168 ms Thu Jul 19 10:54:22 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5442 ttl=128 time=0.175 ms Thu Jul 19 10:54:23 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5443 ttl=128 time=0.188 ms Thu Jul 19 10:54:24 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5444 ttl=128 time=0.217 ms Thu Jul 19 10:54:25 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5445 ttl=128 time=0.156 ms Thu Jul 19 10:54:26 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5446 ttl=128 time=0.163 ms Thu Jul 19 10:54:27 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5447 ttl=128 time=0.185 ms Thu Jul 19 10:54:28 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5448 ttl=128 time=0.192 ms Thu Jul 19 10:54:29 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5449 ttl=128 time=0.186 ms Thu Jul 19 10:54:30 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5450 ttl=128 time=0.177 ms Thu Jul 19 10:54:31 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5451 ttl=128 time=0.185 ms Thu Jul 19 10:54:32 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5452 ttl=128 time=0.202 ms Thu Jul 19 10:54:33 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5453 ttl=128 time=0.172 ms Thu Jul 19 10:54:34 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5454 ttl=128 time=0.180 ms Thu Jul 19 10:54:35 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5455 ttl=128 time=0.142 ms Thu Jul 19 10:54:36 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5456 ttl=128 time=0.164 ms Thu Jul 19 10:54:37 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5457 ttl=128 time=0.180 ms Thu Jul 19 10:54:38 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5458 ttl=128 time=0.188 ms Thu Jul 19 10:55:05 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5485 ttl=128 time=0.192 ms Thu Jul 19 10:55:06 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5486 ttl=128 time=0.188 ms Thu Jul 19 10:55:07 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5487 ttl=128 time=0.165 ms Thu Jul 19 10:55:08 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5488 ttl=128 time=0.164 ms Thu Jul 19 10:55:09 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5489 ttl=128 time=0.184 ms Thu Jul 19 10:55:10 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5490 ttl=128 time=0.162 ms Thu Jul 19 10:55:11 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5491 ttl=128 time=0.164 ms Thu Jul 19 10:55:12 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5492 ttl=128 time=0.187 ms Thu Jul 19 10:55:13 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5493 ttl=128 time=0.158 ms Thu Jul 19 10:55:14 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5494 ttl=128 time=0.201 ms Thu Jul 19 10:55:15 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5495 ttl=128 time=0.164 ms Thu Jul 19 10:55:16 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5496 ttl=128 time=0.180 ms Thu Jul 19 10:55:17 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5497 ttl=128 time=0.175 ms Thu Jul 19 10:55:18 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5498 ttl=128 time=0.188 ms Thu Jul 19 10:55:19 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5499 ttl=128 time=0.200 ms Thu Jul 19 10:55:20 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5500 ttl=128 time=0.178 ms Thu Jul 19 10:55:21 CDT 2012: 64 bytes from 192.168.2.5: icmp_req=5501 ttl=128 time=0.169 ms I've got the full 6+ hours capture available if you need it. 2. Just now i've been told yet another IP is failling to communicate with the same server with the exact same problem (this is getting contagious i'm affraid). So far then the issue has happened with XP SP3 the first time, then Linux (x86_64) and now with another XP SP3 client. 3. TCPIP.SYS version on server is: 5.2.3790.4573 (srv03_sp2_gdr.090815-0925) Again, thanks for your help =) "When something is not working as it is supposed to, then it is working as expected" -R
Free Windows Admin Tool Kit Click here and download it now
July 20th, 2012 11:09am

Hi Iker, Thanks for posting here. > 3. TCPIP.SYS version on server is: 5.2.3790.4573 (srv03_sp2_gdr.090815-0925) It does seem a known issue that described in the KB article I posted, could we first patch it and others that listed in that blog post and see how is going ? Thanks. Tiger LiTiger Li TechNet Community Support
July 23rd, 2012 2:13am

Hi, sorry couldn't get on earlier. Surely enough i do have the update installed. Strange how it didn't show symptoms before. I'll check onto that and report back. Thanks Tiger!"When something is not working as it is supposed to, then it is working as expected" -R
Free Windows Admin Tool Kit Click here and download it now
July 26th, 2012 9:54am

Hi, sorry couldn't get on earlier. Surely enough i do have the update installed. Strange how it didn't show symptoms before. I'll check onto that and report back. Thanks Tiger!"When something is not working as it is supposed to, then it is working as expected" -R
July 26th, 2012 9:54am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics