Resolving Issues

[Jator]

I can't seem to ping www.teamanandtech.com and a few other popular sites, but others I can. I can find the IP addresses, but nothing comes back. Thus I am sitting on about 22,000 RC5 blocks in my pproxy. Hopefully it will resolve itself before the end of the day, otherwise I'll flush through one of the other baby bovines.

Jay

 

[TwoFace]

You're sure it's just not a firewall thing that stops your ping Jay?

Not that teamanandtech.com has had that before... but maybe it has one now...

Just a thought... hope you get it to work, and thanks for the heads up

With love and respect your fellow TA member

Two-Face

 

[JonB]

Sounds like it may be time to put the IP address into the HOSTS file. Then it won't need the stinking DNS lookup.

 

[Jarhead]

Works here...

Microsoft(R) Windows 98
(C)Copyright Microsoft Corp 1981-1998.

C:\WINDOWS\Desktop>ping www.teamanandtech.com

Pinging edge.teamanandtech.com [204.209.128.158] with 32 bytes of data:

Reply from 204.209.128.158: bytes=32 time=234ms TTL=108
Reply from 204.209.128.158: bytes=32 time=219ms TTL=108
Reply from 204.209.128.158: bytes=32 time=223ms TTL=108
Reply from 204.209.128.158: bytes=32 time=222ms TTL=108

Ping statistics for 204.209.128.158:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 219ms, Maximum = 234ms, Average = 224ms

C:\WINDOWS\Desktop>

 

[DanC]

I'd just plug in the IP Jay.

 

[Jator]

C:\>ping www.teamanandtech.com

Pinging edge.teamanandtech.com [204.209.128.158] with 32 bytes of data:

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

Ping statistics for 204.209.128.158:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

It's not a DNS server, as I implied in my thread title, I can't physically ping www.teamanandtech.com (notice the IP is resolved). I'm thinking there is a problem with one of the routers between TA.com and myself.

Jay

BTW, I can't open the web page either.

 

[Jator]

Tracing route to edge.teamanandtech.com [204.209.128.158]
over a maximum of 30 hops:

1 <10 ms <10 ms <10 ms 192.168.0.254
2 <10 ms <10 ms <10 ms dsl-216-227-69-110.telocity.com [216.227.69.110]

3 10 ms 20 ms 10 ms route-216-227-65-1.telocity.com [216.227.65.1]
4 10 ms 10 ms 20 ms fe1-1-core1.orl.tlct.net [216.227.64.65]
5 30 ms 30 ms 30 ms 216.227.126.37
6 30 ms 30 ms 40 ms fe2-11-hfr1.atl.tlct.net [216.227.126.129]
7 70 ms 80 ms 81 ms pos8-1-hfr2.dfw.tlct.net [216.227.126.22]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

 

[SpaceWalker]

Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-1999.

C:\>ping www.teamanandtech.com

Pinging edge.teamanandtech.com [204.209.128.158] with 32 bytes of data:

Reply from 204.209.128.158: bytes=32 time=351ms TTL=114
Reply from 204.209.128.158: bytes=32 time=210ms TTL=114
Reply from 204.209.128.158: bytes=32 time=231ms TTL=114
Reply from 204.209.128.158: bytes=32 time=230ms TTL=114

Ping statistics for 204.209.128.158:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 210ms, Maximum = 351ms, Average = 255ms

C:\>

Pings fine from down here J.

It's got to be a problem with Telocity....

MOOOOOOOOOOOOOOOOOOOooooooooooooooooooo.....................

 

[Jator]

SW, of that, I have no doubt!!!!

 

[DanC]

How about another mini-bovine Jay?

 

[ViRGE]

Humm, that's really, really odd Jay. Check again tomorrow morning, and tell us what you get. This may indicate a bigger problem for either you, or us.:Q

 

[Jator]

Sorry, I didn't mention it resloved itself about 2 hours later. Must of been a router problem at Telocity. I'm suprised they fixed it. :Q

 

[Jarhead]

FYI,

I tried pinging one of the IPs near you 192.168.0.254, and 25% of time, the pings time out. I don't have that problem pinging anywhere else.

 

[Jator]

JarHead,

That's my router. The 192.168.0.254 is not visible to the outside internet. On the internet side, the IP address is 216.227.69.109

Jay