[Nottingham] Network question - google unreachable?!
vanschoo at speakeasy.net
vanschoo at speakeasy.net
Sat Aug 4 20:38:39 BST 2007
Folks,
Just a quick update re this problem. The apartment complex's IT people have replaced their router, and now the urls resolve correctly. Not the most satisfying resolution, as I still don't know what the real problem & fix was.
I no longer have to put ip addresses into the browser to get to google. The problem was apparently connected with the router or maybe the way they had it configured. It's definitely the strangest internet connection issue I've encountered.
- njv
> -----Original Message-----
> From: vanschoo at speakeasy.net [mailto:vanschoo at speakeasy.net]
> Sent: Sunday, July 29, 2007 09:52 AM
> To: nottingham at mailman.lug.org.uk
> Subject: Re: [Nottingham] Network question - google unreachable?!
>
> Peter,
>
> Thanks for the suggestions! I tried keying in 64.233.183.104 with Firefox, and it reached google ok. So do the other 3 ip addresses you gave. It works with Safari also. Simultaneously, using the google urls still comes up with "server not found". That points to the ISP.
>
> Here are some commands I tried:
>
> :~ njv$ host www.google.co.uk
> ;; connection timed out; no servers could be reached
> :~ njv$
> :~ njv$ ping 64.233.183.104
> PING 64.233.183.104 (64.233.183.104): 56 data bytes
> 64 bytes from 64.233.183.104: icmp_seq=0 ttl=247 time=209.145 ms
> 64 bytes from 64.233.183.104: icmp_seq=1 ttl=247 time=218.604 ms
> 64 bytes from 64.233.183.104: icmp_seq=2 ttl=247 time=220.541 ms
> ^C
> --- 64.233.183.104 ping statistics ---
> 3 packets transmitted, 3 packets received, 0% packet loss
> round-trip min/avg/max/stddev = 209.145/216.097/220.541/4.979 ms
> :~ njv$
> :~ njv$ traceroute www.google.co.uk
> traceroute: unknown host www.google.co.uk
> :~ njv$ host www.google.com
> www.google.com has address 216.239.59.99
> ;; connection timed out; no servers could be reached
> ;; connection timed out; no servers could be reached
> :~ njv$
>
>
> It seems clear that there is a problem in the ISP's network. I will follow up with the apartment folks. I'm curious though as to how this can happen. I can believe their DNS lookup has a problem, but with such a popular site as google, that's very strange.
>
> - njv
>
>
> > -----Original Message-----
> > From: Peter Chang [mailto:Peter.Chang at nottingham.ac.uk]
> > Sent: Saturday, July 28, 2007 05:12 PM
> > To: nottingham at mailman.lug.org.uk
> > Subject: Re: [Nottingham] Network question - google unreachable?!
> >
> >
> > On Sat, 28 Jul 2007, vanschoo at speakeasy.net wrote:
> > [can't get google]
> >
> > Your problem sounds very strange indeed. How are you connecting to the
> > internet?
> >
> > I think you should check that your dns is working:
> >
> > $ host www.google.co.uk
> >
> > gives me
> >
> > www.google.co.uk is an alias for www.google.com.
> > www.google.com is an alias for www.l.google.com.
> > www.l.google.com has address 64.233.183.104
> > www.l.google.com has address 64.233.183.99
> > www.l.google.com has address 64.233.183.103
> > www.l.google.com has address 64.233.183.147
> >
> >
> > then
> > $ traceroute www.google.co.uk
> > 1 192.168.0.1 (192.168.0.1) 1.508 ms 1.362 ms 1.325 ms
> > 2 x.x.x.x (x.x.x.x) 13.159 ms 13.128 ms 21.078 ms
> > 3 x.x.x.x (x.x.x.x) 21.044 ms 20.948 ms 24.864 ms
> > 4 x.inet.ntl.com (x.x.x.x) 24.829 ms 29.776 ms 29.740 ms
> > 5 nth-bb-b-so-020-0.inet.ntl.com (213.105.174.173) 38.679 ms 41.628 ms
> > 41.597 ms
> > 6 tele-ic-1-as0-0.inet.ntl.com (62.253.184.2) 49.538 ms 10.872 ms
> > 20.802 ms
> > 7 212.250.14.66 (212.250.14.66) 20.769 ms 15.913 ms 15.863 ms
> > 8 72.14.238.244 (72.14.238.244) 24.804 ms 24.771 ms 24.732 ms
> > 9 209.85.248.80 (209.85.248.80) 36.687 ms 72.14.233.63 (72.14.233.63)
> > 44.621 ms 45.582 ms
> > 10 64.233.175.246 (64.233.175.246) 83.508 ms 209.85.248.79
> > (209.85.248.79) 68.446 ms 64.233.175.246 (64.233.175.246) 38.888 ms
> > 11 * 72.14.233.79 (72.14.233.79) 57.788 ms 72.14.233.77 (72.14.233.77)
> > 57.757 ms
> > 12 209.85.249.129 (209.85.249.129) 67.676 ms * 216.239.43.30
> > (216.239.43.30) 30.944 ms
> > 13 nf-in-f99.google.com (64.233.183.99) 30.866 ms 37.809 ms 38.767 ms
> >
> > [where I've elided some IP addresses and hostnames]
> >
> > Does firefox work when you use the IP address above?
> > Does safari work?
> >
> > hth,
> > Peter
> >
> >
> > This message has been checked for viruses but the contents of an attachment
> > may still contain software viruses, which could damage your computer system:
> > you are advised to perform your own checks. Email communications with the
> > University of Nottingham may be monitored as permitted by UK legislation.
> >
> >
> > _______________________________________________
> > Nottingham mailing list
> > Nottingham at mailman.lug.org.uk
> > https://mailman.lug.org.uk/mailman/listinfo/nottingham
> >
>
>
>
> _______________________________________________
> Nottingham mailing list
> Nottingham at mailman.lug.org.uk
> https://mailman.lug.org.uk/mailman/listinfo/nottingham
>
More information about the Nottingham
mailing list