1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Vista and Wireless connectivity problems

Discussion in 'Networking (Hardware & Software)' started by DPG, 2009/04/10.

  1. 2009/04/10
    DPG

    DPG Inactive Thread Starter

    Joined:
    2009/04/10
    Messages:
    2
    Likes Received:
    0
    Hello,

    Have run out of ideas on this, so any help appreciated.

    I have a wireless network that has been working fine for over a year. Being connected to very successfully by 3 Vista machines and 2 XP machines.

    It currently uses WEP 128 bit security (yes I know I should move away from WEP and will do shortly, but had other things on the go).

    Approximately a month ago one Vista machine stopped connecting. It can connect when wired into the router and can connect to other wireless networks, but not to this one.

    I have done the usual, deleted the profile, rebooted the router, upgraded the the driver, stopped AV and firewall. All to no effect.

    A week ago another Vista machine did exactly the same thing.

    Things in common:

    The error: 5 bars on the wireless connection, but with limited or no connectivity (no IP address being issued, so defaults to 169......)

    Both are HP laptops, but completely different specs and ages

    Both use ZoneAlarm for AV and firewall

    Both have MS updates turned on by default.

    The third Vista machine is the same spec and config as the first machine to stop - but that still works normally.

    The machine that I am writing this on, is actually the second machine to fail and I am using one of my neighbours unsecured wireless networks, so this proves that the machine is working fine. As the router is working fine with the other 3 machines, again it proves that the router is OK.

    The fact that both the Vista machines work fine when directly attached proves that the base config is fine with respect to this router (which is only a year old).

    I am guessing that there is some sort of corruption with the configs, that even deleting does not allow me to fix.

    Any ideas?

    Thanks in advance
     
    DPG,
    #1
  2. 2009/04/11
    BurrWalnut

    BurrWalnut Well-Known Member Alumni

    Joined:
    2003/03/05
    Messages:
    628
    Likes Received:
    8
    Have you tried using a different SSID?
     

  3. to hide this advert.

  4. 2009/04/11
    DPG

    DPG Inactive Thread Starter

    Joined:
    2009/04/10
    Messages:
    2
    Likes Received:
    0
    Hello there,

    No I haven't.

    My thinking behind that is simple.

    If this were only one machine, then yes I think that would be logical. However, from the way that I am thinking, there are 5 machines. The time delay between the 1st and 2nd failing would indicate that:

    1. This is not as a result of any changes that I have made to any part of the system (indeed, the 1st machine had not been touched by myself for about 2 months and the 2nd machine is my personal machine and I had not made any changes other than data changes in several weeks.).

    2. This is not as a result of an MS patch release (it could of course still be a corruption just one month apart on each machine).

    3. This is not as a result of a ZoneAlarm change or any other auto software update.

    Happy to understand however, why you think changing the SSID might fix it, as I am always keen to learn.

    Thanks for the response.
     
    DPG,
    #3
  5. 2009/04/11
    BurrWalnut

    BurrWalnut Well-Known Member Alumni

    Joined:
    2003/03/05
    Messages:
    628
    Likes Received:
    8
    The Ethernet cable works so it must be the wireless connection:

    1. It cannot be a faulty wireless adapter or driver as you can connect to your neighbour’s router. So, that leaves the wireless part of the router (SSID and/or Security key) or the stored connection, hence my suggestion to change the SSID.

    2. Longshots, which you’ve probably tried, include:
    2A. Change the channel number, 1 and 11 are usually the best.

    2B. Go to Control Panel > Classic View > Network and Sharing Center > View Status alongside the Wireless Connection > Properties at the bottom > Network Tab and scroll down to Internet Protocol Version 4 (TCP/IPv4) and double-click it. In the General Tab put dots in ‘Obtain an IP address automatically’ and in ‘Obtain DNS server address automatically’. OK, etc. Repeat it for Internet Protocol Version 6 (TCP/IPv6).

    2C. Click the Windows Orb (Start) > All Programs > Accessories and right-click Command Prompt, then ‘Run as Administrator’. Type netsh winsock reset (note the two spaces) and press Enter. Restart the computer.

    2D. Switch off and unplug the router/modem and the computer. Wait five minutes, plug it back in and when the lights stabilise, start the computer.
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.