Re: OFF-TOPIC: Check www.godaddy.com for me ...
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 50287
interpreted = N
texte = >> 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? > > No, it confirms only that the router at 63.241.142.14 is telling > your router that it doesn't have a route from 210.23.235.5 to > 63.241.136.95. Normally this would indicate that 63.241.142.14 > is misconfigured. But the fact that I had a problem tracerouting > to your first router suggests you should look to your own end > before you complain about their end. One reason I suggested that their end is the source of the problem is because I have tried and failed to visit the godaddy.com web site for nearly a week already -- via two completely different ISP's and three different computers. If I could have connected at any time during the past week or so, I would have concluded that the problem is on my end -- with the ISP that did not work properly. But because I failed to connect via both ISP's, I naturally concluded that the problem is on their end.Nevertheless, to further diagnose the problem, I disconnected my LAN router this evening, and I connected my computer directly to my DSL modem so I could use my traceroute utility over my DSL connection. Then I did a DSL traceroute to compare it with my original DIALUP traceroute results. Once again, here is the original traceroute results from my dialup service, followed by the new DSL traceroute results:DIALUP traceroute: 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 *DSL traceroute: Start: 5/13/03 12:11:38 AM Find route from: 202.57.86.42 to: godaddy.com (63.241.136.95), Max 30 hops, 40 byte packets Host Names truncated to 32 bytes 1 adsl-57.86.1.info.com.ph. (202.57.86.1 ): 68ms 34ms 22ms 2 202.57.126.117 (202.57.126.117 ): 21ms 27ms 22ms 3 210.14.3.5 (210.14.3.5 ): 21ms 45ms 22ms 4 210.14.0.33 (210.14.0.33 ): 22ms 21ms 23ms 5 210.14.0.6 (210.14.0.6 ): 223ms 198ms 212ms 6 teleglobe-gw.la2ca.ip.att.net. (192.205.32.221 ): 394ms 392ms * 7 tbr2-p012402.la2ca.ip.att.net. (12.122.11.221 ): 284ms 243ms 200ms 8 gbr2-p40.sd2ca.ip.att.net. (12.122.12.2 ): 200ms 326ms 200ms 9 gbr1-p60.sd2ca.ip.att.net. (12.122.1.109 ): 201ms 200ms 199ms 10 gbr2-p80.dtrmi.ip.att.net. (12.122.3.9 ): 229ms 229ms 230ms 11 gar2-p360.phmaz.ip.att.net. (12.123.142.45 ): 230ms 232ms 229ms 12 mdf1-gsr12-1-pos-2-0.phx1.attens (12.122.255.230 ): 263ms 252ms 254ms 13 mdf1-bi8k-1-eth-6-6.phx1.attens. (63.241.128.250 ): 234ms 324ms 236ms 14 mesaaz-m5-01-fe-0-0-0.secureserv (63.241.142.14 ): 252ms!U 252ms!U 303ms!U * Trace completed 5/13/03 12:11:53 AM *As you can see, both traceroutes fail at the same router -- 63.241.142.14 -- which seems to be located close to the godaddy.com web server. So it looks like 63.241.142.14 really is the problem router here. Thanks for your help!By the way, while I was writing this email, godaddy's tech support people emailed me again. This is the first email I received from them that actually acknowledges the problem I have been trying to tell them about for a week. It seems like they finally decided to sit up and take notice when I included the traceroute results in my most recent email to them:Thank you for contacting customer support. I have escalated this issue to one of our Leads for investigation. Please be patient while we work toward a resolution. When a resolution is achieved, you will be notified with the results. We appreciate your support in this matter.Hopefully they will get the problem fixed soon ... -- 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:
>> 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? > > No, it confirms only that the router at 63.241.142.14 is telling > your router that it doesn't have a route from 210.23.235.5 to > 63.241.136.95. Normally this would indicate that 63.241.142.14 > is misconfigured. But the fact that I had a problem tracerouting > to your first router suggests you should look to your own end > before you complain about their end. One reason I suggested that their end is the source of the problem is because I have tried and failed to visit the godaddy.com web site for nearly a week already -- via two completely different ISP's and three different computers. If I could have connected at any time during the past week or so, I would have concluded that the problem is on my end -- with the ISP that did not work properly. But because I failed to connect via both ISP's, I naturally concluded that the problem is on their end.Nevertheless, to further diagnose the problem, I disconnected my LAN router this evening, and I connected my computer directly to my DSL modem so I could use my traceroute utility over my DSL connection. Then I did a DSL traceroute to compare it with my original DIALUP traceroute results. Once again, here is the original traceroute results from my dialup service, followed by the new DSL traceroute results:DIALUP traceroute: 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 *DSL traceroute: Start: 5/13/03 12:11:38 AM Find route from: 202.57.86.42 to: godaddy.com (63.241.136.95), Max 30 hops, 40 byte packets Host Names truncated to 32 bytes 1 adsl-57.86.1.info.com.ph. (202.57.86.1 ): 68ms 34ms 22ms 2 202.57.126.117 (202.57.126.117 ): 21ms 27ms 22ms 3 210.14.3.5 (210.14.3.5 ): 21ms 45ms 22ms 4 210.14.0.33 (210.14.0.33 ): 22ms 21ms 23ms 5 210.14.0.6 (210.14.0.6 ): 223ms 198ms 212ms 6 teleglobe-gw.la2ca.ip.att.net. (192.205.32.221 ): 394ms 392ms * 7 tbr2-p012402.la2ca.ip.att.net. (12.122.11.221 ): 284ms 243ms 200ms 8 gbr2-p40.sd2ca.ip.att.net. (12.122.12.2 ): 200ms 326ms 200ms 9 gbr1-p60.sd2ca.ip.att.net. (12.122.1.109 ): 201ms 200ms 199ms 10 gbr2-p80.dtrmi.ip.att.net. (12.122.3.9 ): 229ms 229ms 230ms 11 gar2-p360.phmaz.ip.att.net. (12.123.142.45 ): 230ms 232ms 229ms 12 mdf1-gsr12-1-pos-2-0.phx1.attens (12.122.255.230 ): 263ms 252ms 254ms 13 mdf1-bi8k-1-eth-6-6.phx1.attens. (63.241.128.250 ): 234ms 324ms 236ms 14 mesaaz-m5-01-fe-0-0-0.secureserv (63.241.142.14 ): 252ms!U 252ms!U 303ms!U * Trace completed 5/13/03 12:11:53 AM *As you can see, both traceroutes fail at the same router -- 63.241.142.14 -- which seems to be located close to the godaddy.com web server. So it looks like 63.241.142.14 really is the problem router here. Thanks for your help!By the way, while I was writing this email, godaddy's tech support people emailed me again. This is the first email I received from them that actually acknowledges the problem I have been trying to tell them about for a week. It seems like they finally decided to sit up and take notice when I included the traceroute results in my most recent email to them:Thank you for contacting customer support. I have escalated this issue to one of our Leads for investigation. Please be patient while we work toward a resolution. When a resolution is achieved, you will be notified with the results. We appreciate your support in this matter.Hopefully they will get the problem fixed soon ... -- 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:
OK, here goes... (1997)
Stopping bad HTML propagation ? (1997)
WebCat2final1 crashes (1997)
WebCatalog f2 Installation (1997)
Time for a hard questions. (1997)
WebCat2b13 Mac plugin - [sendmail] and checkboxes (1997)
Shipcost lookup? (1997)
&max= (2003)
searching illegal HTML (2002)
Price characteristics? (1997)
Re:no [search] with NT (1997)
Emailer & IMail List Server (1998)
Resume Catalog ? (1997)
Need help with emailer- 2 issues (1997)
Database field limit? (1998)
webcat- multiple selection in input field (1997)
wild question (1998)
Summing fields (1997)
Snake Bites (1997)
Log entry (1999)