I can only visit google, all other sites do not load with rare exceptions.

hydrodev · 01-01-2009, 06:20 PM

Fire Fox on Ubuntu 8.04, 8.10 AND Fedora 10
Comcast Internet
linksys 802.11b wireless, but i am wired into it.
ASUS A8S-X mother, on board LAN.
Successful connection to network.

I have checked my DNS entries, they are all correct.
I have checked MTU settings, set them to 1500 and 1492, same problem.
I can ping any url successfully.
I can NOT surf to ip, have NOT tried googles though.
I can NOT trace route past my router (linksys 802.11b, wired in to it).
I have set up evolution and it sees email to download but hangs on fetching 1 of #.
SMTP check completes successful , though i have not tried to actually send a mail yet.
When surfing to google, i can complete successful log in and searches with results.
When surfing to other pages from google or directly, FF hangs on waiting for domain. It acts like it has connected to site, but for what ever reason it never loads. I get NO error page.

It seems to me that I can send packets but not receive them, except when it comes to google.

I have downloaded the LAN driver for linux from ASUS website, after extracting tar i tried to ./configure, make, make install but i get an error saying missing config.h file or something to that effect. There is only a makefile in the source.

I have asked this very same question in Launchpad for Ubuntu and have been told its DNS issues(resulted in no fix as the namservers are correct) and have been called a troll for making up a nonexistent problem to claim Ubuntu does not work!

I really would like to get any distro working, preferably Ubuntu or Fedora but i am at a complete loss.

Thanks in advance for any help.

Head asplodes!

repo · 01-02-2009, 10:52 AM

Quote:

I can NOT trace route past my router (linksys 802.11b, wired in to it).

Is there a firewall in the router?

MasterC · 01-02-2009, 11:08 AM

Does this happen regardless of the Distro, or have you only tried Ubuntu? If you throw in a LiveCD and test it (using a different LiveCD than Ubuntu, maybe something Fedora based..) does it still produce the same results?

I thought DNS when I read that too. But it sure seems odd that the DNS server you are using would only resolve for google.com

I'm with repo, it sounds like an issue with your router. If you have other machines in the house not exhibiting the same problem, I'm still not inclined to say it's not the router. Try resetting it.

How do you get your IP? DHCP or static? If you use DHCP, does it set a nameserver of itself (something like 192.168.1.1) or does it set your ISP's nameservers (something like 98.202.114.16)? Can you post the contents of /etc/resolv.conf

-Chad

business_kid · 01-02-2009, 11:49 AM

Once you connect, some of these startup scripts rewrite the /etc/resolv.conf, and put it back afterwards. Have you checked it while you are online? dns seems down. To prove it to yourself, try these in 2 tabs

http://207.45.187.114 should bring you to
http://creek.securenet-server.net
If dns is down, you will find that the IP should work, and the url fail.

Obvious checks are in the modem. Often the dns server 192.168.1.1 is entered automagically. Check resolv.conf while "online". If things still don't add up, add opendns.org to the /etc/resolv.conf search line like this

search mydomain.com myisp.net opendns.org
nameserver 208.67.222.222
nameserver 208.67.220.220

and take out anything else in there. Restart firefox and try again.

3rods · 01-02-2009, 12:31 PM

The easiest way to narrow down the problem would be to plug the modem/adapter from Comcast right in to the PC. If it works, it's the router - if not, it's PC hardware or OS.

theNbomr · 01-02-2009, 12:58 PM

Since you say you can ping any IP (you didn't specify whether the IP was already resolved to numeric form, or used named IPs), then it seems like your DNS and routing are working.
Try running a network sniffer, such as wireshark or simply tcpdump, and capture all traffic while you attempt to make a failing connection (sniffer to run with root privileges). Look for numerous retries, damaged replies, even damaged sent packets. Look for unexpected high traffic levels, or unexpected traffic of any kind such as IPs that don't belong on your network.
Do you have a firewall set up? Any other boxes with firewalls set up?
What is the result of the following commands (all as root):

Code:

iptables -L
ifconfig
route

--- rod.

scottwest2 · 01-03-2009, 04:37 AM

3rods is correct. You need to diagnose the problem by narrowing down the hardware first.

hydrodev · 01-03-2009, 12:59 PM

This happens with all distros. Late last night I was told to check ifconfig and found there are alot of frame errors. A friend told me its 99.9% of the time a hardware issue. I have replaced the cable, still did not fix. I will try plugging directly into cable modem and see if it changes. Then i will try a pci NIC rather than the on board. I will keep this thread updated, so others will bennefit from what i find out.

Thank you all for your responses!

theNbomr · 01-03-2009, 04:38 PM

I would concur with your colleague. That is exactly where I was heading with my suggestion to look for retried packets. ping is a kind of go/no-go test, and may conceal channels that are partly broken. You may be able to do a better test of your NIC with ping, if your cable modem has a visible IP. Run arp and see if you can identify the cable modem in the resulting list. If yes, then

Code:

ping -f <ip_of_cable_modem>

Let it run for a few seconds, and see what it reports when you stop it. That may localize the fault somewhat. Also, if you have other hosts on your local network, do the same to/from them.
--- rod.