Emergency!! Kurt Needs Help!!

SAMI

Formerly Beardy McGee
Location
SLC, UT
i started a 7 page thread... *EDIT... i made it 8

a big shout out to my homeboys Shawn and JamesK!! you guys rock...:greg:
 
Here is a copy of Kurts trace, looks like he is going through eli.net and not the qwest route. who is scnet.net, and does the "tagged" mean anything. It also hits the 57 IP twice like it is getting bounced around scnet.net.


1 <1 ms <1 ms <1 ms 10.0.0.1
2 55 ms 60 ms 54 ms 67.50.206.1
3 54 ms 53 ms 53 ms fe-4-0-0--0.gw02.slkc.eli.net [209.210.119.17]
4 53 ms 53 ms 52 ms ge-3-1-0--0.cr01.slkc.eli.net [207.173.115.245]
5 52 ms 84 ms 85 ms so-1-0-0--0.cr02.chcg.il.frontiernet.net [74.4.4.238]
6 85 ms 83 ms 85 ms ge-2-0-0--0.br01.chcg.il.frontiernet.net [74.4.4.142]
7 83 ms 85 ms 88 ms ge0-0-1.j2.ord.scnet.net [206.223.119.57]
8 84 ms 85 ms 85 ms ge0-0-1.j2.ord.scnet.net [206.223.119.57]
9 85 ms 85 ms 85 ms so2-1-0.j1.ord.scnet.net [64.202.110.13]
10 84 ms * * tagged.b2.ord.scnet.net [64.202.111.114]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.

Aw, crap. Looks like I'm losing it at the same spot. I had to use a web proxy in England to get access to RME.

Tracing route to rockymountainextreme.com [216.246.1.218]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms dslmodem.domain.actdsltmp [192.168.0.1]
2 41 ms 40 ms 41 ms slkc-dsl-gw10-202.slkc.qwest.net [67.41.239.202]

3 43 ms 42 ms 41 ms slkc-agw1.inet.qwest.net [67.41.239.93]
4 47 ms 42 ms 41 ms slk-core-01.inet.qwest.net [205.171.131.25]
5 58 ms 57 ms 57 ms svx-core-02.inet.qwest.net [67.14.1.58]
6 60 ms 57 ms 63 ms sjp-brdr-01.inet.qwest.net [205.171.214.138]
7 70 ms 68 ms 80 ms sjo-bb1-geth1-2-0.telia.net [213.248.86.13]
8 113 ms 81 ms 69 ms las-bb1-pos7-0-0-0.telia.net [213.248.80.17]
9 99 ms 104 ms 120 ms dsl-bb1-pos7-0-0.telia.net [213.248.80.14]
10 99 ms 99 ms 104 ms chi-bb1-pos7-1-0-0.telia.net [213.248.80.150]
11 99 ms 156 ms 150 ms so2-2-0.j1.ord.scnet.net [216.246.12.93]
12 99 ms 102 ms 99 ms tagged.b2.ord.scnet.net [64.202.111.114]
13 100 ms 113 ms * tagged.b2.ord.scnet.net [64.202.111.114]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
 

waynehartwig

www.jeeperman.com
Location
Mead, WA
I was ready to drop everything and load up the Cruiser on the trail and rush to his needs. Instead I read that he can not get on the board.............:ugh:

WTF....:shawn: :shawn:

x2 WTF! :shawn:
I'm out in the middle of know where, waiting for my freakin' aircard to load a browser, all the while tripping out and thinking sh!t what can I do from 700 miles away to help! Not cool...:mad2:
 

cruiseroutfit

Cruizah!
Moderator
Vendor
Location
Sandy, Ut
OK, I'm back off again... It started yesterday ~5pm, no service since, but as usual works fine elsewhere. Oddly I was right in the middle of writing a post, and then nothing... Cannot find server. Can I call my ISP and tell them? I tried last time and they seemed to think it was my firewall?

Oddly I am not using the same ISP as last time, now we have Quest (changed last week)...

Anyone else having issues?
 

Brett

Meat-Hippy
Off and on I've had problems. Here at work, my house, my parents house....doesn't seem to matter. I'm on Quest at home too......I doubt that is what AmEx is using though ;)
 

cruiseroutfit

Cruizah!
Moderator
Vendor
Location
Sandy, Ut
Off and on I've had problems. Here at work, my house, my parents house....doesn't seem to matter. I'm on Quest at home too......I doubt that is what AmEx is using though ;)

My comcast service is great, albeit it seems a bit slower than the DSL?

Rusted fixed me up last time (Thanks again :cool:), mabey I'll have to learn myself on these computers and figure it out myself... :rofl:
 

Herzog

somewhat damaged
Admin
Location
Wydaho
I'll see if we can reply to the same ticket as before. It was the host that was causing the problems. Their firewall automatically banned a range of ip addresses to prevent DoS attacks last time. We'll see...
 
Top