#41
|
|||
|
No luck with Tech Support spent 2 hours on the phone, even let the tech guy remote connect and watch as it happened. Tried using the Shield program and the first time it said IP was already in use, so gave up last night, tried today and it came up with a message my account was banned, was freaking out for a bit. Then tried connecting on my cell phone connection which is laggy as shit (but connects fine) and was able to log in fine not banned, so I'm done trying for awhile.
| ||
#42
|
||||
|
Quote:
| |||
#43
|
|||
|
had tech come out, checked lines and no issues (obvious now...)
Def something serverside or in the new spell file it appears being that it started then and isnt just Uverse... | ||
#44
|
|||
|
time warner here - zero issues
| ||
#46
|
|||
|
Had a tech come out today and asked him if he knew anything about ATT Uverse recently blocking ports and he didn't know. Told me to run a traceroute and it does appear that something is dropping on ATT's end. Ran it several times and the 3rd and 4th hops are consistently timing out.
Code:
1 1 ms 1 ms 3 ms homeportal [192.168.x.xxx] 2 37 ms 23 ms 23 ms xx-xxx-xx-x.lightspeed.hstntx.sbcglobal.net [xx .xxx.xx.x] 3 * * * Request timed out. 4 * * * Request timed out. 5 22 ms 22 ms 22 ms 151.164.38.222 6 34 ms 34 ms 36 ms 151.164.101.82 7 74 ms 74 ms 76 ms 151.164.251.150 8 89 ms 89 ms 89 ms po1-20G.ar3.ATL2.gblx.net [67.16.143.174] 9 101 ms 101 ms 96 ms netriplex.tengigabitethernet8-4.ar3.atl2.gblx.ne t [207.136.166.174] 10 114 ms 115 ms * te-4-0-0.rtr1.avl1.netriplex.com [67.23.161.129] 11 121 ms 115 ms 115 ms te-5-4.rtr2.avl1.netriplex.com [67.23.161.134] 12 207 ms 115 ms 114 ms eqemulator.net [67.23.190.71] Trace complete. | ||
#47
|
|||
|
I'm suprised this is ISP business is still going on - I am pretty sure it is -not- an ISP issue.
| ||
#48
|
|||
|
| ||
#49
|
|||
|
thats not a fix, thats doing what everyone was supposed to do...
| ||
#50
|
||||
|
Quote:
| |||
Last edited by GLGanjika; 03-20-2011 at 03:51 PM..
|
|
|