Ping works, WWW doesn't

**co0lingFir3** · January 11th, 2010

Hi folks,
i bought a Asus-Netbook Eee Pc 1005HA PU17 recently and am pretty happy with it. As I installed Ubuntu 9.10 on it today I was unable to get the Internet connection to work. I am able to connect to a network (wired as well as wireless) but cannot open Websites (the connection times out) or update my ubuntu install. What's really strange is that pinging IPs and websites works just fine.

I tried different Kernels (2.6.31-16 and 2.6.32) as well as installing backports.

My network chips are Atheros AR8132 for Ethernet and Atheros AR9285 for WLAN.

Furthermore the Internet works perfectly in Windows 7 and even in Moblin 2.1.

Would be great if anyone would have an advice. Thanks!

**Iowan** · January 11th, 2010

My latest favorite villain is MTU - this thread shows a troubleshooting technique.

**changingstate** · January 11th, 2010

I suspect something is blocking outbound connections to port 80 from your machine.

Do you have something like this in either ~/.profile or /etc/profile?

Code:

export  http_proxy=http://proxy-server.mycorp.com:3128/

To check ~/.profile , please use :

Code:

gedit ~/.profile

For /etc/profile use :

Code:

sudo gedit /etc/profile

It could also be a firewalling rule. A look at what you've got set may be very illuminating. You can list them using :

Code:

sudo iptables -L

Additionally, you're connecting via DHCP, yes? This post ( http://ubuntuforums.org/showthread.php?t=911963 ) suggests if you set up a static address, an error in the gateway setting can cause this.

**co0lingFir3** · January 12th, 2010

Thanks for your hints, but the problem still persists.

@Iowan: I tried pinging -s 32 and -s 1600 and both of them succeeded. So I don't think it's an MTU issue.

@changingstate: I didn't add anything to my profile files since it's a fresh install. There is no export statement in them. Also the iptables seem to be empty. Yes, I am connecting via DHCP.

This is the output of wget www.google.com (it is stuck after that):

Code:

wget www.google.com > result
--2010-01-12 00:37:58--  http://www.google.com/
Resolving www.google.com... 74.125.39.147
Connecting to www.google.com|74.125.39.147|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://www.google.it/ [following]
--2010-01-12 00:37:58--  http://www.google.it/
Resolving www.google.it... 1.0.0.0
Connecting to www.google.it|1.0.0.0|:80...

Seems to be a DNS problem imho. I double checked the systems proxy config and it's set to "Direct Connection to the Internet".

**changingstate** · January 12th, 2010

Aaah, I've seen this with a flaky DNS server on an old D-Link router I have floating around somewhere. It utterly loathed the DNS requests from my debian 2.2 system but was quite happy with the windows systems.

IIRC, I hacked /etc/resolv.conf to access my ISP's nameserver directly, rather than the D-Link router. It produced a little more traffic on the network, but it fixed the issue.

**SteveHillier** · January 12th, 2010

Adding my three ha'p'n'th it does sound a little like DNS issues or firewall.
I hate this answer but have you rebooted your router since setting up the system. There are times when these bits of kit get their underwear twisted and rebooting can often provide a resolution.