Problem back again

[rickf73]

Can't connect to SU at work again. Seems similar to what happened last year. A few months after SU came up I could no longer connect. Changed to Cox the last week of March and could get back on with no problem. 2 months later back to the same thing.

Lost connection to site Wed. afternoon. Google and IE just say they can not connect, Firefox says it timed out.

If I ping SU I receive a time out error also.

Trace Route from both, times out at work just before getting to SU.

From Work.



Tracing route to host.stangsunited.com [67.222.8.137]
over a maximum of 30 hops:

1 7 ms <1 ms <1 ms 192.168.1.1
2 9 ms 7 ms 7 ms 10.136.112.1
3 9 ms 7 ms 9 ms 24.248.104.17
4 6 ms 5 ms 11 ms btnrdsrj01-ae3.0.rd.br.cox.net [24.248.104.178]

5 55 ms 53 ms 55 ms langbprj01-ae2.rd.la.cox.net [68.1.1.17]
6 51 ms 51 ms 51 ms br02-1-1.lax4.net2ez.com [64.93.64.89]
7 53 ms 53 ms 52 ms br01-1-1.lax3.net2ez.com [64.93.64.161]
8 55 ms 55 ms 60 ms cr01-1-1.lax6.net2ez.com [72.172.64.46]
9 55 ms 56 ms 54 ms la-gw.privatesystems.net [72.172.66.10]
10 54 ms 54 ms 54 ms vz41-ca.privatesystems.net [72.172.67.41]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.

--------------------------------------------------------------------------------------
From Home

Tracing route to host.stangsunited.com [67.222.8.137]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms LYNN [192.168.1.1]
2 11 ms 22 ms 11 ms 10.135.178.1
3 10 ms 9 ms 10 ms 24.248.104.58
4 8 ms 8 ms 6 ms btnrdsrj02-ae3.0.rd.br.cox.net [24.248.104.182]

5 54 ms 60 ms 53 ms langbprj01-ae2.rd.la.cox.net [68.1.1.17]
6 52 ms 54 ms 55 ms br02-1-1.lax4.net2ez.com [64.93.64.89]
7 61 ms 56 ms 58 ms br01-1-1.lax3.net2ez.com [64.93.64.161]
8 73 ms 65 ms 57 ms cr01-1-1.lax6.net2ez.com [72.172.64.46]
9 53 ms 54 ms 59 ms la-gw.privatesystems.net [72.172.66.10]
10 65 ms 53 ms 52 ms vz41-ca.privatesystems.net [72.172.67.41]
11 70 ms 56 ms 56 ms host.stangsunited.com [67.222.8.137]

Trace complete.

Any idea's on what the problem could be would be appreciated.


Looks like I will have to do some work while I am at work again. :grin:

[Tommy Gun]

I'll just :ban: you and you won't have to worry about it.







:tiptoe:

.

[rickf73]

I'll just :ban: you and you won't have to worry about it.






:tiptoe:

.


:boink:



I just thought you set me to miserable anyway. :grin:

[Tommy Gun]

:crutch:

