[oclug] re: google

[chris h]

On Tuesday 29 March 2005 13:26, Adrian Irving-Beer wrote:
> On Tue, Mar 29, 2005 at 01:08:57PM -0500, chris h wrote:
> > # traceroute www.l.google.com
> > traceroute to www.l.google.com (64.233.161.104), 30 hops max, 40 byte
> > packets
>
> Have you
>
>   * tried just bringing up a web browser on it instead of traceroute,
>     or doing 'telnet <address> 80'?

simply hangs on both address blocks

>   * tried the -I switch to traceroute?

traceroute -I eth0 www.google.com
traceroute to www.google.com (64.233.161.104), 30 hops max, 40 byte packets
 1  192.168.1.1  0.531 ms   0.458 ms   0.556 ms
 2  * * *
 3  * * *
 4  * * *
 5  * * *


>   * tried one of the 64.233.167.* addresses instead?

tested them all via http and traceroute 

linux:/home/chrish123 # traceroute -I eth0 64.233.167.104
traceroute to 64.233.167.104 (64.233.167.104), 30 hops max, 40 byte packets
 1  192.168.1.1  0.587 ms   0.494 ms   0.544 ms
 2  * * *
 3  * * *
 4  * * *



>   * tried using a web browser on the 64.233.167.* addresses?

tested them all 

> Remember, traceroutes can be blocked by any firewall, or have routing
> issues of their own.  The best way to see if it's up is to actually try
> connecting to port 80, either via a web browser or simple telnet.

no go on both block sets 

Even tested by removing the router at this end and direct cable connection to 
laptop, same results. But I _really_ thank you for hanging in there and 
helping me sort this out. From talks with Rogers support they seem to think 
its a DNS issue on the particular subnet that Im on. Who knows at this point, 
but sure miss google...yahoo sucks but works for now..;)

/ch