Nostalrius Begins - Quality wow vanilla realm (1.12)

I keep getting a disconnected message when I try to login.

I got my brother to login to his account so it's not our connection or anything.

I figured I may have been entering in my password incorrectly, so I went ahead and reset it, but I still am unable to login.

Any help would be greatly appreciated.

Did your brother log into his account on your PC or his own?

If he did on his own PC;
Are you sure the realmlist is 100% correct?

Is your client 1.12?

"Disconnected from server" ?

Happening to me aswell. Was playing fine yesterday.

Naulii wrote:Did your brother log into his account on your PC or his own?

If he did on his own PC;
Are you sure the realmlist is 100% correct?

Is your client 1.12?

I was able to login just fine last night, but I tried logging in on his machine for good measure and still get the "Disconnected from Server" message.

The realmlist also looks correct.

c0m4ndo45 wrote:"Disconnected from server" ?

Happening to me aswell. Was playing fine yesterday.

And here I was looking forward to getting some playtime in after just getting off of work.

I am having the same issue, with the same free evening disappointment

Considering that my brother is able to connect to the server on his account. Is this an account issue?

Has my account been banned? I didn't get any email or notification of any such thing, but at this point I assume not being able to login could be one way of getting the message across.

Ok, so it looks like I can get into my account. My brother noticed something where his first login always failed, but his second one went through.

I may have had made a mistake entering in my password on the second attempt which would have failed it, but so far it's held up that I always get the disconnect message on the very first login.

Just wanted to update the thread. Should I maybe post a bug report regarding this?

Apparently this was a problem which happened to a lot of players (some guildmates told me they had a hard time logging in).

There is probably no bug, but there was a little problem with the login server.