Battle.NET account + Blizzard Authenticator + today = fail

[Targ]

Pushing the button just causes the Display to turn on, the code that is displayed is an encription of the Time of Day (likely rounded to 30 sec) and the Fob serial number.

(there is probably also some tracking server side for the previous and next valid numbers to account for the timebase drift that likely happens on the keychain unit, since it is bound to be significant and would vary with temperature and such)

I suspect it is the Time of Day tracking on the Server side that is issue. When the servers decript the code they get the Time of Day on your Fob. On the Servers they are keeping up with the drift from real time for each Fob on each account in their system, other wise your FOB would stop working when the internal clock drifted too far off real time.

I am thinking that when you log into one Battle.NET account 5 times, it does not like five different FOB time of Day updates in a row with the same TOD, and rejects them. The drift calculation may not like Zero time difference from the last log on. Where as when the accounts were seperate they got a single FOB time of Day Update on each account accross your Five acounts, and then they where keeping up a seperate Drift calculation on each account.

[Svpernova09]

Pushing the button just causes the Display to turn on, the code that is displayed is an encription of the Time of Day (likely rounded to 30 sec) and the Fob serial number.



I suspect it is the Time of Day tracking on the Server side that is issue. When the servers decript the code they get the Time of Day on your Fob. On the Servers they are keeping up with the drift from real time for each Fob on each account in their system, other wise your FOB would stop working when the internal clock drifted too far off real time.

I am thinking that when you log into one Battle.NET account 5 times, it does not like five different FOB time of Day updates in a row with the same TOD, and rejects them. The drift calculation may not like Zero time difference from the last log on. Where as when the accounts were seperate they got a single FOB time of Day Update on each account accross your Five acounts, and then they where keeping up a seperate Drift calculation on each account.

You could be right, but the issue here is this WAS working. Something broke, or someone changed something to no longer allow this.

[Svpernova09]

I sent the paste below via the Contact Support function on blizzard.com We'll see if they get back to me. I haven't had good luck with them before, they proved to be pretty terrible last time I had to contact them about an account I couldn't get in game with.

After maintenance yesterday, 10/13/09 I am no longer able to login 5 accounts with 1 authenticator code. Before maintenance I was using 1 authenticator code to login all 5 of my accounts at the same time. Now 1 logs in, 4 fail. I have to wait till I can generate 5 unique authenticator codes. There are threads posted about others having the same issue: http://forums.worldofwarcraft.com/th...33766552&sid=1 and also http://forums.worldofwarcraft.com/th...62448559&sid=1 Is this an intended change? Is there any way to revert the back to how it was working before?

[Svpernova09]

Question - Are you guys using the key-fob authenticator (i am) or the iphone application? (or other smart phone).

The application is bnet specific, where the key-fob was before bnet conversions. I'm thinking about switching mine to my iphone and trying that.

Using key-fob here, I don't have a supported phone to test /grumble

[moosejaw]

I am using a key-fob also. Any iPhone users around to tell us if it works for them?

Edit: Not sure if I want to blow all that $$ on an iPhone, but if that is the solution, I would consider it.

[Korruptor]

I am using a key-fob also. Any iPhone users around to tell us if it works for them?

Edit: Not sure if I want to blow all that $$ on an iPhone, but if that is the solution, I would consider it.

I have an iPhone but I'm at work so I can't test it yet.

EDIT:
In case you don't want/need an Iphone, the BNet authenticator works with the Ipod Touch as well.

[moosejaw]

I have an iPhone but I'm at work so I can't test it yet.

EDIT:
In case you don't want/need an Iphone, the BNet authenticator works with the Ipod Touch as well.

Hmmm. Nice to know. I have an ATT phone now and I would suffer a huge purchase/upgrade penalty if I get an iPhone right now. The Touch would be a good compromise.

[Bigfish]

I'm not having this issue with my non-Bnet accounts.

[Drommon]

I'm not having this issue with my non-Bnet accounts.

Likewise. I will switch to Bnet at the last minute. There are just too many nuances to multi-boxing to have to suffer through another one of blizzards gimmicks. As for now, I am sticking to non-bnet single authenticator code for all accounts.

Drommon

[Slats]

I have an iPhone its how I use my authenticator. I still have the 4 accounts fail, 1 logs in successfully issue, but I can simple try again on another character and it loads fine. More annoying than a game breaker.

It seems to be one password + one key attempt. You can use the same key multiple times tho. Just not AT the same time. Its annoying. :/