Client Submitted Invalid Key -> ASGS Protection Tripped

[Malicious Wraith]

Whats this about?

• Checking for system updates
• Checking for existing processes
• Saving Settings
• Saving MRU Callsigns
• Checking connectivity
• Using Port: HTTP
• Checking ASGS Client Version
• Client Version: 155
• Server Version: 155
• Securing Installation
• ASGS Protection Tripped.
• ASGS Protect will unlock in 15 minutes.

[ImmortalZ]

Hmm.

You either had too many connections to the ASGS server at the same time or tried to hammer it by trying to logon (with a wrong p/w or username) too quickly. Or it may be for other reasons that only the ASGS admin(s) can look up. I'll pass this on.

[Malicious Wraith]

QUOTE (ImmortalZ @ Aug 17 2007, 08:49 PM) Hmm.

You either had too many connections to the ASGS server at the same time or tried to hammer it by trying to logon (with a wrong p/w or username) too quickly. Or it may be for other reasons that only the ASGS admin(s) can look up. I'll pass this on.

I tried to log on with the correct username and password, but it kept giving me the "Client Submitted Invalid Key" thingy.

Then the protection tripped after many try's. I log back on later with the same username and password and it works fine.

This is not the first time I have gotten Client Submitted Invalid Key, but I have gotten it for many more times consecutively now then ever before.

Edit: Was only a single ASGS connection as well. Just me.

[Tigereye]

You know MW...

it seems you're always running into linked accounts (where all info about each account is identical), or you're tripping ASGS protection, or otherwise doing things that keep putting you on the radar.

What gives?

Why hasn't any other member of our community run into these problems?

Why do you think our system keeps singling you out?

--TE

[Malicious Wraith]

Im not screwing with ASGS if thats what you are saying.

If you were actually looking for a real answer, I have no friggin clue as to why, I dont even know how the ASGS system works, or any of the mechanics behind it.

[Malicious Wraith]

Ok, just started logging in today again, and it said it twice:

7 11:12:01 PM
• Allegiance exited with code: 0
• Beginning Logout
• Closing processes
• Sending Logout Request
• Logged Out
• Checking for system updates
• Checking for existing processes
• Saving Settings
• Saving MRU Callsigns
• Checking connectivity
• Using Port: HTTP
• Checking ASGS Client Version
• Client Version: 155
• Server Version: 155
• Securing Installation
• Validating Installation
• Preparing Key
• Key Generated
• Connecting to ASGS Server
• Authenticating
• Ticket Received
• Return Value: 1
• Callsign:
• Client submitted an invalid key.
• Checking for system updates
• Checking for existing processes
• Saving Settings
• Saving MRU Callsigns
• Checking connectivity
• Using Port: HTTP
• Checking ASGS Client Version
• Client Version: 155
• Server Version: 155
• Securing Installation
• Validating Installation
• Preparing Key
• Key Generated
• Connecting to ASGS Server
• Authenticating
• Ticket Received
• Return Value: 1
• Callsign:
• Client submitted an invalid key.

[FreeBeer]

I don't see you having posted anything about having SMART turned on in the BIOS...

[ImmortalZ]

If he doesn't, he would not be able to log in at all.

[Malicious Wraith]

So whats that all about?

[ImmortalZ]

Only TE/Pook can tell you whats happening when you fail to log in.