[CS-FSLUG] Windows 7 conectability issues.

[Tim Young]

Well, of course, on a Linux list we all like to nod our head and 
smile at people's Windows issues.  Especially when they are someone 
else's problems.

For what it's worth, my wife's XP box was not getting an IP from my 
home network.  Yup.  Gotta be XP.  Oops.  Turned out my Linux server 
was out of disk-space and could not update the DHCP leases file. 
(drat.  It was a Linux issue, not an XP one.)

     - Tim

On 2/1/2013 6:54 PM, davidm at hisfeet.net wrote:
>
> You guys are awesome!  I post questionms on other forums, and seldom get
> any reply at all. So Thanks from the bottom of my heart.  to all who
> replied. Since the computer isn't mine, it has gone 'home', but I'll check
> out your answers as soon as I get it back.
>
> DavidM
>
>> Hi,
>> One "standard" wireless thing I have seen is to disable the wireless
>> adapter and re-enable it.  I have seen many Windows 7 wireless
>> adapters that are fixed with this one.
>>
>> I would second the "disable IPv6" comment.  Windows 7 prefers IPv6
>> where it thinks it can get away with it.
>>
>> If that fails, I would try disabling the windows (or antivirus)
>> firewall temporarily to see if that is the issue.
>>
>> If that fails, download a copy of wireshark (either by using a wired
>> connection or on a different computer and transferring it over).
>> Wireshark is like tcpdump on Linux.  Connect via wireless, run
>> wireshark doing a "capture" and do a number of DNS queries.  You can
>> probably use one of these filters:
>>     udp.port==53
>>     tcp.port==53
>>     ip.host=[his IP address here]
>>
>> For example, if his IP is 192.168.0.23
>>     ip.host=192.168.0.23
>>
>> Most DNS uses udp, but some uses tcp.  If you find that it is using
>> tcp instead of UDP, that will tell us something.  If you do not see
>> anything going out, that will tell us something.  If you see it going
>> out on UDP, but nothing coming back (if it goes from his IP out, but
>> we do not see any responses from the name-server) that tells us
>> something.  Also, look at the IP address of the name-server to make
>> sure it is actually using the name-server you expect it to be using.
>>
>>       - Tim
>>
>> Ps. I assume you will be seeing my dad down there in Mexico in a few
>> days.  If so, greet him for me.  I will be down in Mitla, Oaxaca from
>> Sun - Fri teaching Linux security to some folks.  Looking forward to
>> a brief visit to Mexico.  It has been a number of years.
>>
>>
>> On 2/1/2013 11:15 AM, davidm at hisfeet.net wrote:
>>> We are now in Mexico connected to the TELMEX system, which is the
>>> landline
>>> 'almost monopoly' system. Got everything in our house working just fine,
>>> even my wifes winxp laptop on wifi.  But the pastor here has a win7
>>> laptop.  Strange (to me ) thing.
>>>
>>> It connects by wifi to the modem, nd can png the modem, and other
>>> computers (ours) connected to the modem either by cable, or wifi. It can
>>> even ping internet sites by ip number, but not by name.  Will even show
>>> some of the sites when I put the ip number in the URL line of the
>>> browser.
>>> It seems that it won't connect to any Name Server.
>>>
>>> I managed to change the DNS settings in the win7 machine, but still
>>> won't
>>> connect to any wan by name. I also changed the DNS in the modem, but no
>>> change.
>>>
>>> Any ideas what could keep it from connecting?  Oh, by the way, t works
>>> fine when connected by cable to the modem.
>>>
>>> DavidM
>>>
>>>
>>> _______________________________________________
>>> ChristianSource FSLUG mailing list
>>> Christiansource at ofb.biz
>>> http://cs.uninetsolutions.com
>>>
>>
>> _______________________________________________
>> ChristianSource FSLUG mailing list
>> Christiansource at ofb.biz
>> http://cs.uninetsolutions.com
>>
>
>
> _______________________________________________
> ChristianSource FSLUG mailing list
> Christiansource at ofb.biz
> http://cs.uninetsolutions.com
>