Results 1 to 10 of 10
  1. #1
    Lounger
    Join Date
    Dec 2009
    Location
    Wellington NZ
    Posts
    32
    Thanks
    6
    Thanked 0 Times in 0 Posts

    laptop losing wireless connectivity, odd address in route table

    My mother has a simple home network with a wireless modem (at 192.168.2.1) and a laptop running WinXP (with a static IP of 192.168.2.2). When she switches the laptop on and connects to the internet to send/receive mail the connection is successful, but usually within 5 or 10 minutes she loses connectivity and has to repair the network connection. She has to do this repeatedly throughout the day.
    If her laptop is connected to the ethernet port on the modem the connection persists with no issues. (That isn't a tenable workaround for her.)
    My phone connects to the wireless network and does not drop out when her laptop does.

    I managed to capture the network routing tables (netstat -r on her laptop) before and after she loses network connectivity:
    Before (network is fine):

    Code:
    ===========================================================================
    Interface List
    0x1 ........................... MS TCP Loopback interface
    0x3 ...00 01 4a 1a 21 8d ...... Intel(R) PRO/100 VE Network Connection - Packet Scheduler Miniport
    0x20002 ...00 0e 35 dd 24 55 ...... Intel(R) PRO/Wireless 2200BG Network Connection - Packet Scheduler Miniport
    ===========================================================================
    ===========================================================================
    Active Routes:
    Network Destination        Netmask          Gateway       Interface  Metric
              0.0.0.0          0.0.0.0      192.168.2.1     192.168.2.2       25
            127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1        1
          192.168.2.0    255.255.255.0      192.168.2.2     192.168.2.2       25
          192.168.2.2  255.255.255.255        127.0.0.1       127.0.0.1       25
        192.168.2.255  255.255.255.255      192.168.2.2     192.168.2.2       25
            224.0.0.0        240.0.0.0      192.168.2.2     192.168.2.2       25
      255.255.255.255  255.255.255.255      192.168.2.2               3        1
      255.255.255.255  255.255.255.255      192.168.2.2     192.168.2.2        1
    Default Gateway:       192.168.2.1
    ===========================================================================
    Persistent Routes:
      None
    
    Route Table

    After (network broken):

    Code:
    ===========================================================================
    Interface List
    0x1 ........................... MS TCP Loopback interface
    0x2 ...00 0e 35 dd 24 55 ...... Intel(R) PRO/Wireless 2200BG Network Connection - Packet Scheduler Miniport
    0x3 ...00 01 4a 1a 21 8d ...... Intel(R) PRO/100 VE Network Connection - Packet Scheduler Miniport
    ===========================================================================
    ===========================================================================
    Active Routes:
    Network Destination        Netmask          Gateway       Interface  Metric
              0.0.0.0          0.0.0.0      192.168.2.1     192.168.2.2       25
            127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1        1
          169.254.0.0      255.255.0.0      192.168.2.2     192.168.2.2        1
          192.168.2.0    255.255.255.0      192.168.2.2     192.168.2.2       25
          192.168.2.2  255.255.255.255        127.0.0.1       127.0.0.1       25
        192.168.2.255  255.255.255.255      192.168.2.2     192.168.2.2       25
            224.0.0.0        240.0.0.0      192.168.2.2     192.168.2.2       25
      255.255.255.255  255.255.255.255      192.168.2.2               3        1
      255.255.255.255  255.255.255.255      192.168.2.2     192.168.2.2        1
    Default Gateway:       192.168.2.1
    ===========================================================================
    Persistent Routes:
     None
    
    Route Table
    
    The only significant difference I can see is the introduction of 169.254.0.0 in the table when the connection is broken. As I understand it this suggests that somewhere there is a device trying to connect to the laptop bypassing the network that already exists, and this connection is getting in the way of the wireless modem.

    When the network is like this her laptop can ping localhost, 127.0.0.1 and 192.168.2.2 successfully. It times out trying to ping 192.168.2.1 (the modem).

    At this point I've run out of tests in my mental toolkit and I don't know where to look next; the laptop is not physically connected to anything so the vagrant device must be trying to connect wirelessly. What would be sensible things to try now?

    Thanks for any suggestions
    T
    Last edited by aquatarkus; 2012-08-02 at 14:29.

  2. #2
    Lounger
    Join Date
    Dec 2009
    Location
    Wellington NZ
    Posts
    32
    Thanks
    6
    Thanked 0 Times in 0 Posts
    My apologies for the original appearance of the previous post; I'm still learning how to format messages and screwed that one up badly. I think it makes more sense now :-)

  3. #3
    Super Moderator jwitalka's Avatar
    Join Date
    Dec 2009
    Location
    Minnesota
    Posts
    6,794
    Thanks
    117
    Thanked 799 Times in 720 Posts
    Try assigning a different wireless broadcast channel in your router that is at least 4 numbers away from the current setting. (1, 7, or 11). If its set to Auto, set it to Channel 1. If that doesn't work, set it to channel11.

    Jerry

  4. #4
    Super Moderator
    Join Date
    Jun 2011
    Location
    New England
    Posts
    4,748
    Thanks
    171
    Thanked 649 Times in 572 Posts
    I believe the existence of 169.254.0.0 typically just indicates that DHCP has failed to allocate an external IP address from the ISP: 169.254.0.0/16 addresses explained

    Bruce

  5. #5
    Lounger
    Join Date
    Dec 2009
    Location
    Wellington NZ
    Posts
    32
    Thanks
    6
    Thanked 0 Times in 0 Posts
    OK, an update, because I still haven't been able to fix this properly.

    I have tried three things:
    1. changing the wifi channel (as suggested in this thread); no difference.
    2. having the wifi adapter use a dynamically assigned IP instead of the static 192.168.2.2; no difference.
    3. reading around on the 169.254.0.0 address, the appearance of which seems to correlate with the loss of wireless connectivity, I wondered if the plugandplay service might be a factor, so I disabled the service and rebooted (dire Windows warnings about how this is a bad idea notwithstanding). This did seem to improve things: with PnP enabled the wifi connection would typically drop within 5 minutes while without it the laptop stayed connected for an hour. I doubt if disabling PnP permanently is the correct solution, although perhaps it indicates where to look next.

  6. #6
    Plutonium Lounger Medico's Avatar
    Join Date
    Dec 2009
    Location
    USA
    Posts
    12,631
    Thanks
    161
    Thanked 936 Times in 856 Posts
    Does she have any USB devices attached all the time when this is occurring? Perhaps there is a device plugged in that is causing this.
    BACKUP...BACKUP...BACKUP
    Have a Great Day! Ted


    Sony Vaio Laptop, 2.53 GHz Duo Core Intel CPU, 8 GB RAM, 320 GB HD
    Win 8 Pro (64 Bit), IE 10 (64 Bit)


    Complete PC Specs: By Speccy

  7. #7
    Lounger
    Join Date
    Dec 2009
    Location
    Wellington NZ
    Posts
    32
    Thanks
    6
    Thanked 0 Times in 0 Posts
    Hi

    No, no usb devices at all. It's a very simple network: an ADSL router offering wired and wireless connection, a laptop and a printer. The printer is connected wirelessly and has a dynamically allocated IP address (but the printer is not a factor here because I have replicated the problem starting with everything powered off and never turning the printer on).

    When connected to the router via ethernet her network connection stays up forever. When connected via wireless the connection drops within a few minutes. She usually has time to send and receive email then she has to repair the network connection. Or time to check the weather in the browser before needing to repair the connection in order to check the news (but the problem is not related to her email or browser clients because I have replicated the problem starting from cold and simply pinging IP addresses in a command shell).

    Connecting permanently via cable isn't really satisfactory for her.

    She knows how to repair the connection, and it normally isn't a huge drama when it happens, apart from happening over and over again. But it's annoying that I can't fix it, and I'm half expecting to have to recover from some unfinished chain of updates when the connection drops in the middle of something critical one day :-/

  8. #8
    Administrator
    Join Date
    Jun 2010
    Location
    Portugal
    Posts
    12,519
    Thanks
    152
    Thanked 1,398 Times in 1,221 Posts
    Did you make sure she has the most up to date drivers available? Is the wireless adapter an integrated one or an add-on?

  9. #9
    Lounger
    Join Date
    Dec 2009
    Location
    Wellington NZ
    Posts
    32
    Thanks
    6
    Thanked 0 Times in 0 Posts
    Her laptop is an old(ish) Sony VAIO with on-board Intel PRO/100 VE wireless adapter. I'm reasonably certain that the drivers are up to date but I'll check that again next time I see her.

  10. #10
    Administrator
    Join Date
    Jun 2010
    Location
    Portugal
    Posts
    12,519
    Thanks
    152
    Thanked 1,398 Times in 1,221 Posts
    Intel updates drivers fairly regularly and it seems there is recent software: http://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Network+C onnectivity&ProductLine=Intel%C2%AE+Desktop+Adapte rs&ProductProduct=Intel%C2%AE+PRO%2f100+VE+Desktop +Adapter

    I
    t may also happen the opposite - new software, especially drivers, added through Windows Update, that has adverse effects.

  11. The Following User Says Thank You to ruirib For This Useful Post:

    aquatarkus (2012-09-06)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •