RE: [KCFusion] DNS issues OT

[Bruce Dunwiddie]

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] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Adaryl Wakefield Sent: Thursday, January 08, 2004 11:39 AM To: [EMAIL PROTECTED] Subject: [KCFusion] DNS issues OT 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