WinXP wireless problem...
in [Wireless Internet]
|
Prev: 150N USB
Next: Security. WPA?/-TKIP /-CCMP
From: Jeff Liebermann on 25 Nov 2008 00:48 On Mon, 24 Nov 2008 18:09:57 -0800 (PST), jnkmail009(a)yahoo.com wrote: >Anyone familiar with WinXP enough to know what exactly it does with >network connections at each login? Something is causing it to get >lost. This is a clean and fresh WinXP install, so it must be >something in Windows. Yep, but you didn't bother to supply any makers, models, or numbers, of your hardware, so I can't really offer specific suggestions. The easiest way to determine the cause of failure is to enable Wireless Zero Config logging. <http://www.microsoft.com/technet/network/wifi/wlansupp.mspx> It's quite an ordeal slogging through the voluminous logs produced by WZC, but the answer should be in there somewhere. However, before you embark on that adventure, you may have a point about DHCP. Start -> run -> cmd <enter> ipconfig What do you get before and after you "login". -- Jeff Liebermann jeffl(a)cruzio.com 150 Felker St #D http://www.LearnByDestroying.com Santa Cruz CA 95060 http://802.11junk.com Skype: JeffLiebermann AE6KS 831-336-2558
From: jnkmail009 on 25 Nov 2008 07:59 On Nov 25, 12:48 am, Jeff Liebermann <je...(a)cruzio.com> wrote: > On Mon, 24 Nov 2008 18:09:57 -0800 (PST), jnkmail...(a)yahoo.com wrote: > >Anyone familiar with WinXP enough to know what exactly it does with > >network connections at each login? Something is causing it to get > >lost. This is a clean and fresh WinXP install, so it must be > >something in Windows. > > Yep, but you didn't bother to supply any makers, models, or numbers, > of your hardware, so I can't really offer specific suggestions. > > The easiest way to determine the cause of failure is to enable > Wireless Zero Config logging. > <http://www.microsoft.com/technet/network/wifi/wlansupp.mspx> > It's quite an ordeal slogging through the voluminous logs produced by > WZC, but the answer should be in there somewhere. > > However, before you embark on that adventure, you may have a point > about DHCP. > Start -> run -> cmd <enter> > ipconfig > What do you get before and after you "login". Wow, thanks! Your reply is leading me very close to the fix. I forgot all about WZC as I had been using the DLink client. Using WZC, everything works like it should. I don't have to "bump" the connection after logging on. So... It looks like it must be with the DLink drivers and client. I'll try weeding that out now. Before tinkering with the DLink stuff, I have a new suspicion first. I just noticed in Device Manager that the wireless card is mislabeled as "Wireless PCI Adapter #2" even though there is just one card installed. I now remember Windoze mislabling another piece of hardware (soundcard) once as a "#2" and it caused some weird problems. I'll try deleting it and rebooting. Thanks!
From: jnkmail009 on 25 Nov 2008 11:22 Ok. Got that fixed. It was the same issue as with the soundcard, multiple entries in Device Manager! For future reference (probably mine!), to get to "unconnected" and unused entries: cmd set devmgr_show_nonpresent_devices=1 start devmgmt.msc (Show hidden devices on the View) (Delete the ghosts) F'n Windoze! Thanks!
From: Bill Kearney on 26 Nov 2008 07:19 > I just noticed in Device Manager that > the wireless card is mislabeled as "Wireless PCI Adapter #2" even > though there is just one card installed. At some point, probably due to drivers, the card appeared different 'enough' for the OS to treat it as such. Since you don't mention what sort of network interface it's not possible to pinpoint why. But a device moved to a different USB port, or card slot would definitely do it. Combine that with screwing around with drivers and it'll certainly happen.
From: Jeff Liebermann on 26 Nov 2008 10:51
On Wed, 26 Nov 2008 07:19:04 -0500, "Bill Kearney" <wkearney99(a)hotmail.com> wrote: >> I just noticed in Device Manager that >> the wireless card is mislabeled as "Wireless PCI Adapter #2" even >> though there is just one card installed. > >At some point, probably due to drivers, the card appeared different 'enough' >for the OS to treat it as such. >Since you don't mention what sort of network interface it's not possible to >pinpoint why. But a device moved to a different USB port, or card slot >would definitely do it. Combine that with screwing around with drivers and >it'll certainly happen. An OS or driver update also does it, sometimes. I just finished setting up XP SP1 on a Compaq V6000 laptop with a built in Broadcom wireless card, using the original HP recovery CD set. After initial installation, it would connect nicely using wireless. Of course, any recovery CD that's older than 30 seconds requires hundreds of megabloats of updates for everything. After multiple rounds of updates for the OS, apps, drivers, and junkware, it now connects using "wireless something #2". Apparently, this happened during an update of either WZC or the Broadcom drivers. No hardware juggling or screwing around required. -- Jeff Liebermann jeffl(a)cruzio.com 150 Felker St #D http://www.LearnByDestroying.com Santa Cruz CA 95060 http://802.11junk.com Skype: JeffLiebermann AE6KS 831-336-2558 |