[colug-432] network help with Windows 7

Rick Hornsby richardjhornsby at gmail.com
Thu Jul 12 21:22:23 EDT 2012


> Please excuse this not being a Linux question--if it's too egregious to ask about Windows 7, please say so  :)

We all have to deal with Windows at some point or another - knowing how to troubleshoot a networking issue is useful regardless of the OS, so let me see what I can do here.

> Networking and hardware stuff looks normal.

Except when it doesn't... :)

>    Autoconfiguration IPv4 Address. . : 169.254.105.172(Preferred) 

This address is usually what Windows assigns to the NIC when it can't talk to a DHCP server.  This is the only NIC in that list that I can see that appears to possibly have a link.

> Wireless LAN adapter Wireless Network Connection: 
>  
>    Connection-specific DNS Suffix  . : wowway.com 
>    Description . . . . . . . . . . . : Intel(R) Centrino(R) Advanced-N 6250 AGN 
>    Physical Address. . . . . . . . . : 64-80-99-34-A6-F0 
>    DHCP Enabled. . . . . . . . . . . : Yes 
>    Autoconfiguration Enabled . . . . : Yes 
>    Link-local IPv6 Address . . . . . : fe80::dc89:f5ad:da2e:69ac%11(Preferred) 
>    Autoconfiguration IPv4 Address. . : 169.254.105.172(Preferred) 
>    Subnet Mask . . . . . . . . . . . : 255.255.0.0 
>    Default Gateway . . . . . . . . . : 
>    DNS Servers . . . . . . . . . . . : 64.233.222.2 
>                                        64.233.222.7 
>    NetBIOS over Tcpip. . . . . . . . : Enabled 

It says DHCP enabled, but the first thing that I'm going to suspect is that the DHCP client isn't configured properly - or is configured at least partially with manual settings.  It is highly unlikely to get DNS servers from DHCP but not get an IP address, a proper subnet mask, or a router/gateway address.

Notice there that there is no gateway address at all.  Given that you said the wireless NIC successfully negotiated a link to more than one wireless AP at different locations, I strongly suspect a client misconfiguration of some sort (as opposed to something wrong with her wireless AP at her house) - most likely that the DHCP client is disabled, or at least partially disabled.

Make sure that she's really connected to the wireless AP.  (Really, getting a wired hardline to the network eliminates so many things that could go wrong and will make this much easier to troubleshoot initially.  The wired ethernet links are easier to get working - and once that it is working it may solve the wireless issue or make it easier to figure out.)

One of the steps I might try if nothing jumps out at you is to actually manually configure her wireless NIC with an IP address, a subnet mask, a gateway address, and DNS servers.  Match everything that your computer is set to, except change the last octet of her IP address to something like yours +1.  So if your IP address is 192.168.0.100, make hers 192.168.0.101.  That might not work.  If yours is 100, try making hers 50 or 200.  What you're trying to do is manually assign her a unique address for the network.

Note, that this is not a fix but rather a troubleshooting step.  That configuration is almost certain to break the minute she leaves your house.

Once you get that all set up, run ipconfig again to make sure the settings took correctly.  Now try to ping your computer from hers:

ping 192.168.0.100 (or whatever yours is).  

If you get a response, then there is something whacko with the DHCP client on her computer and you'll need to dig into why.  Try pinging the gateway address (usually ends in .1), then try pinging one of the DNS servers, then try pinging something like 128.146.1.7 (one of the OSU servers), try going out to the internet and see what happens.

If none of that works, then I would start to suspect something deeper - either the configuration set above isn't right, there is some additional piece of software blocking, the drivers for the NIC are screwy (a windows update could have screwed something up here), possibly an OS (this is Windows after all) being dumb issue, or *maybe* hardware.

If that does work, however, make sure you set her NIC to be "Automatically configured" for any many of those parameters as it will let you and try again.

I'm a bit surprised that a NIC misconfiguration with respect to the DHCP client would be at fault here, since you indicated that two different adapters exhibited the same issue.  What happens to the output of ipconfig if you use an ethernet cable to connect her laptop to the network?

Is it possible that she installed some piece of software recently that claimed to "fix" her computer, but is really blocking network traffic?  Like a detective, ask lots and lots of questions about what led up to the event - what was she doing, when did it start, when did she first notice it, did she install something new, etc?



On Jul 12, 2012, at 17:35 , Jim Baker wrote:

