intranet works, internet doesn't
Weird problem, but it happens.
interfaces file = Code:
#This file describes the network interfaces available on your system Any reason why this wouldn't be working? I do have 3 NIC's (Onboard = eth0, ethernet NIC and wireless NIC are both installed in the pc but not set up yet) |
Is that network correct ? ... I would have thought it should be 192.168.1.0 ..
cheers |
I'm not entirely sure what "network" is supposed to be.. I was just googling possible configs and one seemed to have it in there so I threw it in mine.
I did however just change it currently reads: Code:
# The primary network interface Also, seems to be just a DNS issue. ping 4.2.2.2 works, but ping google.com does not. Which would explain why intranet works, and internet does not. I know the dns server I had specified works, as I've used the same ones for a good 5 years now (even on this box..) |
Can you perform a 'netstat -nr' and post the output ? .. that will show us the routing table
Is the dns server yours or an ISP one ? cheers |
Code:
Kernel IP routing table |
Looks good.. can you query any other dns servers ?
|
ServU:~# ping google.com
ping: unknown host google.com ServU:~# ping linuxquestions.org ping: unknown host linuxquestions.org ServU:~# ping yahoo.com ping: unknown host yahoo.com ServU:~# ping fox.com ping: unknown host fox.com :( Just noticed as I was rebooting the pc, the winbind daemon is failing to start. Quick google search shows it's used for resolving names from NT servers.. Would this have any affect on the DNS? |
Is there another dns server you can query other than 4.2.2.2 ?
eg. 'dig @anotherdnsserver www.google.com' |
ping 4.2.2.4 google.com
ping: unknown host google.com |
I don't think thats a valid command mate... try 'dig @4.2.2.3 www.google.com'
|
oh snap
Code:
dig @4.2.2.3 www.google.com But either way, even with this new development, I still cannot route to websites.. |
That server seems to be working so change your network config accordingly then retest net access
|
Used "dns-nameserver 4.2.2.1 4.2.2.2 4.2.2.3 4.2.2.4" for good measure
Then "/etc/init.d/networking restart" Samething, still can't route :( |
Try testing them individually with dig as before and remove any that don't respond from your network config. After that, if you can successfully perform name resolution at the command line try this:
'wget http://www.google.com/' |
Tried them all, they all work.
Code:
ServU:~# wget http://www.google.com/ |
All times are GMT -5. The time now is 07:34 PM. |