Windows XP TCP Problem

Computing.Net > Forums > Networking > Windows XP TCP Problem

Original Message

Name: xscript
Date: May 16, 2005 at 13:58:07 Pacific
Subject: Windows XP TCP Problem
OS: Windows XP SP1a
CPU/Ram: NA

Comment:

I have a very strange and annoying problem that I can't fix.
I have a wireless router, two computers connected. One computer is fine, however the other one has started displaying some odd connection problems ever since I installed MSN Messenger 7. It loses connection almost immediantly after opening Internet Explorer.
I started troubleshooting.
I boot up the machine and set a continuous ping to the router.
I can ping the router (or any other IP / URL to outside world for that matter) exactly 11 times and then I receive the 'Request Timed Out' message.
I can hit the 'repair connection' button on Network Connections and my PC will ping the router another 11 times before 'Request Timed Out'.
Corrupt winsock or TCP/IP I thought, so I ran netdiag /test:winsock /v,
This failed here:
NetBT transports test. . . . . . . : Failed
List of NetBt transports currently configured:
[FATAL] Unable to retrieve transport list from Redir. [NERR_WkstaNotStarted]
I disabled my connection and decided to remove the winsock registry entries so fresh replacements would be created at the next reboot.
Removed :
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Winsock and delete it; just below that, see HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Winsock2
Rebooted.
Reinstalled TCP/IP using c:\windows\inf\nettcpip.inf
Reenabled my connection without rebooting, tested by continuous ping and all is fine,
Rebooted.
Problem is back, I can repair the connection and it will ping exactly 11 times and then request times out.
I ran the System File Checker, no new news there.
I have attached the results from netdiag and I have shown the 11 pings then request times out, every time it comes back, it's because I run the repair on the TCP/IP connection.
I'm doing that to send this request for help!!
Has anyone any suggestions other than to reinstall OS?
Many Thanks
Shaun

Report Offensive Message For Removal

Response Number 1

Name: xscript
Date: May 16, 2005 at 13:58:52 Pacific
Subject: Windows XP TCP Problem

Reply: (edit)

Gathering IPX configuration information.
Querying status of the Netcard drivers... Passed
Testing Domain membership... Passed
Gathering NetBT configuration information.
Gathering Winsock information.
Tests complete.

Computer Name: SHAUNSPC
DNS Host Name: SHAUNsPC
DNS Domain Name: (null)
System info : Windows 2000 Professional (Build 2600)
Processor : x86 Family 6 Model 6 Stepping 2, AuthenticAMD
Hotfixes :
Installed? Name
Yes KB810217
Yes KB821557
Yes KB823182
Yes KB823559
Yes KB823980
Yes KB824105
Yes KB824141
Yes KB824146
Yes KB824151
Yes KB825119
Yes KB826939
Yes KB828035
Yes KB828741
Yes KB833987
Yes KB834707-IE6SP1-20040929.091901
Yes KB835732
Yes KB837001
Yes KB839645
Yes KB840315
Yes KB840374
Yes KB840987
Yes KB841356
Yes KB841533
Yes KB841873
Yes KB842773
Yes KB873333
Yes KB873339
Yes KB873376
Yes KB883357
Yes KB885835
Yes KB885836
Yes KB887472
Yes KB888113
Yes KB888302
Yes KB890175
Yes KB890859
Yes KB890923-IE6SP1-20050225.103456
Yes KB891781
Yes KB892944
Yes KB893066
Yes KB893086
Yes Q147222
Yes Q323255
Yes Q328310
Yes Q329048
Yes Q329115
Yes Q329170
Yes Q329390
Yes Q329441
Yes Q329834
Yes Q331953
Yes Q810565
Yes Q810577
Yes Q810833
Yes Q811114
Yes Q811493
Yes Q811630
Yes Q814033
Yes Q815021
Yes Q817287
Yes Q817606

Netcard queries test . . . . . . . : Passed
Information of Netcard drivers:
---------------------
Description: Wireless-G PCI Adapter
Device: \DEVICE\{7DCDFF25-5842-4B39-9011-0AF213AA7DD3}
Media State: Connected
Device State: Connected
Connect Time: 00:20:13
Media Speed: 54 Mbps
Packets Sent: 1477
Bytes Sent (Optional): 0
Packets Received: 1880
Directed Pkts Recd (Optional): 1340
Bytes Received (Optional): 0
Directed Bytes Recd (Optional): 0
---------------------
[PASS] - At least one netcard is in the 'Connected' state.
Per interface results:
Adapter : Wireless Network Connection 6
Adapter ID . . . . . . . . : {7DCDFF25-5842-4B39-9011-0AF213AA7DD3}
Netcard queries test . . . : Passed

Global results:

