UNSOLVED

Bozz5384

updated

22 years ago

B

Bozz5384

13 Posts

0

4926

October 23rd, 2004 03:00

Problems connecting to Wireless AP's

I've been struggling lately to get quick, consistant connections when using my C400 w/Intel Pro 2200BG when I attempt to connect to various wireless networks.
 
It took me 30 mins. to get a connection at my home, had to keep disabling the adaptor, re-enabling, doing a connection repair, etc.  Finally, it just connected!
 
Same thing happened while using a public hotspot as well, never did get it to connect.  I get a signal between my computer and access point/router, but cannot obtain a good IP address.  Keeps giving a 169.xx address.
 
What is the secret to consistant, quick connections when using different wireless networks at work, home, public places?
 
Thanks,
Bozz
 
  • Jerry Park

    695 Posts

    213

    0

    Posted October 23rd, 2004 13:00

    I have experienced trouble when switching sites with my wireless connection. Found that the [wireless card? windows registry? or something] tries to keep the gateway address at the former site. Of course, if the card is trying to connect to a gateway or DHCP server that no longer exists, the card can't get an IP address. The expected behavior is, of course, for the card to broadcast a request for IP, etc.

    I suspect that this is a bug in the OS, but don't really know.

    I use devcon.exe to restart the device to overcome the problem.

    Devcon.exe is Microsoft's command line device manager:
    http://support.microsoft.com/default.aspx?scid=kb;en-us;311272

    I create a logon script to run which restarts my wireless device. Have had no further problems:

    REM Restart Wireless connection to force broadcast IP request.
    REM Don't restart if ping successful.
    ping -n 1 yahoo.com
    if %errorlevel% EQU 0 goto end
    devcon restart PCI\VEN_14E4*
    :end

    To set logon/logoff scripts, Start|run|gpedit.msc
  • Bozz5384

    13 Posts

    213

    0

    Posted October 26th, 2004 00:00

    Jerry,
     
    Thanks for the help -- I downloaded and tried the Devcon.exe from the command line, and here is my problem:
     
    *** I don't know what the device is called to add it to the parameter on the command line?  It is an Intel Pro Wireless 2200BG mini-PCI card.  I did the restart of intel* and it restarted some video stuff, etc. that wanted a reboot.  To my knowledge, it did not restart the wireless card. 
     
    This problem is driving me nuts, about 25% of the time I cannot get connected to 1 of 3 wireless networks I frequent (home, office, friends)
     
    How do I come up with a device name to restart?
     
    Thanks,
    Jason (Bozz)
  • Jerry Park

    695 Posts

    213

    0

    Posted October 26th, 2004 20:00

    Use devcon to loccate and name the device. If it is an internal wireless card, it will use the PCI interface. So run devcon find PCI*

    The device will be identified as a wireless device.

    If not internal, just run devcon find *