I can only browse to google.com

[beaker_]

Being able to ping www.xwz.com suggests your name servers are ok but for giggles try pinging both or reversing thier order. I'm thinking a firewall or proxy is blocking your request but it just doesn't fit.

ping 192.168.2.1 <<----- This is your router I assume.
ping 68.87.72.134

If you're using kde, how does konqueror work? Likely the same way.


Hahaha, think I found it:

In firefox's address bar, type "about: config"
Look for or type 'network.dns.disableIPv6' in the filter.
Double click on 'network.dns.disableIPv6' to change it's value from false to true.


Am I lucky?

[timktaylor]

Tried it. Didn't help.

That was new for me. I didn't know about that. Thanks so much for your tenacity.

Yes,

192.168.2.1 is my router

I am using GNOME.

I find that I can hit most *.edu that I try.

Still weird.

[beaker_]

I'm thinking two routes; either you're behind a proxy (some nanny thing), or resolv order. Either way it's outside of my knowledge, at least off the top of my head.

Double check your router, maybe it's been locked down or a filter (by mac address?) is enabled, some content blocking?


I don't know but how about nsswitch.conf? At the terminal:

cat /etc/nsswitch

does the hosts entry look like this?

hosts: files dns


You could rule out your linux box by downloading a live disk. Don't install it, just see if it'll boot, connect and browse. If not, then you likely ruled out that box and it's time to focus on that router.

[MikeV]

I'd blow out those DNS servers and try 4.2.2.1, which responds to queries from anyone, and see if you get the same response...

Do other PCs on your network have this issue? If you have a windows box, do an "ipconfig /all" to see what IPs they're using for DNS, and match those on Linux.

If you drop the 192.168.2.1 from your DNS servers, you'll rule out any odd querying problems from your router.

Also, setting it to 4.2.2.1 should do the same thing: bypass the dns forwarder on the router.

It sounds like it's resolving some stuff but not all. It's purely a DNS issue from the sounds of it, because you can go to the IPs ok.

[timktaylor]

Here is more info:

• Setting 4.2.2.1 as only nameserver does not help. Same behavior.
• I can surf to certain IP's only; just as I can surf to certain sites only (ibm.com, google.com, mit.edu, vanderbilt.edu, etc)
• I can go to http://209.132.177.50/ solidly but not to http://redhat.com or http://www.redhat.com
• No other PC on my network has this issue. There are 2 Win2k, and three WinXP also local
• I have downloaded and booted with the LiveCD and tried to surf with it; same problem exists on the system I am experiencing the problem (Fedora Core 11 new install).
• I booted the LiveCD on one of my Win2K machines and surfing works!

Now this says to me perhaps my NIC? What flaky? I can run wire shark and the spotty site access mentioned above; I don't think so.

Theories?

[nigerag]

Try to find the DNS ip adresses for your ISP and manually add them to /etc/resolve.conf

Take a look at http://www.cyberciti.biz/tips/linux-...ns-client.html

[beaker_]

I wonder if it's a driver related issue

lspci |grep Ethernet
lspci |grep Network

These will kick back your nic & wireless, unless they're usb but then substitute lsusb for lspci, and lsmod will kick back your loaded modules. Try a google search for your nic & or module, maybe there are know issues. Also swap your ethernet cables just for giggles anyway.

Come to think of it, I don't recall you mentioning whether you connect via ethernet or wireless. If you convince yourself that it's related to your nic then be careful when purchasing a replacement. If you're like me, you'll grab the $13 special only to realise it supports up to a 100MHz bus.

[timktaylor]

I am using wired connection but I do have a wireless adapter installed and inactive.

I have swapped ethernet cables already, to no avail, as well as, swapped ports on the hub that serves my basement wired systems. I also triied bypassing the hub.

You gave me the right advice that time. I have a SiS 191 NIC and this vents about the same futile efforts.

There was no solution found so I may need to get another NIC. I will look further but this came up fairly quickly in my search.

regards,
tt

[brunson]

I have only skimmed the thread, but I haven't seen anyone recommend removing the router from them mix. Can you temporarily plug your WAN connection directly into your linux box? You'll have to make sure you re-acquire DHCP settings, though NetworkManager my take care of that for you. The act of unplugging and replugging the ethernet should cause NM to DHCP directly from your ISP. If that works, suspect your router, if not then you've only lost a minute or two.

[pdowns]

Was helping my son set up a new PC and put Fedora 11 on it. It came with Firefox 3.5 Beta 4. It is obviously customized to have Fedora home pages, etc. I can get to those!

I would describe my symptoms as being able to go to some websites, but for most I get "server not found." But from a terminal window I can ping and resolve any DNS name I want.

One other thing I'd note is that this PC has two ethernet adapters on the motherboard. I won't get back to my son's house for a couple days so I hope you all fix this before then! TIA

I'm going to look in resolv.conf for clues, as well as install ethereal. That will prove to me the problem is inside the box.

This is really weird.

[timktaylor]

Brunson,

I verified that taking my router (and therefore all other systems in my home LAN) out of the equation does not change the behavior one bit.

I am researching any known incompatibility between Linux and an Integrated SiS191 ethernet adapter...

regards,
tt

[MikeV]

Your router shouldn't be an issue, because your other PCs work just fine.

I've never heard of a NIC that will pass most traffic, but not DNS requests. I consider that a very remote possibility.

can you post here the full contents of /etc/resolv.conf ?

What DNS is your Windows box using?

[timktaylor]

The Windows boxes use the same DNS I have configured (by Network Manager) on Fedora.

Actually, they only use the primary. I have both DNS's provided by my ISP in /etc/resolv.conf: 68.87.72.134, 68.87.77.134.

A colleague told me about Wireshark. I installed it and started looking at the packet traffic.

For the sites that work like a charm: e.g. ibm.com, mit.edu, vanderbilt.ed, there is an exchange of DNS queries and responses that cover perhaps over a dozen packets for the initial page load. For sites that don't work, there are like two packets: e.g. query www.redhat.com, response www.redhat.com.edgesuite.net.

Also, for sites that DO NOT WORK, I do see the TCP handshake SYN, SYN-ACK, ACK, however the HTTP traffic doesn't seem to show 200 OK responses to my begging (hanging) client.

Anyone have any ideas on how I can use this power tool to find out more?

It is like some sites can't adequately find there way back to me.

regards,
tt

[beaker_]

I know, you just want something fixed but for giggles;

At the term,

telnet www.google.com 80 (sorry, windows here)
get /

I'm curious if it throws back a webpage.

Also try running apache or iis on one of those windows pc's, place an entry into hosts and see if you can navigate your way to that pc. i.e., myWinBox

Basically I'm snooping around, wondering if maybe running dns-masq on your machine would band-aid it.


Edit: Also try to telneting to a url who doesn't work. Oops, baid-aid likely not to work. Sorry I missed your post. Also, any reason why we don't try your wireless card? What type is it?

[beaker_]

Sorry for the double post but have you tried this?

http://ubuntuforums.org/showthread.p...09#post2545109