Reply to thread

Message

<blockquote data-quote="nickt" data-source="post: 259661" data-attributes="member: 4923">If you have windows you might want to play with the tracert command. (there is a mac equivalent, but not familiar) I don't know enough to help you troubleshoot, but it might be interesting for you. You open a command prompt window, it should be under Accessories. Type tracert nikonites,com in the command window (I used a comma so it didn't turn into a forum link, use a period). It will return to you the path your request took.&nbsp; I can't help you with the results, way over my head, but the path will not always be the same. Some of the points will be your isp's equipment, some are various carrier connections and you should end at the server hosting nikonites. Here is my result:Tracing route to nikonites.com [174.132.134.35]over a maximum of 30 hops:&nbsp; 1&nbsp; &nbsp;&nbsp; 3 ms&nbsp; &nbsp;&nbsp; 4 ms&nbsp; &nbsp;&nbsp; 3 ms&nbsp; Wireless_Broadband_Router.home [192.168.1.1] &nbsp; 2&nbsp; &nbsp; 10 ms&nbsp; &nbsp;&nbsp; 7 ms&nbsp; &nbsp;&nbsp; 7 ms&nbsp; L100.PGHKNY-VFTTP-08.verizon-gni.net [96.248.38.1] &nbsp; 3&nbsp; &nbsp;&nbsp; 6 ms&nbsp; &nbsp;&nbsp; 7 ms&nbsp; &nbsp;&nbsp; 8 ms&nbsp; G9-3-108.PGHKNY-LCR-01.verizon-gni.net [130.81.131.90] &nbsp; 4&nbsp; &nbsp; 38 ms&nbsp; &nbsp; 23 ms&nbsp; &nbsp; 22 ms&nbsp; 130.81.199.0 &nbsp; 5&nbsp; &nbsp; 17 ms&nbsp; &nbsp; 17 ms&nbsp; &nbsp; 19 ms&nbsp; 0.xe-11-3-0.BR2.NYC4.ALTER.NET [152.63.23.137] &nbsp; 6&nbsp; &nbsp; 17 ms&nbsp; &nbsp; 18 ms&nbsp; &nbsp; 15 ms&nbsp; 204.255.173.54 &nbsp; 7&nbsp; &nbsp; 25 ms&nbsp; &nbsp; 27 ms&nbsp; &nbsp; 25 ms&nbsp; vlan51.ebr1.NewYork2.Level3.net [4.69.138.222] &nbsp; 8&nbsp; &nbsp; 19 ms&nbsp; &nbsp; 17 ms&nbsp; &nbsp; 17 ms&nbsp; ae-47-47.ebr1.NewYork1.Level3.net [4.69.201.45] &nbsp; 9&nbsp; &nbsp; 25 ms&nbsp; &nbsp; 27 ms&nbsp; &nbsp; 26 ms&nbsp; ae-81-81.csw3.NewYork1.Level3.net [4.69.134.74] &nbsp;10&nbsp; &nbsp; 24 ms&nbsp; &nbsp; 26 ms&nbsp; &nbsp; 25 ms&nbsp; ae-3-80.edge3.NewYork1.Level3.net [4.69.155.145] &nbsp;11&nbsp; &nbsp; 24 ms&nbsp; &nbsp; 22 ms&nbsp; &nbsp; 23 ms&nbsp; te2-5.bbr01.tl01.nyc01.networklayer.com [4.26.34.22] &nbsp;12&nbsp; &nbsp; 44 ms&nbsp; &nbsp; 44 ms&nbsp; &nbsp; 44 ms&nbsp; ae1.bbr01.eq01.chi01.networklayer.com [173.192.18.132] &nbsp;13&nbsp; &nbsp; 62 ms&nbsp; &nbsp; 63 ms&nbsp; &nbsp; 61 ms&nbsp; ae20.bbr01.eq01.dal03.networklayer.com [173.192.18.136] &nbsp;14&nbsp; &nbsp; 63 ms&nbsp; &nbsp; 65 ms&nbsp; &nbsp; 62 ms&nbsp; po31.dsr01.dllstx3.networklayer.com [173.192.18.225] &nbsp;15&nbsp; &nbsp; 66 ms&nbsp; &nbsp; 64 ms&nbsp; &nbsp; 65 ms&nbsp; po31.dsr01.dllstx2.networklayer.com [70.87.255.66] &nbsp;16&nbsp; &nbsp; 56 ms&nbsp; &nbsp; 60 ms&nbsp; &nbsp; 56 ms&nbsp; te5-1.car13.dllstx6.networklayer.com [70.87.254.234] &nbsp;17&nbsp; &nbsp; 59 ms&nbsp; &nbsp; 57 ms&nbsp; &nbsp; 57 ms&nbsp; 23.86.84ae.static.theplanet.com [174.132.134.35] Trace complete.If yours hangs up somewhere, I think you might be able to reverse search the various ip addresses to see if they belong to your isp.&nbsp; <a href="http://www.domaintools.com/" target="_blank">Domain Whois Lookup, Whois API &amp; DNS Data Research - DomainTools</a>Or if the trace goes nowhere, I think that would definitely indicate an isp problem. Maybe try it while nikonites is working so you have something to compare with.</blockquote>

