Connecting to wireless network, but not to internet

[Nikkiru]

Still hoping somebody has an idea for me to try.

[JafoFubar]

I'm having the same problem. Go to System/Preferences/Network Connections, go to the Wireless tab, highlight the connection you want, click Edit and go to the IPv4 tab. On mine, when I connect, the Method is set to Shared to Other Computers. So I'm not getting a DHCP IP address and I'm not getting DNS settings. But it is connected to the router. When I change that setting to Automatic (DHCP), it then tries to connect and then a box pops up prompting me to enter my WEP key. I enter it but it won't connect. The box pops back up prompting me to enter my WEP key. I'm stuck at this point.

[JafoFubar]

OK. It's working now. I had to change it to DHCP automatic and then open Terminal and run sudo dhclient and it connects fine now. I rebooted a couple of times and it reconnects every time so I guess I'm done.

[Nikkiru]

OK. It's working now. I had to change it to DHCP automatic and then open Terminal and run sudo dhclient and it connects fine now. I rebooted a couple of times and it reconnects every time so I guess I'm done.

Wow, that brought up a whole other problem.

I opened a terminal and typed in "sudo dhclient". Then it prompted for a password, but the window didn't accept input from my keyboard.

nikkiru@ubuntu:~$ sudo dhclient
[sudo] password for nikkiru:

Guess that's a whole other thread, eh? Or am I doing something obviously wrong?

[JafoFubar]

I'm not sure if you're messing with me or not so I'll hope you're not and answer anyway. When you type your password in Terminal, it doesn't show anything but it is accepting the input. You're used to seeing ***** or something, but it doesn't show in Terminal like that. Just type your password and hit Enter.

[Scooter_X]

I have had that same trouble with my machine. I think there is a timing issue in the 9.1 code. What I have done is (after the wireless interface connects) run the command sudo ifdown wlan0 then sudo ifup wlan0. I then immediately have an internet connection.

Dunno exactly what's wrong but that works every time for me.

Tom Stephenson

Hey thanks for posting that. It worked for me. I'm going to try, obviously, but when you reboot, do you have to do that all over again? Or is it usually just once for you after installing ubuntu for the first time?

EDIT: Actually, for some reason, only google.com wanted to come up. Everything else didn't... I'm going to keep poking around... But thanks all the same.

[Scooter_X]

Darn. JafoFubar, yours didn't work for me either. I'll keep poking around some more...

[dmizer]

I suspect this is just a DNS issue.

Can you ping google by IP address? If so, just configure your DNS server entries for OpenDNS: https://store.opendns.com/setup/operatingsystem/ubuntu

[JafoFubar]

I agree that it's a DNS issue. More specifically though, it's a DHCP issue. If they're connecting to their router, as I was, but their network card is not set to DHCP, it won't work. Yes, they can set it manually but I don't think that's what they're looking for. I could be wrong.

[Nikkiru]

OK. It's working now. I had to change it to DHCP automatic and then open Terminal and run sudo dhclient and it connects fine now. I rebooted a couple of times and it reconnects every time so I guess I'm done.

I was already set at Automatic. I did try running sudo dhclient, but it seems not to be recognizing the connection either.

This is what I got the first time I ran it, while I was connected to the same server I'm posting this from:

nikkiru@ubuntu:~$ sudo dhclient
[sudo] password for nikkiru:
Internet Systems Consortium DHCP Client V3.1.2
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

SIOCSIFFLAGS: No such file or directory
SIOCSIFFLAGS: No such file or directory
Listening on LPF/wlan0/00:90:4b:7e:b2:be
Sending on LPF/wlan0/00:90:4b:7e:b2:be
Listening on LPF/eth0/00:11:43:47:68:59
Sending on LPF/eth0/00:11:43:47:68:59
Listening on LPF/wlan1/00:e0:4c:03:bf:03
Sending on LPF/wlan1/00:e0:4c:03:bf:03
Sending on Socket/fallback
receive_packet failed on wlan0: Network is down
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
send_packet: Network is down
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
send_packet: Network is down
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
send_packet: Network is down
DHCPOFFER of 192.168.1.100 from 192.168.1.1
DHCPREQUEST of 192.168.1.100 on wlan1 to 255.255.255.255 port 67
DHCPACK of 192.168.1.100 from 192.168.1.1
bound to 192.168.1.100 -- renewal in 41781 seconds.
nikkiru@ubuntu:~$ ^C
nikkiru@ubuntu:~$

Then I rebooted to windows to make sure the connection was working. When I booted back into Karmic, and saw that I was showing a connection, I tried again. No connection through FF again, and sudo dhclient gave a somewhat different report:

nikkiru@ubuntu:~$ sudo dhclient
[sudo] password for nikkiru:
Internet Systems Consortium DHCP Client V3.1.2
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

SIOCSIFFLAGS: No such file or directory
SIOCSIFFLAGS: No such file or directory
Listening on LPF/wlan0/00:90:4b:7e:b2:be
Sending on LPF/wlan0/00:90:4b:7e:b2:be
Listening on LPF/eth0/00:11:43:47:68:59
Sending on LPF/eth0/00:11:43:47:68:59
Listening on LPF/wlan1/00:e0:4c:03:bf:03
Sending on LPF/wlan1/00:e0:4c:03:bf:03
Sending on Socket/fallback
DHCPREQUEST of 192.168.1.100 on wlan1 to 255.255.255.255 port 67
receive_packet failed on wlan0: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
send_packet: Network is down
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
send_packet: Network is down
DHCPREQUEST of 192.168.1.100 on wlan1 to 255.255.255.255 port 67
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
send_packet: Network is down
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 21
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
send_packet: Network is down
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19
send_packet: Network is down
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 19
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
send_packet: Network is down
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
send_packet: Network is down
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 16
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
nikkiru@ubuntu:~$

Given what I already posted on page 1, can anybody make heads or tails of this?