On Sun, 22 Apr 2007 22:25:38 -0000, "Jeff Gaines"
<(E-Mail Removed)> mused:
>I have an IBM R50e laptop which has an Intel 2200 b/g Wi Fi chip-set.
>
>When I turn it in (or come out of standby/hibernation) it takes an age to
>connect to my Netgear WAP. Net Stumbler picks up the signal straightaway
>but I have to open the Intel Wi Fi manager app, turn it off nd on, select
>a profile and reset its parameters and after 5 minutes or so I get
>connected. Once its connected it works very well.
>
>I have the latest Intel drivers installed. I have switched from WEP to WPA
>security and it seems slower since the switch but is a pain with WEP as
>well.
>
Mine sometimes takes a while to connect as well (also an Intel 2200BG
mini-PCI card but on a Panasonic CF-50). Right clicking the icon in
the system tray and selecting the profile often gives it a kick up the
arse when first connecting. For some reason, it doesn't always pick up
an IP address although it is connected to the network. Not sure
whether that's Windows, the router, or the card but doing a
cmd>ipconfig /release and renew sorts it out straight away.
I only really get the extended connection problems when the laptop's
been away from the network and has to try and remember what it's
doing. If it's just been rebooted then it seems to come up straight
away.
>Is this a feature of 2200b/g? Would I be better off getting a Netgear
>PCMCIA card (pre n to match the WAP)?
>
Why not just get anoter card to fit internally to the laptop? I don't
like things protuding from mine.
>Any thoughts or ideas would be appreciated, it's making using the laptop a
>real PITA!
Computers are a PITA whatever, ITYM _more_ of a PITA.

--
Regards,
Stuart.