test content
Logo
What is the Arc Client?
Install Arc
Forums > Home› descenderx› Comments
Howdy, Stranger!
Comments
-
No worries. I'll end the pseudo-spam here ;). Best of luck!
-
[EDIT: This may not be terribly meaningful depending on their setup. Don't kill yourself :)] Start -> Run -> cmd (hit ok) tracert 208.95.185.165 - Right click/mark - Select - Right click (copies to clipboard) Paste. Remove anything you're not comfortable sharing (not that it's generally a big deal; just for your own peace…
-
Resolution removed to reduce the conjecture. I'd recommend using http://www.locaping.com - lets you generate traces from around the globe ;). 1 <1 ms <1 ms <1 ms 192.168.0.1 2 7 ms 8 ms 6 ms 10.125.244.1 3 16 ms 16 ms 15 ms 67.231.220.161 4 15 ms 15 ms 16 ms [cable hop 1] 5 13 ms 16 ms 12 ms [69.196.136.36] 6 14 ms 13 ms…
-
I'm probably just lucky ;). Regardless, token/auth systems are definitely more secure, but they're an absolute nightmare to debug when something goes awry. Even if it's just a dead network link or a VM that went to sleep. Your auth server doing this from my end is: 208.95.185.165
-
It doesn't look like a ban. See my results in post #44. If anyone else knows a thing or two about networking, fire up wireshark, change your account password, and see if you get the same results I did - identical hash values (tokens) before and after. It might help them isolate the issue. Anything else will just be useless…
-
Wiresharking reveals some more information... See my support ticket ( # 2333665 ) for more information on my debugging path. [EDIT]: I rotated my password and am receiving identical tokens & static seeds. I've seen this kind of thing before in production environments when a new salt is generated either incorrectly, or…