> Please excuse this not being a Linux question--if it's too egregious to ask about Windows 7, please say so  :)
> 
> My buddy brought me her laptop, Toshiba Satellite E305-s1995, I think it was new last year.  
> As of a couple days ago, she can't connect to the internet.  She can connect locally to wifi 
> (at her house and at mine), and can connect locally via ethernet cable, but can't venture out to the web.
> 
> Networking and hardware stuff looks normal.  I surfed a bunch of forums, and found in one case 
> somebody's Norton Antivirus was stopping them.  She has a program like that called Kapersky, so
>  I uninstalled it, and rebooted.  
> 
> Still no good.  I'm appending an ipconfig /all text file.  Any other ideas?  Thanks!
> 
> Jim 
> 
> Here's the ipconfig:
> 
> Microsoft Windows [Version 6.1.7601] 
> Copyright (c) 2009 Microsoft Corporation.  All rights reserved. 
>  
> C:\Users\Tammy>ipconfig/all 
>  
> Windows IP Configuration 
>  
>    Host Name . . . . . . . . . . . . : Tammy-PC 
>    Primary Dns Suffix  . . . . . . . : 
>    Node Type . . . . . . . . . . . . : Peer-Peer 
>    IP Routing Enabled. . . . . . . . : No 
>    WINS Proxy Enabled. . . . . . . . : No 
>    DNS Suffix Search List. . . . . . : wowway.com 
>  
> Wireless LAN adapter Wireless Network Connection 3: 
>  
>    Media State . . . . . . . . . . . : Media disconnected 
>    Connection-specific DNS Suffix  . : 
>    Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter # 
> 2 
>    Physical Address. . . . . . . . . : 64-80-99-34-A6-F1 
>    DHCP Enabled. . . . . . . . . . . : Yes 
>    Autoconfiguration Enabled . . . . : Yes 
>  
> Wireless LAN adapter Wireless Network Connection 2: 
>  
>    Media State . . . . . . . . . . . : Media disconnected 
>    Connection-specific DNS Suffix  . : 
>    Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter 
>    Physical Address. . . . . . . . . : 64-80-99-34-A6-F1 
>    DHCP Enabled. . . . . . . . . . . : Yes 
>    Autoconfiguration Enabled . . . . : Yes 
>  
> Ethernet adapter Local Area Connection 2: 
>  
>    Media State . . . . . . . . . . . : Media disconnected 
>    Connection-specific DNS Suffix  . : 
>    Description . . . . . . . . . . . : Intel(R) Centrino(R) WiMAX 6250 
>    Physical Address. . . . . . . . . : 64-D4-DA-2A-C7-87 
>    DHCP Enabled. . . . . . . . . . . : Yes 
>    Autoconfiguration Enabled . . . . : Yes 
>  
> Ethernet adapter Local Area Connection: 
>  
>    Media State . . . . . . . . . . . : Media disconnected 
>    Connection-specific DNS Suffix  . : columbus.rr.com 
>    Description . . . . . . . . . . . : Atheros AR8152/8158 PCI-E Fast Ethernet C 
> ontroller (NDIS 6.20) 
>    Physical Address. . . . . . . . . : E8-9A-8F-35-EB-66 
>    DHCP Enabled. . . . . . . . . . . : Yes 
>    Autoconfiguration Enabled . . . . : Yes 
>  
> Wireless LAN adapter Wireless Network Connection: 
>  
>    Connection-specific DNS Suffix  . : wowway.com 
>    Description . . . . . . . . . . . : Intel(R) Centrino(R) Advanced-N 6250 AGN 
>    Physical Address. . . . . . . . . : 64-80-99-34-A6-F0 
>    DHCP Enabled. . . . . . . . . . . : Yes 
>    Autoconfiguration Enabled . . . . : Yes 
>    Link-local IPv6 Address . . . . . : fe80::dc89:f5ad:da2e:69ac%11(Preferred) 
>    Autoconfiguration IPv4 Address. . : 169.254.105.172(Preferred) 
>    Subnet Mask . . . . . . . . . . . : 255.255.0.0 
>    Default Gateway . . . . . . . . . : 
>    DNS Servers . . . . . . . . . . . : 64.233.222.2 
>                                        64.233.222.7 
>    NetBIOS over Tcpip. . . . . . . . : Enabled 
>  
> Tunnel adapter isatap.{9C8810D9-37CF-4874-BE29-A749AF4BBFF3}: 
>  
>    Media State . . . . . . . . . . . : Media disconnected 
>    Connection-specific DNS Suffix  . : 
>    Description . . . . . . . . . . . : Microsoft ISATAP Adapter 
>    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 
>    DHCP Enabled. . . . . . . . . . . : No 
>    Autoconfiguration Enabled . . . . : Yes 
>  
> Tunnel adapter isatap.{8FD032E8-7BBF-4074-8311-0C6DA2AE6B7A}: 
>  
>    Media State . . . . . . . . . . . : Media disconnected 
>    Connection-specific DNS Suffix  . : 
>    Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2 
>    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 
>    DHCP Enabled. . . . . . . . . . . : No 
>    Autoconfiguration Enabled . . . . : Yes 
>  
> Tunnel adapter Teredo Tunneling Pseudo-Interface: 
>  
>    Media State . . . . . . . . . . . : Media disconnected 
>    Connection-specific DNS Suffix  . : 
>    Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface 
>    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 
>    DHCP Enabled. . . . . . . . . . . : No 
>    Autoconfiguration Enabled . . . . : Yes 
>  
> Tunnel adapter isatap.wowway.com: 
>  
>    Media State . . . . . . . . . . . : Media disconnected 
>    Connection-specific DNS Suffix  . : wowway.com 
>    Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3 
>    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 
>    DHCP Enabled. . . . . . . . . . . : No 
>    Autoconfiguration Enabled . . . . : Yes
> 
> _______________________________________________
> colug-432 mailing list
> colug-432 at colug.net
> http://lists.colug.net/mailman/listinfo/colug-432




More information about the colug-432 mailing list