[SOLVED] Wifi Says Connected, but Can't Ping or Access Web - Mint10
Linux MintThis forum is for the discussion of Linux Mint.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Wifi Says Connected, but Can't Ping or Access Web - Mint10
I have Mint 10/Gnome/amd64. All updates applied. My wifi card is ZD1211. There is no problem accessing the web through wired, and I have used the wireless on other wifi networks. It does work w/WinXP, but that installation keeps crashing w/a trap or some other serious error I can't recall now.
I'm temporarily staying at a friend's house, and I can't connect to their wifi. My wifi says "connection established" but Firefox is unable to connect to anything. When I put the mouse cursor over the wifi bar graph, it says,"Wireless network connection 'FriendsNet' active: FriendsNet (100%)". The router gateway address is 192.168.1.1.
Code:
Ping reports:
ping -c 3 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
From 169.254.10.41 icmp_seq=1 Destination Host Unreachable
From 169.254.10.41 icmp_seq=2 Destination Host Unreachable
From 169.254.10.41 icmp_seq=3 Destination Host Unreachable
--- 192.168.1.1 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2003ms
Clicking on Administration/Network:
"Network Settings" has nothing listed for host or domanin name on the General tab. OpenDNS's servers for DNS servers on the DNS tab, and on the Hosts tab this:
The rest of the list is ip6 stuff, but I don't have that connection that I know of.
Windows Vista (on my friend's PC) ipconfig reports:
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\owner>ipconfig
Windows IP Configuration
Code:
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . : home
Link-local IPv6 Address . . . . . : fe80::bd99:b41:95d7:986e%11
IPv4 Address. . . . . . . . . . . : 192.168.1.5
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : somewhere.xx.xx.whoever.com
[can't list actual address for security]
Tunnel adapter Local Area Connection* 6:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Tunnel adapter Local Area Connection* 7:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Tunnel adapter Local Area Connection* 11:
Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:306e:35a9:b884:39de
Link-local IPv6 Address . . . . . : fe80::306e:35a9:b884:39de%13
Default Gateway . . . . . . . . . : ::
Here's the output of mintwifi:
Code:
-------------------------
* I. scanning WIFI PCI devices...
-------------------------
* II. querying ndiswrapper...
-------------------------
* III. querying iwconfig...
lo no wireless extensions.
eth0 no wireless extensions.
wlan0 IEEE 802.11bg ESSID:"WFCM3"
Mode:Ad-Hoc Frequency:2.412 GHz Cell: A6:B6:28:C5:D9:6A
Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:AF28-1AB9-DE78-FCD3-7AD7-48F7-43
Power Management:off
vboxnet0 no wireless extensions.
-------------------------
* IV. querying ifconfig...
eth0 Link encap:Ethernet HWaddr 00:16:d3:84:92:b8
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:60952 errors:0 dropped:0 overruns:0 frame:0
TX packets:35908 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:81411951 (81.4 MB) TX bytes:3345103 (3.3 MB)
Interrupt:20 Base address:0x2000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1998 errors:0 dropped:0 overruns:0 frame:0
TX packets:1998 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:138091 (138.0 KB) TX bytes:138091 (138.0 KB)
vboxnet0 Link encap:Ethernet HWaddr 0a:00:27:00:00:00
inet6 addr: fe80::800:27ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:457 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:28296 (28.2 KB)
vboxnet0:avahi Link encap:Ethernet HWaddr 0a:00:27:00:00:00
inet addr:169.254.1.79 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
wlan0 Link encap:Ethernet HWaddr 00:60:b3:37:d7:27
inet6 addr: fe80::260:b3ff:fe37:d727/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:240 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:56461 (56.4 KB)
wlan0:avahi Link encap:Ethernet HWaddr 00:60:b3:37:d7:27
inet addr:169.254.7.139 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
-------------------------
* V. querying DHCP...
Internet Systems Consortium DHCP Client V3.1.3
Copyright 2004-2009 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/eth0/00:16:d3:84:92:b8
Sending on LPF/eth0/00:16:d3:84:92:b8
Listening on LPF/vboxnet0/0a:00:27:00:00:00
Sending on LPF/vboxnet0/0a:00:27:00:00:00
Listening on LPF/wlan0/00:60:b3:37:d7:27
Sending on LPF/wlan0/00:60:b3:37:d7:27
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on vboxnet0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on vboxnet0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on vboxnet0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on vboxnet0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on vboxnet0 to 255.255.255.255 port 67 interval 20
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on vboxnet0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on vboxnet0 to 255.255.255.255 port 67 interval 2
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 2
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
-------------------------
* VI. querying nslookup google.com...
;; connection timed out; no servers could be reached
Firefox reports:
Code:
Unable to connect
Firefox can't establish a connection to the server at google.com
* The site could be temporarily unavailable or too busy. Try again in a few
moments.
* If you are unable to load any pages, check your computer's network
connection.
* If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.
I used siw.exe for Windows and PC Wizard on my old laptop to try to get info necessary for changing something, but alas, there is nothing there that makes sense to me except that it said the domain name is "home". Do I have to put the domain in or will LM10 in particular and Linux in general automatically connect?
Did you check the settings for your friend's wireless router? You may also want to check NetworkManager (is Mint WiFi a front end to that?) and make sure that
a) it is configured to retrieve IP addresses with DHCP,
b) the router is configured to assign IP addresses with DHCP,
c) if your friend's router has a firewall, make sure that it isn't blocking you,
d) your computer and your friend's computer both use the same default gateway address
Last edited by PhoenixAndThor; 05-11-2011 at 05:35 PM.
My friend's router is not checkable. I said router, but had forgotten that it's a router/modem from the ISP - Verizon. Anyway, he doesn't know about getting into the router's GUI, and not ever having this ISP, I'm guessing that Verizon doesn't want customers changing those settings. Anyway, since my other laptop (too old and slow to do work on) WILL get online via the WinXP it has, I see no problem with the router. Sure, it might be configured only for Windows (is that even possible?), but I cannot change it, and he doesn't have time to call and get it changed. Again, because both my old laptop, and this one can get on in Windows, I don't see it as a router issue. But the Windows on this cpu keeps crashing so I need to get Linux working on the wifi.
I tried to run nm-applet, but it says already running. Though three is no window of it. So I can't check any settings in NetworkManager.
I do not know how to check any of this. Again, how can Windows be allowed (on this network) wireLESSLY or wired, and Linux allowed WIRED, but Linux not allowed wireLESSLY?
Quote:
a) it is configured to retrieve IP addresses with DHCP,
b) the router is configured to assign IP addresses with DHCP,
c) if your friend's router has a firewall, make sure that it isn't blocking you,
d) your computer and your friend's computer both use the same default gateway address
BTW, the only way to use the wired connection is to practically sit on the floor in a hunched over position, and I'm too old for that, so I need the wireless connection to work, so I can sit at the table.
This thread was one of the first ones I saw when google searching my problem. It is marked [SOLVED] but there was no solution provided in the thread. I eventually figured my problem out and so want to share what my solution was in case anybody else has a similar problem.
/etc/resolve.conf is auto-generated, so go ahead, nuke the contents and put
Code:
nameserver 8.8.8.8
in there. 8.8.8.8 is the Google public DNS. If this gets you internet connection, then the problem is that your system isn't auto-detecting nameservers correctly (like mine was). Simply manually configure the connection. I was using the networkmanager applet to manage my connections, so I was able to right-click the wifi applet, and select "Edit Connections"
From there, I went to the Wireless tab and edited my connection. For ease of use, I just told it to use DHCP for addresses only and manually specified the DNS Server and DHCP Client ID.
Obviously, if you manually set all this information yourself and you still have troubles, this isn't your solution.
At any rate, since I'm a comcast customer, I have my DNS servers set to Comcast's, but the Google DNS or your own favorite DNS server will work here.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
