The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Intel 2200BG Wireless Connection Problem

    Discussion in 'Networking and Wireless' started by Dandy_Don, Jan 20, 2008.

  1. Dandy_Don

    Dandy_Don Newbie

    Reputations:
    0
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    5
    Hi Folks,

    I am looking for any assistance with the following problem.

    I have a Toshiba Laptop, Centrino, think its the M60 although not 100%, and it has an Intel 2200BG wireless card built in. The system is using Windows XP, SP 2.

    I have recently moved house, and was promised free internet by the landlord, via his wireless router.

    When I search for the router, I can see it fine. He gave me a WEP key, and when I tried it, it said connected with Limited or No Connectivity. I tried to repair and nothing happened. I disabled my Firewall and nothing happened. I then tried a different WEP code, which was completely wrong, and I received the same outcome.

    I guessed at this point that the WEP key was causing havoc, so the landlord disabled the WEP key, and I tried to connect to the Unsecured network. This caused the same outcome.

    After some research on the net, I discovered that the router wasnt assigning an appropriate IP address.

    I changed the TCP/IP settings from obtain automatic to the following:

    IP: 192.168.1.37

    DNS: 195.170.0.1
    DNS2: 195.170.2.2

    The DNS settings are those provided by the ISP , Otenet, over here in Greece.

    It then said I was connected, with Excellent signal, and would send packets, but absolutely nothing being received.

    I have connected to other Otenet wireless points here with absolutely no problem. The landlord said that a couple of others have had the same problem, yet 2 guys upstairs, plus the landlord and his son, can connect to the network fine - 3 of them wirelessly.

    Is there something I should be doing here, and I am missing? I dont believe its a card problem, as I have used the card several times in recent weeks on different networks, and had no problems. And the fact that other people have had similar problems, coupled with the fact that others have had no problems, is leaving me absolutely stumped... can only assume its a settings problem?

    Thanks in advance,

    Kris
     
  2. Tranquility

    Tranquility Notebook Consultant

    Reputations:
    80
    Messages:
    227
    Likes Received:
    0
    Trophy Points:
    30
    I have a D-Link wireless router and four laptops in the house. One laptop has the 2200. Every other laptop establishes and maintains its connection without issue. The operating systems include W2K, XP Pro, XP Home, & Vista. The 2200 is on Pro. I've used the OS and Intel's software to manage the card. I've changed between every form of encryption offered by the D-Link to no encryption. I've turned SSID broadcast on and off. I've used and disabled DHCP. I've set the laptop's TCP/IP manually.

    The 2200 has issues. Sometimes connecting, sometimes not. Sometimes rebooting will get it to connect and sometimes not. I tried to put in an earlier 2100 but the BIOS complains it is not compatible. I think the "incompatibility" is nothing more than Intel protecting its Centrino label, even though the 2100 is from an earlier Centrino.

    I'd love a solution too, but I doubt it exists. I have the latest driver. I haven't seen any kind of firmware update at Intel. The problem lies with the card, its firmware, or its driver. It's really disappointing because it's in my best laptop with my favorite OS and the BIOS wont let me be rid of it.
     
  3. Tranquility

    Tranquility Notebook Consultant

    Reputations:
    80
    Messages:
    227
    Likes Received:
    0
    Trophy Points:
    30
  4. blue68f100

    blue68f100 Notebook Virtuoso

    Reputations:
    1,020
    Messages:
    3,439
    Likes Received:
    0
    Trophy Points:
    105
    I would not setup a manual connection because you have no idea what the DHCP is giving out. Have 2 the same will cause nothing but trouble. Beside the lanlord can set the range to any thing he likes, except public IP are not recommended unless he has been issued a range for his use. With limited connectivity look at the gateway and dns info. Test by pinging a site with IP and name (ping yahoo.com). If you do not have a gateway you can not ping anything outside your internal network. If you can ping IP gateway is good. If you can not ping yahoo.com your dns server settings are wrong. Use "ipconfig /all" from the cmd prompt to check your settings.

    I do not like the Intel card management, takes up way to many resources. I would disable it and start MS Zero config up.

    Is he actually using WEP and NOT WPA? I would remove the connection from my locations. reboot the nb. then try connecting to it. If he gave you hex code, it should not be case sensitivity. If it's actually WPA it can be, then I would ask him if there are any caps or other chrs and confirm the key. Some routers allow you to show the key, not ****. If so copy and past to a notepad and transfer the key. I would also push for WPA if he is WEP. Vista does not like WEP.
     
  5. Johnny T

    Johnny T Notebook Nobel Laureate

    Reputations:
    6,092
    Messages:
    12,975
    Likes Received:
    201
    Trophy Points:
    481
    Interesting enough my 2200BG works well in most places...including my D-Link router at home... o_O

    And external PCMCIA wireless card could be an option...they dont cost too much.
     
  6. blue68f100

    blue68f100 Notebook Virtuoso

    Reputations:
    1,020
    Messages:
    3,439
    Likes Received:
    0
    Trophy Points:
    105
    Sometimes you need to clean out old connection locations. Including the one you are have problems with. If they have not changed the SSID it's possiable you have 2 locations with the same ID but different security.