rycanada's endless connection saga

[IronWolf]

Isn't that part of my ipconfig/all (posted above) or do you need something else?

The one from the ipconfig /all shows the IP of your computer, which was an IP for use on private networks. I need to be sure of your public address. You can check it by going here:

http://www.whatismyip.org/

from a browser. That's the address I will need to pass along to cyberstreet,

Thanks!

 

[Ry]

And the answer: 99.246.210.39

 

[IronWolf]

Email sent to Cyberstreet with the IP information.

 

[Ry]

Email sent to Cyberstreet with the IP information.

Wolf/P-Cat, can you post a message when you get a reply? So far no luck, but I imagine 48 hours turnaround wouldn't be unusual.

 

[Ry]

Still nada (zero, zilch, niente - bupkiss)

Did Mouse have better luck?

 

[Piratecat]

I wasn't at work today, Ryan, so I'm not sure of the latest. We'll stay on top of this to figure out the problem.

 

[Mouseferatu]

Still no luck for me. I can post right now, because I'm at my mother's place, but as of this afternoon when I left home, I still couldn't get here from my own connection.

 

[IronWolf]

I heard back from Cyberstreet and the filtering they do would not let the pings and traceroutes from Windows work. So there is still something not adding up.

This is a long shot, but can someone having trouble please download the demo version of PingPlotter standard here:

http://www.pingplotter.com/standard.html

Install that, then open it and go to Edit | Options. Click on Packet and switch the Packet type to UDP Unix style in the drop down. Then say okay and back in the main windows type in www.enworld.org as the address to trace to. Set the sampling number to 3 or 5. Then click the Trace button. Let me know what it says.

 

[Ry]

OK, trying Wolf's suggestion... (I'm posting using bypasser.info as a web-based proxy, it's really slow)

I followed Wolf's suggestions, then tried selecting copy-as-text and pasted below:

Target Name: www.enworld.org
IP: 65.127.163.19
Date/Time: 12/05/2007 12:26:24 PM to 12/05/2007 12:28:39 PM

1 2 ms 2 ms 2 ms 2 ms 2 ms 2 ms 1 ms 2 ms 1 ms 2 ms [192.168.1.1]
2 9 ms 9 ms 7 ms 10 ms 608 ms 10 ms 9 ms 9 ms 8 ms 9 ms [10.104.188.1]
3 9 ms 9 ms 11 ms 9 ms 562 ms 12 ms 9 ms 10 ms 21 ms 9 ms gw03.mtnk.phub.net.cable.rogers.com [66.185.90.97]
4 8 ms 10 ms 10 ms 21 ms 583 ms 8 ms 10 ms 8 ms 10 ms 12 ms gw02.mtnk.phub.net.cable.rogers.com [66.185.83.105]
5 9 ms 11 ms 11 ms 9 ms 661 ms 11 ms 10 ms 11 ms 10 ms 93 ms gw03.ym.phub.net.cable.rogers.com [66.185.83.126]
6 26 ms 26 ms 26 ms 26 ms 635 ms 26 ms 26 ms 27 ms 27 ms 59 ms pos-6-0-0.igw01.vaash.phub.net.cable.rogers.com [24.153.5.230]
7 30 ms 31 ms 30 ms 30 ms 591 ms 32 ms 33 ms 30 ms 30 ms 30 ms if-15-0.core4.AEQ-Ashburn.teleglobe.net [209.58.27.33]
8 41 ms 32 ms 32 ms 41 ms 580 ms 32 ms 34 ms 30 ms 30 ms 31 ms if-0-2.core3.AEQ-Ashburn.teleglobe.net [216.6.51.17]
9 29 ms 33 ms 26 ms 25 ms 531 ms 27 ms 26 ms 38 ms 26 ms 27 ms dcp-brdr-01.inet.qwest.net [63.146.26.25]
10 26 ms 27 ms 26 ms 27 ms 518 ms 82 ms 26 ms 27 ms 26 ms 28 ms dcx-core-01.inet.qwest.net [205.171.251.57]
11 54 ms 96 ms 53 ms 53 ms 498 ms 59 ms 54 ms 53 ms 54 ms 53 ms tpa-core-01.inet.qwest.net [67.14.3.2]
12 106 ms 80 ms 59 ms 59 ms 490 ms 60 ms 56 ms 59 ms 59 ms 58 ms nap-edge-01.inet.qwest.net [205.171.27.50]
13 66 ms 63 ms 62 ms 128 ms * * * * * * [65.124.198.234]
14 66 ms 63 ms 62 ms 128 ms * * * * * * [65.124.198.234]
15 * * * * * * * * * * [-]
16 * * * * * * * * * * [-]
17 * * * * * * * * * * [-]
18 * * * * * * * * * * [-]
19 * * * * * * * * * * [-]
20 * * * * * * * * * * [-]
21 * * * * * * * * * * [-]
22 N/A N/A N/A N/A N/A N/A N/A 341 ms * * [65.124.198.234]
23 N/A N/A N/A N/A N/A N/A 63 ms * * * [65.124.198.234]
24 N/A 66 ms * 114 ms * 64 ms * * * * [65.124.198.234]
25 63 ms * 62 ms * * * * * * * [65.124.198.234]
26 * * * * * * * * * * [-]
27 * * * * * * * * * * [-]
28 * * * * * * * * * * [-]
29 N/A 66 ms * 114 ms * 64 ms * * * * [65.124.198.234]
30 63 ms * 62 ms * * * * * * * [65.124.198.234]
31 * * * * * * * * * * [-]
32 * * * * * * * * * * [-]
33 * * * * * * * * * * [-]
34 * * * * * * * * * * [-]
35 * 64 ms * * * * * * 63 ms 62 ms [65.124.198.234]
36 * * * * * * * * * * [-]
37 * * * * * * * * * * [-]
38 * * * * * * * * * * [-]
39 * * * * * * N/A N/A N/A N/A [65.124.198.234]
40 66 ms * * * * 63 ms N/A N/A N/A N/A [65.124.198.234]
41 * * 63 ms 64 ms N/A N/A N/A N/A N/A N/A [65.124.198.234]

Destination not reached in 35 hops

 

[IronWolf]

Once again thanks rycanada! I think we might *finally* at least have a more solid finger to point. I will spare folks the tech details, but take a look at one of your normal tracerts from windows and the one I just had you do with PingPlotter and UDP packets.

Your last response with the UDP trace is at 65.124.198.234. Looking back to your normal tracert in Windows you should have hit 63-144-217-198.cust.neotechus.com in that UDP trace, but you aren't getting responses from it. Looks like we may be back to freaky stuff from the neotechus.com network like we saw with the Australians.

I have a kid begging me to get ready to go to the zoo, so I will be offline this afternoon. If you could... As you have time, just repeat that trace from PingPlotter here and there. No need to post the results unless they change - just later today mention whether they were staying the same or not.

Also, please try the same settings in PingPlotter, but trace to www.cyberstreet.com and post those results when you have a chance.

Thanks!

EDIT: rycanada, I PM'ed you my email address. There is no point in making you suffer the slow proxy just to report the t-shooting info I have asked for.