how-to block ads
|
bcastner
Premium,VIP,MVM
join:2002-09-25
Chevy Chase, MD
clubs: 
 ·Verizon Online DSL
| reply to jmorlan
Re: [XP Pro] Erratic wirless connection after SP3
jmoralan,
Are you using the Linksys Client as well? In other words, you have XP's Wireless Zero disabled, and all configuration is done through a Linksys utility?
1. This is not preferred. It would be better to use only the drivers from Linksys, and allow XP to natively configure the adapter and all Network associations.
2. If you do not wish to do this, use your Laptop as the test case. I would download the Stand-alone XP SP3 Redistributable, or the ISO. (See the first response in this very thread).
Next, head to the Linksys site and be sure you have the most recent driver release.
Next, Use Add or Remove Programs, and Uninstall the Linksys client software.
Next, using the ISO or standalone Network Installation Package, install SP3.
Reboot twice when done.
Finally, install the Linksys adapter client software, just as if it were a brand new installation of the adapter.
======================
My guess is that you are seeing Authentication failures. There are some bugged reports from the Beta period on certain Broadcom chipset based adapters. Linksys went back and forth between Broadcom and Atheros chipsets, so what is in yours is tough to say.
See if the following helps:
• Run the command “Netsh ras set tracing * enabled”
• Reproduce the problem
• Run the command “Netsh ras set tracing * disabled”
• The logs will be at %windir%\tracing
Open the log file with Notepad. What I am looking for is a repeated sequence that resembles the following:
3660] 14:54:26:121: Interface {DCC9F2F1-DF04-4A97-92E9-6F264781F65C}:
[3660] 14:54:26:121: IP Address: 192.168.30.43
[3660] 14:54:26:121: HrAddIPCharacteristics {DCC9F2F1-DF04-4A97-92E9-6F264781F65C}: HrDHCPAcquiring=1 (Done), dwRetryTime=345597, NonZeroAddress=1, bDhcpEnabled=1, dwCharacteristics=NCCF:0x00101009
[3124] 14:54:26:137: NETMAN: GetProperties-WZCQueryGUIDNCSState (NETMANNCS=NCS_CONNECTED WZCNCS=NCS_AUTHENTICATION_FAILED hr=0x00000000 fZeroConfEnabled=0)
-- OR -- like this:
3124] 14:54:26:293: Interface {DCC9F2F1-DF04-4A97-92E9-6F264781F65C}:
[3124] 14:54:26:293: IP Address: 192.168.30.43
[3124] 14:54:26:293: HrAddIPCharacteristics {DCC9F2F1-DF04-4A97-92E9-6F264781F65C}: HrDHCPAcquiring=1 (Done), dwRetryTime=345597, NonZeroAddress=1, bDhcpEnabled=1, dwCharacteristics=NCCF:0x00101009
[3124] 14:58:33:053: INetConnectionRefresh: ConnectionStatusChanged call [NCS_AUTHENTICATING]
[2480] 14:58:33:053: NETMAN: LanEventWorkItem (Type = CONNECTION_STATUS_CHANGE)
[1560] 14:58:33:053: INetConnectionRefresh: ConnectionStatusChanged call [NCS_AUTHENTICATING]
[2480] 14:58:33:053: NETMAN: LanEventWorkItem-WZCQueryGUIDNCSState (NETMANNCS=NCS_CONNECTED WZCNCS=NCS_AUTHENTICATING hr=0x00000000 fZeroConfEnabled=0)
[2480] 14:58:33:053: NOTIFY: Notifying ConnectionStatusChange... (pSink=0x0576241C) [NCS_AUTHENTICATING]
[2480] 14:58:33:162: HrWZCDLGNotify: Not sending status to WZC, because fZeroConfEnabled is FALSE and ncs is NCS_AUTHENTICATING
Here you have a third-party Wireless configuration service being used instead of the native service. Authentication with the router/AP is clearly failing intermittently.
1. Start Services.msc; be sure the new service "Wired AutoConfig" is set to Manual or Disabled.
2. Be sure that "Enable IEEE 802.1x authentication" on the client adapter settings is Disabled.
3. Re-enter the WEP/WAP key for the Network Connection. (This is a theory of mine about the changes in the Cryptographic services of XP3). This will force a new write of the key to your registry.
Reboot and test.
If you could, after doing all of the above, and still no joy, let me know. Be sure to re-enable logging to capture a small log, and send back to the Forum a small snippet where it shows a connection failure.
But at the moment, at least from bugged reparts on XP SP3, there is not a lot of complaints about intermittent wireless issues.
I promise to review any logs you submit.
Best wishes,
Bill Castner
--
============
MS-MVP 2004 - -2008, ASAP Member
Users Helping Users
| |
jmorlan
Hmm... That's funny.
Premium
join:2001-02-05
Pacifica, CA
·Pacific Bell - SBC
| Thank you again for the detailed analysis and suggestions. The laptop was using a LinkSys (Odyssey) client with Wireless Zero disabled which was recommended by LinkSys. I got rid of the LinkSys software and enabled Wireless Zero and that works much better in my opinion. Unfortunately that configuration is unsupported, but I don't care.
After that I installed SP3 on the laptop with no issues.
Then I tried SP3 again on the wireless desktop which had the original wireless connection problems. That system was using XP's Wireless Zero already as recommended by the manufacturer. I updated the driver for the wireless adapter first and then installed SP3 from a CD with no antirvirus running. I am please to report that the wireless connection has been solid for the last several days.
I've printed out your last post in case the issue arises in the future. At this time I am unable to reproduce the problem or provide you with any logs.
Thanks again.
--
If America has an official philosophy, it surely includes the belief in individualism, competition, private property, democracy, freedom, and a deep faith in education. This social philosophy is called "liberalism." GKM (1936) | |
|
