Re: OFF-TOPIC: Check www.godaddy.com for me ...
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 50264
interpreted = N
texte = >Kenneth Grome wrote: >>I did a traceroute and got this result. Does this mean the server >>at ip address 63.241.142.14 is the cause of my failed attempts to >>connect to godaddy.com?: > >Yes that is exactly what it means. > >>410ms 473ms 14 mesaaz-m5-01-fe-0-0-0.secureserv >>(63.241.142.14 ): 345ms!U 406ms!U 368ms!U > >The notation !U is like what I have seen before as NO ROUTE TO >HOST which of course could mean equally that you have no route to >that host or that that host has no route to you. I am unable to >complete a traceroute to 210.23.235.5 so it is more likely than not >it is your network that is at fault. Okay, now I am confused. First you seem to be confirming my conclusion that 63.241.142.14 is the cause of the problem, but then you said it is more likely than not it is your network that is at fault because you could not complete a traceroute to 210.23.235.5.My traceroute utility gets past 210.23.235.5 every time -- and every time, my tests made it all the way to 63.241.142.14 before failing. Wouldn't this reconfirm that it is not a problem at 210.23.235.5 but actually the problem is at 63.241.142.14? -- Sincerely, Kenneth Grome ------------------------------------------------------------- My programmers will write WebDNA code for you at $27 an hour! -------------------------------------------------------------------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
>Kenneth Grome wrote: >>I did a traceroute and got this result. Does this mean the server >>at ip address 63.241.142.14 is the cause of my failed attempts to >>connect to godaddy.com?: > >Yes that is exactly what it means. > >>410ms 473ms 14 mesaaz-m5-01-fe-0-0-0.secureserv >>(63.241.142.14 ): 345ms!U 406ms!U 368ms!U > >The notation !U is like what I have seen before as NO ROUTE TO >HOST which of course could mean equally that you have no route to >that host or that that host has no route to you. I am unable to >complete a traceroute to 210.23.235.5 so it is more likely than not >it is your network that is at fault. Okay, now I am confused. First you seem to be confirming my conclusion that 63.241.142.14 is the cause of the problem, but then you said it is more likely than not it is your network that is at fault because you could not complete a traceroute to 210.23.235.5.My traceroute utility gets past 210.23.235.5 every time -- and every time, my tests made it all the way to 63.241.142.14 before failing. Wouldn't this reconfirm that it is not a problem at 210.23.235.5 but actually the problem is at 63.241.142.14? -- Sincerely, Kenneth Grome ------------------------------------------------------------- My programmers will write WebDNA code for you at $27 an hour! -------------------------------------------------------------------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Kenneth Grome
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
WebCat2 several catalogs? (1997)
WebCatalog can't find database (1997)
Date problems-more (1997)
WebCatalog for guestbook ? (1997)
Understanding texta (1997)
maximum characters in [username]? (2002)
Help! (2000)
Customer (1998)
Re1000001: Setting up shop (1997)
WebCat2: multiple currency support (1997)
Attention SMSI - DOCS Error (2004)
WebCat and WebTV (1997)
PIXO support (1997)
WebCat2 - Getting to the browser's username/password data (1997)
WCS Newbie question (1997)
Exclude by date - multiple (1997)
shownext not showing next...still r2 (1997)
X Server (1999)
database paths/names, and a typo (1997)
getchars broken? (1997)