I'm sure no one wants to even look at me/this, much less respond to it.
Given the historical issues with the Power Tier in another thread (http://www.dslreports.com/forum/r28734599-No-45MB-Speed-for-me-), I am hoping it is acceptable to start this issue as a new topic versus appending to the existing.
Since those who were involved in my previous thread know the unstable nature of, and VERY slow speed of, the Power Tier w/Uverse, could someone give some pointers as to where to begin based upon the steps already taken?
Uverse is not interested, in the least, to try & offer any insight as to a "connection between my known issues & the VPN failures/drops" which I sort of understand but rebut. My rebuttal is based upon the service, itself, being unstable & is therefore the likely culprit in the VPN issues. I admit little knowledge on the Cisco VPN/Concentrator/SecurID authentication other than what I have read on my own. While this offers insight into this authentication process, trying to pinpoint where is becoming just as difficult as the known Uverse service issue.
On the opposite end, in the "logs" of the VPN I'm connecting to, all they show are me "dropping off" as a result of a "missed heartbeat" if I am able to connect at all. VPN is initiated through the Cisco VPN client, enter my username, passcode, and the six digits from the SecurID token; most of the time, the first failure to connect comes back as the token lapsing, despite me "waiting it out" if there are less than 3 bars on the current token digits. The next attempt USUALLY connects, however it is still a VERY slow connection process compared to pre-power-tier and/or from a different internet connection altogether.
If I am successful in connecting, once that "heartbeat skips", it's all over & back to re-authenticating I go. From my understandings from the NA's advice, the issue is stemming from my connection which, again given the Uverse issues, makes sense.
Does anyone have some type of "testing" that I could do, over a period of time, or any other type of connectivity "testing" to where I could truly pinpoint this as either an issue on my end or an issue within the VPN client? I cannot see this as an issue on the far end given there are no others reporting this behavior & our NA is pretty baffled.
I know the whole SecurID aspect is "in and of itself" so to speak & timing is everything, but as stated above, I ensure I wait until I get a new set of numbers before attempting the connection. The "loss of a heartbeat" further makes me believe the issue is on my end - my internet connection that is - and not that of an issue with the PC/VPN client.
Thank you in advance & if I have answered my own question, at least partially, I do apologize for the irritations. This Uverse issue, as a whole, has been a nightmare in and of itself & now that I'm having the VPN problems, I just do not want to jump to conclusions & declare the Uverse service as the culprit without doing as much as I can in order to support this. Otherwise, I will continue to basically be battling Uverse "blind" as I have nothing to support the connectivity itself as to why I'm failing to authenticate timely, failing to authenticate due to the expired token, and this disconnection due to "skipping heartbeats". Hell my own heart skips beats & yet I'm still functioning LOLOL. I wish I knew more on this so I did not have to bother you all with yet another issue.
Again I certainly apologize to all for bothering with this - particularly if the answer is fairly obvious. It's hard for me to discern such as all these issues w/Uverse & now this have me fairly biased.
Thanks again everyone :)
↧