Re: OFF-TOPIC: Check www.godaddy.com for me ...
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 50271
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? By the way, since the server at 210.23.235.5 is the first server in the list, it seems like this is probably the server that assigned me the dynamic ip address 210.23.213.143 when I logged into my dialup service so I could perform my traceroute tests.But because I virtually never use this dialup service, I doubt that this server is the cause of the problem ...I usually use a DSL connection on a different service, which of course means that the server at 210.23.235.5 would not appear in the traceroute if done from my DSL service. But because my DSL connection goes thru my LAN router, and because my traceroute utility does not work on this side of my router, the easiest way for me to perform a traceroute test was to use a temporary dialup connection in order to bypass the router and get a direct connection to the net.So, if 210.23.235.5 exists *only* in the traceroute path of my temporary dialup service but not in the path of my DSL service -- yet the problem exists on my DSL service as well as on a completely separate dialup service -- then it seems like 210.23.235.5 is not the problem.Does this make sense or not?For reference, this is the traceroute data again:Start: 5/12/03 4:43:25 PM Find route from: 210.23.213.143 to: godaddy.com (63.241.136.95), Max 30 hops, 40 byte packets Host Names truncated to 32 bytes 1 210.23.235.5 (210.23.235.5 ): 119ms 162ms 143ms 2 210.23.235.4 (210.23.235.4 ): 164ms 144ms 170ms 3 if-5-1-0.msfc1.quezon.teleglobe. (64.86.127.17 ): 145ms 144ms 130ms 4 if-1-1.core2.losangeles.teleglob (64.86.82.157 ): 319ms 310ms 329ms 5 if-5-0.core1.losangeles.teleglob (207.45.223.62 ): 351ms 336ms 325ms 6 teleglobe-gw.la2ca.ip.att.net. (192.205.32.221 ): 301ms 309ms 296ms 7 gbr4-p50.la2ca.ip.att.net. (12.123.28.134 ): 312ms 313ms 326ms 8 gbr2-p20.sd2ca.ip.att.net. (12.122.11.254 ): 304ms 332ms 330ms 9 gbr1-p60.sd2ca.ip.att.net. (12.122.1.109 ): 338ms 350ms 383ms 10 gbr1-p20.phmaz.ip.att.net. (12.122.2.5 ): 394ms 447ms 447ms 11 gar2-p360.phmaz.ip.att.net. (12.123.142.45 ): 477ms 463ms 459ms 12 mdf1-gsr12-1-pos-2-0.phx1.attens (12.122.255.230 ): 430ms 400ms 405ms 13 mdf1-bi8k-1-eth-6-6.phx1.attens. (63.241.128.250 ): 433ms 410ms 473ms 14 mesaaz-m5-01-fe-0-0-0.secureserv (63.241.142.14 ): 345ms!U 406ms!U 368ms!U * Trace completed 5/12/03 4:43:41 PM * -- 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? By the way, since the server at 210.23.235.5 is the first server in the list, it seems like this is probably the server that assigned me the dynamic ip address 210.23.213.143 when I logged into my dialup service so I could perform my traceroute tests.But because I virtually never use this dialup service, I doubt that this server is the cause of the problem ...I usually use a DSL connection on a different service, which of course means that the server at 210.23.235.5 would not appear in the traceroute if done from my DSL service. But because my DSL connection goes thru my LAN router, and because my traceroute utility does not work on this side of my router, the easiest way for me to perform a traceroute test was to use a temporary dialup connection in order to bypass the router and get a direct connection to the net.So, if 210.23.235.5 exists *only* in the traceroute path of my temporary dialup service but not in the path of my DSL service -- yet the problem exists on my DSL service as well as on a completely separate dialup service -- then it seems like 210.23.235.5 is not the problem.Does this make sense or not?For reference, this is the traceroute data again:Start: 5/12/03 4:43:25 PM Find route from: 210.23.213.143 to: godaddy.com (63.241.136.95), Max 30 hops, 40 byte packets Host Names truncated to 32 bytes 1 210.23.235.5 (210.23.235.5 ): 119ms 162ms 143ms 2 210.23.235.4 (210.23.235.4 ): 164ms 144ms 170ms 3 if-5-1-0.msfc1.quezon.teleglobe. (64.86.127.17 ): 145ms 144ms 130ms 4 if-1-1.core2.losangeles.teleglob (64.86.82.157 ): 319ms 310ms 329ms 5 if-5-0.core1.losangeles.teleglob (207.45.223.62 ): 351ms 336ms 325ms 6 teleglobe-gw.la2ca.ip.att.net. (192.205.32.221 ): 301ms 309ms 296ms 7 gbr4-p50.la2ca.ip.att.net. (12.123.28.134 ): 312ms 313ms 326ms 8 gbr2-p20.sd2ca.ip.att.net. (12.122.11.254 ): 304ms 332ms 330ms 9 gbr1-p60.sd2ca.ip.att.net. (12.122.1.109 ): 338ms 350ms 383ms 10 gbr1-p20.phmaz.ip.att.net. (12.122.2.5 ): 394ms 447ms 447ms 11 gar2-p360.phmaz.ip.att.net. (12.123.142.45 ): 477ms 463ms 459ms 12 mdf1-gsr12-1-pos-2-0.phx1.attens (12.122.255.230 ): 430ms 400ms 405ms 13 mdf1-bi8k-1-eth-6-6.phx1.attens. (63.241.128.250 ): 433ms 410ms 473ms 14 mesaaz-m5-01-fe-0-0-0.secureserv (63.241.142.14 ): 345ms!U 406ms!U 368ms!U * Trace completed 5/12/03 4:43:41 PM * -- 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:
Postprocessing CCs (2000)
why do I get authorization requests, even though (1999)
Problem with a search context (2005)
Help! WebCat2 bug (1997)
New Webcatalog for Mac (1997)
[WebDNA] Press Release (2008)
Getting total number of items ordered (1997)
SSL and reg web* (1997)
WC2.0 Memory Requirements (1997)
Fwd: Problems with Webcatalog Plug-in (1997)
Problem (1997)
CloseDatabase (1997)
Appending problem (still) on Solaris (2000)
searching by part of the date information (1999)
Post size Limit? (1998)
UPDATE PROBLEM (1997)
Webcat no longer supported? (2006)
Mac Os X and WebCat (1999)
Wanted: Broader string manipulation functions (1997)
Running 2 two WebCatalog.acgi's (1996)