authincator

what do I need to change to stop the requirement to use this each time I log in, it used to work for a week now it is each log in, none of my accounts are set on wow to require it on log in,

[bob]

A little bit of setup is required for multiboxing with the authenticators.. http://www.dual-boxing.com/threads/5288 ... post403517

The main problem is each time you log in the next account, the previous authentication is not valid for it, so you need to do it again. Unfortunately if you do it outside of ISBoxer, and then use ISBoxer to load up, ISBoxer virtualises the registry entries for WoW, so a previous authentication doesn't apply.

[jabberie]

By default, the Authenicator will only challenge you once per 30 days if nothing changes in your log in pattern.
Being Challenged every time is a setting you can turn on.
This is the Authenticator Page on Battle.net. The Check box is the Always Challenge option.
https://battle.net/account/management/authenticator.html

If you are getting challenged each time, something in changing to make it think you are not the same person that logged in last time.
Change of IP is the biggest cause.

I've never run in to a problem with ISboxer and authentication beyond my IP changing. (My modem would reset the connection every night on purpose.)

[MiRai]

If you are getting challenged each time, something in changing to make it think you are not the same person that logged in last time.
Change of IP is the biggest cause.

I've never run in to a problem with ISboxer and authentication beyond my IP changing. (My modem would reset the connection every night on purpose.)

What you mention is correct... However, if you aren't using multiple BNet accounts, then it is unlikely that you will experience the issue that the OP is (possibly) describing. Virtualizing an additional registry key, as explained in bob's link, is the method which was discovered to alleviate this problem of constantly having to enter in authenticator (or Captcha code) when using multiple BNet accounts.