[Dad's72Mach]

Sounds like operator error. Ole Miss fans get kinda confused with anything more technical than a couple cans and some string.



:pimp:

[rickf73]

Sounds like operator error. Ole Miss fans get kinda confused with anything more technical than a couple cans and some string.



:pimp:


At least Ole Miss fans can use a can and a string.

:grin:

[Shlbylvr]

At least Ole Miss fans can use a can and a string.

:grin:

But a can and A string won't get you the Internet.



:haha:

[Joker]

Rick,

Try it again and let me know if it works now from your work IP address.

[Dad's72Mach]

At least Ole Miss fans can use a can and a string.

:grin:

Touche. Well played sir.


:pimp:

[rickf73]

Rick,

Try it again and let me know if it works now from your work IP address.

Works fine now. :tiphat2:

Thats the reason you get the big bucks. :moneyman:

[Gr8snkbite]

Rick,

Try it again and let me know if it works now from your work IP address.

Rob,

go into our gmail acct and review the emails there from cpanel....interesting, but i have no clue

[Joker]

Rob,

go into our gmail acct and review the emails there from cpanel....interesting, but i have no clue

Sorry I can't do that. I don't have access to that info.

I'm not that high up the ladder here:tease2:

[Joker]

Works fine now. :tiphat2:

Thats the reason you get the big bucks. :moneyman:

Glad I got it worked out for you. Let me know if it happens again.

[rickf73]

Glad I got it worked out for you. Let me know if it happens again.

Will do, actually the site seems to be loading much faster than before.

[Gr8snkbite]

Sorry I can't do that. I don't have access to that info.

I'm not that high up the ladder here:tease2:

thought you did..i'll forward to you or have G do it...

[Joker]

Will do, actually the site seems to be loading much faster than before.

Cool. I did some stuff this morning but I doubt it helped site speed.


thought you did..i'll forward to you or have G do it...

I'll check it out. Thanks.

[HSURB]

Thanks Robert.

Rick's boss isn't so thankful. :haha::haha:

HSURB®

[Birdman]

Can't connect to SU at work again. Seems similar to what happened last year. A few months after SU came up I could no longer connect. Changed to Cox the last week of March and could get back on with no problem. 2 months later back to the same thing.

Lost connection to site Wed. afternoon. Google and IE just say they can not connect, Firefox says it timed out.

If I ping SU I receive a time out error also.

Trace Route from both, times out at work just before getting to SU.

From Work.



Tracing route to host.stangsunited.com [67.222.8.137]
over a maximum of 30 hops:

1 7 ms <1 ms <1 ms 192.168.1.1
2 9 ms 7 ms 7 ms 10.136.112.1
3 9 ms 7 ms 9 ms 24.248.104.17
4 6 ms 5 ms 11 ms btnrdsrj01-ae3.0.rd.br.cox.net [24.248.104.178]

5 55 ms 53 ms 55 ms langbprj01-ae2.rd.la.cox.net [68.1.1.17]
6 51 ms 51 ms 51 ms br02-1-1.lax4.net2ez.com [64.93.64.89]
7 53 ms 53 ms 52 ms br01-1-1.lax3.net2ez.com [64.93.64.161]
8 55 ms 55 ms 60 ms cr01-1-1.lax6.net2ez.com [72.172.64.46]
9 55 ms 56 ms 54 ms la-gw.privatesystems.net [72.172.66.10]
10 54 ms 54 ms 54 ms vz41-ca.privatesystems.net [72.172.67.41]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.

--------------------------------------------------------------------------------------
From Home

Tracing route to host.stangsunited.com [67.222.8.137]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms LYNN [192.168.1.1]
2 11 ms 22 ms 11 ms 10.135.178.1
3 10 ms 9 ms 10 ms 24.248.104.58
4 8 ms 8 ms 6 ms btnrdsrj02-ae3.0.rd.br.cox.net [24.248.104.182]

5 54 ms 60 ms 53 ms langbprj01-ae2.rd.la.cox.net [68.1.1.17]
6 52 ms 54 ms 55 ms br02-1-1.lax4.net2ez.com [64.93.64.89]
7 61 ms 56 ms 58 ms br01-1-1.lax3.net2ez.com [64.93.64.161]
8 73 ms 65 ms 57 ms cr01-1-1.lax6.net2ez.com [72.172.64.46]
9 53 ms 54 ms 59 ms la-gw.privatesystems.net [72.172.66.10]
10 65 ms 53 ms 52 ms vz41-ca.privatesystems.net [72.172.67.41]
11 70 ms 56 ms 56 ms host.stangsunited.com [67.222.8.137]

Trace complete.

Any idea's on what the problem could be would be appreciated.


Looks like I will have to do some work while I am at work again. :grin:

It sounds like our site host got you confused with Tommy Gun....he's the one who needs a "Time-out" ...:mine:


Thanks Robert for helping out with this :wtg:

[rickf73]

Thanks Robert.

Rick's boss isn't so thankful. :haha::haha:

HSURB®

Maybe he is the one that keeps screwing with my connection, maybe I should cut off his Facebook connection. :grin:

[rickf73]

It sounds like our site host got you confused with Tommy Gun....he's the one who needs a "Time-out" ...:mine:


Thanks Robert for helping out with this :wtg:

I knew it had to be TG's fault.


:giggle:

[68fastback]

This sounds similar to what I see occasionally (last time was May 23) where I'll get locked out for a half-hour or so. I was able to trace the route last time and it was a dozen hops three of whcih were in Germany. Strange.

[Tommy Gun]

It sounds like our site host got you confused with Tommy Gun....he's the one who needs a "Time-out" ...:mine:


Thanks Robert for helping out with this :wtg:


:hey2:


Just remember who signs all you peoples checks around here. :sherriff:


.

[Birdman]

:hey2:


Just remember who signs all you peoples checks around here. :sherriff:


.

yeah Alloy Dave....:spitcopy:

[Tommy Gun]

:doh2:

[Joker]

yeah alloy dave....:spitcopy:

lmao!

[68fastback]

:haha:

[onecrazydog]

Site locked me out from home for a few days... Pffft, whatever, ignore my pings...

Still worked at the office though... I cleared all history and cookies (GRRRRR), acquired a new ip at home, so not sure if that was the fix...

[admin]

Site locked me out from home for a few days... Pffft, whatever, ignore my pings...

Still worked at the office though... I cleared all history and cookies (GRRRRR), acquired a new ip at home, so not sure if that was the fix...


see the thread TG posted i have been responding in. I had KH remove the block. Sorry about that Dog....:grin:

[Tommy Gun]

Dog can't see the moderator threads :groan:

[admin]

Dog can't see the moderator threads :groan:


didnt realize it was in that section....i was focused on correcting the issue....:grin:

[onecrazydog]

see the thread TG posted i have been responding in. I had KH remove the block. Sorry about that Dog....:grin:

Thanks guys!!

[admin]

Thanks guys!!

Dog...below is what we got from KH on your issue...


Ip block is removed....:grin:

Its not a matter of attempts to log in. If that were the case, the gmail report from KH would indicate 5 attempts. This was a mod_security issue in which his IP triggered it which prompted the block to prevent what the server thought was an attack. I am in discussion with kH to figure what cause the trigger to begin with.

this was the cause of the block....[id "950005"] [msg "Remote File Access Attempt"]

possibly his server was acting up at the time. Sunday attempts were 7 at the exact same time, to the second. Mon were two attempts at the same time (6 sec apart) and got this code..[id "950801"] [msg "UTF8 Encoding Abuse Attack Attempt"]

[Boston Mike]

Dog can't see the moderator threads :groan:

can that Ramone guy see them?

[Boston Mike]

Dog...below is what we got from KH on your issue...


Ip block is removed....:grin:

Its not a matter of attempts to log in. If that were the case, the gmail report from KH would indicate 5 attempts. This was a mod_security issue in which his IP triggered it which prompted the block to prevent what the server thought was an attack. I am in discussion with kH to figure what cause the trigger to begin with.

this was the cause of the block....[id "950005"] [msg "Remote File Access Attempt"]

possibly his server was acting up at the time. Sunday attempts were 7 at the exact same time, to the second. Mon were two attempts at the same time (6 sec apart) and got this code..[id "950801"] [msg "UTF8 Encoding Abuse Attack Attempt"]

**** Canadian cyberhackers................

[Joe G]

**** Canadian cyberhackers................
Nah... their strange language gives them away.

http://www.iwantnetware.com/canadian_keyboard.jpg

[68fastback]

:giggle:

[Tommy Gun]

can that Ramone guy see them?


Maybe :shades: