On Sun, May 20, 2007 at 10:52:12PM +0100, Pete wrote: > On Sunday 20 May 2007 19:56:47 H.S. wrote: > > Pete wrote: > > > DHCP. Laptop has its own IP address. No idea about name resolution. Not > > > certain how to check it > > > > What is the output of the following commands: > > > > $> ping 4.2.2.2 > > > > $> ping google.com > > > > $> ping <your router's IP address here> > > > > > > ->HS > > Curiouser and curiouser. > > My router is set up with the following (from my IP's instructions) > [EMAIL PROTECTED] > Password=######## > IP Address=82.138.204.44 > > If I ping 'phone.coop' I get > [EMAIL PROTECTED]:~$ ping -c5 phone.coop > PING phone.coop (1.0.0.0) 56(84) bytes of data. -------------------^^^^^^^^ this means you're not getting name resolution (the part where the name is turned into an IP address). > 5 packets transmitted, 0 received, +5 errors, 100% packet loss, time 4001ms > > If I ping the IP address I get: > > [EMAIL PROTECTED]:~$ ping -c5 82.138.204.44 > PING 82.138.204.44 (82.138.204.44) 56(84) bytes of data. > 64 bytes from 82.138.204.44: icmp_seq=1 ttl=255 time=3.02 ms > 64 bytes from 82.138.204.44: icmp_seq=2 ttl=255 time=0.688 ms > 64 bytes from 82.138.204.44: icmp_seq=3 ttl=255 time=0.676 ms > 64 bytes from 82.138.204.44: icmp_seq=4 ttl=255 time=0.681 ms > 64 bytes from 82.138.204.44: icmp_seq=5 ttl=255 time=0.672 ms
right... > > The result is exactly the same on this partition (Xubuntu, which is working) > and the other one (Debian, which isn't). Not certain what it proves other > than neither system recognises the name of the IP. > > Pinging google.com gives the expected result: > > [EMAIL PROTECTED]:~$ ping -c 5 google.com > PING google.com (64.233.167.99) 56(84) bytes of data. > 64 bytes from google.com (64.233.167.99): icmp_seq=1 ttl=241 time=151 ms > 64 bytes from google.com (64.233.167.99): icmp_seq=2 ttl=241 time=147 > ms................. I'm confused. Which boot, debian or Xubuntu gives the good results for ping google? > > Following Jeff D's advice > /etc/resolv.conf > > # generated by NetworkManager, do not edit! > > nameserver 192.168.1.1 > > The result is the same for both systems. Haven't tried laptop but it should > give 'nameserver 192.168.1.2' ummm... The contents of /etc/resolv.conf general comes from your dhcp server and it should be the address(es) of a nameserver and possible a search domain as well. If you are using the same dhcp server for both boots (your router, I assume) then you should be getting the same contents of /etc/resolv.conf. Please confirm what the contents of /etc/resolv.conf are for the ubuntu boot. I believe that network manager is probabnly complicating the picture and maybe you need just a basic dhcp client that properly handles resolv.conf, but that's just me. ONe thing you could do as a test is put in some known good name server addresses into resolv.conf and see if that fixes it up for you. Unless your router has a cacheing nameserver incorporated into it, it should be providing you with your ISP's nameservers and not its own address... A
signature.asc
Description: Digital signature
