[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [at-l] geocities access

Just a bit more info on what Tom wrote.

To check out if there is a connection to geocities and your site, there are 
a couple of operating systems commands you can use.

1) From a DOS window enter the command - ping www.geocities.com   - you 
should get a response like the one below.

Pinging www.geocities.com [209.1.224.12] with 32 bytes of data:

Reply from 204.119.2.30: bytes=32 time=XXXXms TTL=63
Reply from 204.119.2.30: bytes=32 time=XXXXms TTL=63
Reply from 204.119.2.30: bytes=32 time=XXXXms TTL=63
Reply from 204.119.2.30: bytes=32 time=XXXXms TTL=63

The XXXX is the amount of time in milliseconds for a packet to travel from 
your system to geocities and back.

If the link is not up you'll probably get a response like

Pinging www.geocities.com [209.1.224.12] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

If you get back a bad IP statement below, then the DNS is not working. 
Don't worry about what it means. Generally DNS tables short life span so if 
a major route changes on the net a new one will take it's place. I usually 
takes about 24 hours to propagate new routes across the net.

Bad IP address www.geocities.com

2) If ping works and you still can't get through. Try the command tracert. 
Below is tracert run from my machine. You'll notice that there are 12 
computers between mine and geocities. Yours will vary. If there are too 
many computer in the route (generally 30) most routers will drop the packet 
and you'll get nothing back. Routes can be funny. I once had a route 
between me and a company downtown (5 miles away) that went from me to 
downtown Portland to San Francisco, to Seattle, back to Portland.

c:\users\ronm>tracert www.geocities.com

Tracing route to www.geocities.com [209.1.224.11]
over a maximum of 30 hops:

  1   <10 ms   <10 ms   <10 ms  204.119.2.85
  2  2243 ms  2113 ms  2184 ms  BDSRTR [204.119.2.28]
  3  1963 ms  1863 ms  2013 ms  204.119.2.29
  4  1943 ms  2063 ms  2213 ms  i0.pdx.RAIN.NET [206.163.10.37]
  5  2163 ms  1673 ms  2173 ms  f12-0.r0.pdx.RAIN.NET [199.2.96.33]
  6  2273 ms  1903 ms     *     f0.pdx0.verio.NET [199.2.96.34]
  7  2073 ms  2203 ms  2523 ms  pdx0-3.paix-3.verio.NET [205.238.56.50]
  8  1963 ms  2063 ms  2313 ms  paix.paix1.verio.NET [205.238.56.90]
  9  2113 ms  2113 ms  2463 ms  paix.exodus.NET [198.32.176.15]
 10  2013 ms  2023 ms  2063 ms  scca-01-h0-0-0.core.exodus.NET 
[209.1.169.229]
 11  2414 ms  2013 ms  2473 ms  209.1.218.10
 12  2103 ms  2053 ms  1923 ms  res2.GEOCITIES.com [209.1.224.11]

Trace complete.

There are a few other commands, but then I wouldn't want to turn you into a 
hacker.

Also case sensitivity depends upon the OS that's hosting the WEB. NT hosts 
aren't case sensitive while Unix host are. If in doubt make it exact.

Ron.



* From the Appalachian Trail Mailing List | For info http://www.hack.net/lists *

==============================================================================