Domain membership test . . . . . . : Passed
Machine is a . . . . . . . . . : Standalone Workstation
Netbios Workgroup name . . . . : LIZARD
Dns domain name is not specified.
Dns forest name is not specified.
Domain Guid. . . . . . . . . . : {00000000-0000-0000-0000-000000000000}
Logon User . . . . . . . . . . : Administrator
Logon Domain . . . . . . . . . : SHAUNSPC

NetBT transports test. . . . . . . : Failed
List of NetBt transports currently configured:
[FATAL] Unable to retrieve transport list from Redir. [NERR_WkstaNotStarted]

Winsock test . . . . . . . . . . . : Passed
The number of protocols which have been reported : 2
Description: MSAFD Tcpip [TCP/IP]
Provider Version :2
Max message size : Stream Oriented
Description: MSAFD Tcpip [UDP/IP]
Provider Version :2
Max UDP size : 65507 bytes

The command completed successfully

Report Offensive Follow Up For Removal

Response Number 2

Name: xscript
Date: May 16, 2005 at 13:59:17 Pacific
Subject: Windows XP TCP Problem

Reply: (edit)

Pinging www.l.google.com [66.102.9.99] with 32 bytes of data:
Reply from 66.102.9.99: bytes=32 time=40ms TTL=238
Reply from 66.102.9.99: bytes=32 time=41ms TTL=238
Reply from 66.102.9.99: bytes=32 time=76ms TTL=238
Reply from 66.102.9.99: bytes=32 time=39ms TTL=238
Reply from 66.102.9.99: bytes=32 time=59ms TTL=238
Reply from 66.102.9.99: bytes=32 time=40ms TTL=238
Reply from 66.102.9.99: bytes=32 time=40ms TTL=238
Reply from 66.102.9.99: bytes=32 time=38ms TTL=238
Reply from 66.102.9.99: bytes=32 time=53ms TTL=238
Reply from 66.102.9.99: bytes=32 time=90ms TTL=238
Reply from 66.102.9.99: bytes=32 time=69ms TTL=238
Request timed out.
Reply from 66.102.9.99: bytes=32 time=42ms TTL=238
Reply from 66.102.9.99: bytes=32 time=39ms TTL=238
Reply from 66.102.9.99: bytes=32 time=43ms TTL=238
Reply from 66.102.9.99: bytes=32 time=44ms TTL=238
Reply from 66.102.9.99: bytes=32 time=95ms TTL=238
Reply from 66.102.9.99: bytes=32 time=87ms TTL=238
Reply from 66.102.9.99: bytes=32 time=47ms TTL=238
Reply from 66.102.9.99: bytes=32 time=50ms TTL=238
Reply from 66.102.9.99: bytes=32 time=42ms TTL=238
Reply from 66.102.9.99: bytes=32 time=68ms TTL=238
Reply from 66.102.9.99: bytes=32 time=87ms TTL=238
Request timed out.
Reply from 66.102.9.99: bytes=32 time=161ms TTL=238
Reply from 66.102.9.99: bytes=32 time=73ms TTL=238
Reply from 66.102.9.99: bytes=32 time=41ms TTL=238
Reply from 66.102.9.99: bytes=32 time=43ms TTL=238
Reply from 66.102.9.99: bytes=32 time=53ms TTL=238
Reply from 66.102.9.99: bytes=32 time=42ms TTL=238
Reply from 66.102.9.99: bytes=32 time=59ms TTL=238
Reply from 66.102.9.99: bytes=32 time=38ms TTL=238
Reply from 66.102.9.99: bytes=32 time=39ms TTL=238
Reply from 66.102.9.99: bytes=32 time=65ms TTL=238
Reply from 66.102.9.99: bytes=32 time=66ms TTL=238
Request timed out.
Reply from 66.102.9.99: bytes=32 time=1539ms TTL=238
Reply from 66.102.9.99: bytes=32 time=43ms TTL=238
Reply from 66.102.9.99: bytes=32 time=54ms TTL=238
Reply from 66.102.9.99: bytes=32 time=62ms TTL=238
Reply from 66.102.9.99: bytes=32 time=42ms TTL=238
Reply from 66.102.9.99: bytes=32 time=57ms TTL=238
Reply from 66.102.9.99: bytes=32 time=51ms TTL=238
Reply from 66.102.9.99: bytes=32 time=90ms TTL=238
Reply from 66.102.9.99: bytes=32 time=76ms TTL=238
Reply from 66.102.9.99: bytes=32 time=41ms TTL=238
Reply from 66.102.9.99: bytes=32 time=42ms TTL=238
Request timed out.
Request timed out.

Report Offensive Follow Up For Removal

Response Number 3

Name: lebanese_007
Date: May 21, 2005 at 19:28:32 Pacific
Subject: Windows XP TCP Problem