[QUOTE="nickt, post: 259661, member: 4923"] If you have windows you might want to play with the tracert command. (there is a mac equivalent, but not familiar) I don't know enough to help you troubleshoot, but it might be interesting for you. You open a command prompt window, it should be under Accessories. Type tracert nikonites,com in the command window (I used a comma so it didn't turn into a forum link, use a period). It will return to you the path your request took. I can't help you with the results, way over my head, but the path will not always be the same. Some of the points will be your isp's equipment, some are various carrier connections and you should end at the server hosting nikonites. Here is my result: Tracing route to nikonites.com [174.132.134.35] over a maximum of 30 hops: 1 3 ms 4 ms 3 ms Wireless_Broadband_Router.home [192.168.1.1] 2 10 ms 7 ms 7 ms L100.PGHKNY-VFTTP-08.verizon-gni.net [96.248.38.1] 3 6 ms 7 ms 8 ms G9-3-108.PGHKNY-LCR-01.verizon-gni.net [130.81.131.90] 4 38 ms 23 ms 22 ms 130.81.199.0 5 17 ms 17 ms 19 ms 0.xe-11-3-0.BR2.NYC4.ALTER.NET [152.63.23.137] 6 17 ms 18 ms 15 ms 204.255.173.54 7 25 ms 27 ms 25 ms vlan51.ebr1.NewYork2.Level3.net [4.69.138.222] 8 19 ms 17 ms 17 ms ae-47-47.ebr1.NewYork1.Level3.net [4.69.201.45] 9 25 ms 27 ms 26 ms ae-81-81.csw3.NewYork1.Level3.net [4.69.134.74] 10 24 ms 26 ms 25 ms ae-3-80.edge3.NewYork1.Level3.net [4.69.155.145] 11 24 ms 22 ms 23 ms te2-5.bbr01.tl01.nyc01.networklayer.com [4.26.34.22] 12 44 ms 44 ms 44 ms ae1.bbr01.eq01.chi01.networklayer.com [173.192.18.132] 13 62 ms 63 ms 61 ms ae20.bbr01.eq01.dal03.networklayer.com [173.192.18.136] 14 63 ms 65 ms 62 ms po31.dsr01.dllstx3.networklayer.com [173.192.18.225] 15 66 ms 64 ms 65 ms po31.dsr01.dllstx2.networklayer.com [70.87.255.66] 16 56 ms 60 ms 56 ms te5-1.car13.dllstx6.networklayer.com [70.87.254.234] 17 59 ms 57 ms 57 ms 23.86.84ae.static.theplanet.com [174.132.134.35] Trace complete. If yours hangs up somewhere, I think you might be able to reverse search the various ip addresses to see if they belong to your isp. [URL="http://www.domaintools.com/"]Domain Whois Lookup, Whois API & DNS Data Research - DomainTools[/URL] Or if the trace goes nowhere, I think that would definitely indicate an isp problem. Maybe try it while nikonites is working so you have something to compare with. [/QUOTE]

Verification