OK that came out terrible let me try
again.
Tracing route to ss1.keys.org
[64.200.212.203]
over a maximum of 30 hops:
1 <1
ms <1 ms <1 ms
192.168.123.254
2 5
ms 5 ms 6 ms
adsl-216-103-76-41.dsl.snfc21.pacbell.net [216.103.76.41]
3 6
ms 7 ms 5 ms
dist1-vlan60.snfc21.pbi.net [216.102.187.130]
4 6
ms 8 ms 5 ms
bb1-g1-3-0.snfc21.pbi.net [209.232.130.28]
5 5
ms 6 ms 5 ms
bb2-p3-0.snfcca.sbcglobal.net [151.164.190.186]
6 7
ms 7 ms 6 ms
bb1-p13-0.sntc01.pbi.net [64.161.124.241]
7 6
ms 8 ms 6 ms
bb2-p12-0.sntc01.pbi.net [64.161.1.26]
8 7
ms 7 ms 6 ms
64.161.1.22
9 7
ms 6 ms 6 ms
151.164.248.26
10 46
ms 48 ms 45 ms
sntcca1wcx2-pos1-0.wcg.net [64.200.240.125]
11 50
ms 46 ms 49 ms
dnvrco1wcx2-pos11-0.wcg.net [64.200.210.253]
12 46
ms 49 ms 49 ms
chcgil1wcx3-pos15-0.wcg.net [64.200.210.65]
13 48
ms 49 ms 48 ms
brvwil1wcx3-pos12-0-3-a60.wcg.net [64.200.236.34]
14 49
ms 48 ms 48 ms
stlsmo1wcxb-pos6-3.wcg.net [64.200.240.169]
15 48
ms 50 ms 46 ms
stlsmo1wcxa-pos6-2.wcg.net [64.200.246.69]
16 47
ms 48 ms 45 ms
kscymo1wce1-pos3-1.wcg.net [64.200.210.234]
17 50
ms 49 ms 48 ms
tpkaks1wcf1-atm.wcg.net [64.200.103.86]
18 53
ms 55 ms 57 ms keys1.nomb.com
[64.200.212.115]
Trace complete.
Adaryl "Did you reboot?" Wakefield
Aviator by
passion
Programmer by sheer force of will
----- Original Message -----
Sent: Thursday, January 08, 2004
12:46 PM
Subject: Fw: [KCFusion] DNS
issues OT
>you need to find some way of finding
out what ip 64.200.103.86 is routing traffic for 64.200.212.203
to
Now see this is an interesting comment.
Enclosed is a text file of a ping report for a guy out of San
Francisco. It seems after the williams router that the web server is
supposed to be the next stop. But as you can see on the report it does
not go to the web server it goes to the firewall (the .115
address). With out giving too much away the webserver is not
behind the fire wall. as a matter of fact they share a network
ID.
Adaryl "Did you reboot?" Wakefield
Aviator by
passion
Programmer by sheer force of will
----- Original Message -----
Sent: Thursday, January 08, 2004 11:51 AM
Subject: RE: [KCFusion] DNS issues OT
the trace
doesn't die at 64.200.103.86, it dies at the next hop, which doesn't
respond, which you don't get to see what ip/hostname it is using
tracert because it says "request timed out". again, this is beyond my
knowledge, but you need to find some way of finding out what ip
64.200.103.86 is routing traffic for 64.200.212.203 to. the guys at
willims communication should atleast be able to get you that info from
some routing table or something, but again, I wouldn't even know
offhand what to ask them to look in to get that information. the fact
that they can trace it from their place yet no one else can, including
me, would make me very suspicious that it's something going on at
their end and I'd probably be pretty serious with them, but I'm also
not sure what responsibilities they have to solve your problems. it
might be easier to talk to your isp directly, considering they're the
ones that actively get your check and have an account on file as to
who you are and make them go up the ladder from there. as for willims
communication not being able to pull up the website and it working
internally, that could be a ton of different things. the traffic could
possibly be never leaving your internal network, thereby bypassing
your company firewall, and allowing the traffic. the firewall may not
be correctly setup to route incoming traffic on port 80 for your
external public ip, the 64.200.212.203, to the internal network ip of
your webserver. I'd worry about getting the trace to work before I
worried about the website itself.
Bruce Dunwiddie
Ticket Technology
P: 866.543.3331
F:
913.451.7832
[EMAIL PROTECTED]
Im about at my wits end with this and
could use some senior help. This week just blows. Heres the
sitrep.
For some odd reason you can't bring up
www.keys.org. Ive ran though every
trick in the book and so has my ISP and we still can't fix this
issue.
If you try doing a tracert on www.keys.org or 64.200.212.203 the
trace dies at router 64.200.103.86 which belongs to willims
communcation so I got on the horn with them and they said they could
trace 203 but could not see the website. When i use www.visualroute.com to go to
some other servers it goes right to 203 and yet nobody around the
world that I have talked to says they can bring up the site. So at
this point I think there is something wrong with the webserver
right? wrong. If you are in the office you can pull up the web page.
After 2 days of troubleshooting im dead out of ideas.
P.S I even rebooted.
Adaryl "Did you reboot?"
Wakefield
Aviator by passion
Programmer by sheer force of
will