Reply: (edit)

I have almost the same problem... i have HP pavilion ze5400 with on-board wireless NIC card 802.11g. connected to a linksys router 802.11b. it has been working fine for the last 2 years but all of the sudden, i noticed slow connection.. sometimes it takes for ever to open a webpage, so i pingged the router "ping 192.168.2.1 -t" , the result is not good.. here is a sample of what i get
--------------------
Reply from 192.168.2.1: bytes=32 time=4ms TTL=255
Reply from 192.168.2.1: bytes=32 time=2ms TTL=255
Reply from 192.168.2.1: bytes=32 time=3ms TTL=255
Reply from 192.168.2.1: bytes=32 time=2ms TTL=255
Reply from 192.168.2.1: bytes=32 time=2ms TTL=255
Request timed out.
Reply from 192.168.2.1: bytes=32 time=4ms TTL=255
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.2.1: bytes=32 time=2ms TTL=255
Reply from 192.168.2.1: bytes=32 time=2ms TTL=255
Reply from 192.168.2.1: bytes=32 time=3ms TTL=255
Reply from 192.168.2.1: bytes=32 time=4ms TTL=255
Reply from 192.168.2.1: bytes=32 time=10ms TTL=255
Reply from 192.168.2.1: bytes=32 time=3ms TTL=255
Reply from 192.168.2.1: bytes=32 time=2ms TTL=255
Reply from 192.168.2.1: bytes=32 time=3ms TTL=255
Reply from 192.168.2.1: bytes=32 time=3ms TTL=255
Reply from 192.168.2.1: bytes=32 time=4ms TTL=255
Reply from 192.168.2.1: bytes=32 time=6ms TTL=255
Reply from 192.168.2.1: bytes=32 time=7ms TTL=255
Request timed out.
Request timed out.
Reply from 192.168.2.1: bytes=32 time=6ms TTL=255
Request timed out.
Request timed out.
Reply from 192.168.2.1: bytes=32 time=20ms TTL=255
Reply from 192.168.2.1: bytes=32 time=4ms TTL=255
Request timed out.
Reply from 192.168.2.1: bytes=32 time=10ms TTL=255
Reply from 192.168.2.1: bytes=32 time=2ms TTL=255
Reply from 192.168.2.1: bytes=32 time=3ms TTL=255
Reply from 192.168.2.1: bytes=32 time=2ms TTL=255
Reply from 192.168.2.1: bytes=32 time=2ms TTL=255
Reply from 192.168.2.1: bytes=32 time=13ms TTL=255
Reply from 192.168.2.1: bytes=32 time=4ms TTL=255
Reply from 192.168.2.1: bytes=32 time=2ms TTL=255
Ping statistics for 192.168.2.1:
Packets: Sent = 146, Received = 120, Lost = 26 (17% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 20ms, Average = 3ms
------------------------
I ran windows update for the wireless NIC card, didn't find anything..
I have the lasted firmware on the router.
i tried so many things but didn't work, i even used the recovery CDs that came with the laptop... that didn't help.
i have another Laptop that it is almost identical to mine...it is ze5200 and it is working fine.
Any help please...
Thanks in advance

Report Offensive Follow Up For Removal

Response Number 4

Name: xscript
Date: May 24, 2005 at 01:54:15 Pacific
Subject: Windows XP TCP Problem

Reply: (edit)

It's not quite the same problem as the one I had, mine would ping exactly 11 times and then I had to run the windows repair TCP/IP connection and it would ping another 11 times.
Finally, after many hours of fighting, I gave in and reinstalled the OS to a seperate partition and transferred all my documents across, did mean I had to reinstall all the applications, but I've not got a stable and reliable connection.
It may be this is your only alternative, what is the signal strengh like on the laptop? How about swopping the PCMCIA in the devices and seeing if that makes a difference?
Have you run netdiag?
Xscript

Report Offensive Follow Up For Removal


Windows XP network problem Windows XP Networking Problem Windows XP LAN Problems?? Warcraft 2, Windows XP, IPX Network Windows XP log on problem	Windows XP and ICS? Is it just me? Problems interconnecting windows xp windows 2000 network problem Windows XP network problems windows xp networking problem

vnc working with d-link ...

how to share PowerlIne US...

Use following form to reply to current message:

Name: From My Computing.Net Settings E-Mail: From My Computing.Net Settings Subject: Windows XP TCP Problem

Comments:

  Homepage URL (*): 
Homepage Title (*): 
         Image URL:

XP Showing less ram

WinXP 32bit to WinXP 64bit

Drivers for clie PEG-NX70V/E

New to vista

Cloning Laptop XP to bigger Drive

All Posts Awaiting Replies