When trying to return, be persistent when it tells you wrong password...

[Area51]

I just reinstalled last night, after having been away since last June. POL kept telling me I had the wrong password, so I kept trying every one I could think of that I could have used. After trying different combos of usernames and passwords for like 20 minutes, it finally let me in with the original password I thought I had used. No joke, it is the same password I had entered several times before, and it's very easy and I made sure I didn't misspell it. I just typed it one character at a time, so maybe POL was too slow for my typing or something.

The reason I post this is that I see a lot of threads around (here and other forums) where people panic because they think they forgot their password. Chances are, they didn't, but it's just POL being screwy.

Anyways, after the horrific download of updates last night (left it on overnight, but according to the timer it probably took 3 to 3.5 hours) I am ready to return tonight after work.

[Balfree]

Re: When trying to return, be persistent when it tells you wrong password...

Dont forget to disable CAPS lock (or enable..)

Passwords are case-sensitive

[Macht]

Re: When trying to return, be persistent when it tells you wrong password...

Dont forget to disable CAPS lock (or enable..)

Passwords are case-sensitive

Lol, guess I don't have to say that.... Yeah, I've had POL refuse me because it's become almost second nature to hit Shift when I first starts a sentance or type. Problem is I put my password with a lowercase character starting so throws me off at times.

[Area51]

Re: When trying to return, be persistent when it tells you wrong password...

Nope, had nothing to do with caps lock. Tried it both ways and it was still rejecting my password for a while.

[Omni]

Re: When trying to return, be persistent when it tells you wrong password...

the moogles inside the big pol machine in japan must have been dozing off.

[Jkid]

Re: When trying to return, be persistent when it tells you wrong password...

That never happened to me before, not ever.

[Macht]

Re: When trying to return, be persistent when it tells you wrong password...

If that wasn't it then there is a couple alternatives to why that happened I could guess.

Either bad network connection occuring when you attempted to send the password, when the send failed the system attributed it to incorrect Username/Password even though it never even reached its source. I've had this happen with various network devices, with one device taking well over 3 hrs before it responded. Replaced the bad cable and went just fine after that.

The other I can think is that the server maybe floats the more frequent users to the top of it's indexing so they get faster resonce and the less frequent start becoming archived. So if you are gone long enough it may take the server longer then the set timeout period to find you, so the client is killing the connection as a timeout and stating it's a bad username/password.

If it's the server's side trying to find you then you only need to input the password and username you know is right and give it like 5 min. before trying again. Even though the client terminated the connection usually Pass-Through Queries will continue to run even though the source waiting for it is gone, which means when it find that user it likely floats them higher up in the index so the server finds them faster if they try to log in again after that 5 min. time frame.

Both of those are actual events I've had happened with the servers and devices I use at work.

[Medalink]

Re: When trying to return, be persistent when it tells you wrong password...

Macht FTW! ^^

Medalink