Error - Connection Timed Out (Ragefire)

I can get to the server select just fine by normally logging in through their client. Once I boot up the boxes with ISBoxer, I get Error - A Timeout Has Occurred, over and over and over. Any ideas? Was working fine last night.

Are they possibly trying to combat the use of ISBoxer, or am I just doing something wrong? Highly guessing it's the latter, but thanks for any help!

[MiRai]

When do you get the error? After entering your password? If so, entering a wrong password will give you a timeout error and not a "wrong password" error. If that is the issue, then disabling Key Maps (Shift Alt M) will fix the issue unless you've added additional Key Maps which aren't being toggled off.

I get the error after entering my password. I know I'm using the correct password. What's really strange is it gives me the error - timeout has occurred. But then when I go to log in normally through the client, it says "You've had # of failed login attempts."

It even does it if I just a single client via ISBoxer

Low and behold, I did have something in my DPS rotation assigned to the number 2, which is also in my password, and I think that might have actually been screwing things up. Now that I changed the hotkey, now it won't let me type in the number 2, weird.

[bob]

Usually you Disable key maps (SHIFT+ALT+M) when typing in your password to prevent any of them interfering with the direct input you are trying to enter.

As MiRai pointed out earlier, if you added new key maps, then you need to make sure they are being disabled by the "Activate Maps" mapped key (which both activates and disables maps) or if you put any mapped keys into the Always On key map with hotkeys on them that are needed for your password, then they are in the wrong place because the Always On key map is excluded from the disable process (because you need some mapped keys to be available to re-enable key maps after you have disabled them!).

All that said, if you are configured correctly when you disable key maps and disable broadcasting, then under a standard configuration, this should then mean only a few combination of keys (e.g. SHIFT+ALT+M or SHIFT+ALT+R) are being routed through ISboxer and everything else is just direct input.

One problem that does come up often is if you have an ALTGr key, and you use ALTGr+2 to enter an @ symbol. If this is what is happening to you, then this means you probably did not tick the "I have an AltGr key" option, which means that ISboxer has configured CTRL+ALT+2 as the hotkey to swap to Slot2 on your character set, so it will be intercepted. You can change this by changing the option under your Character Set, Slots, 2, and changing the hotkey to switch to the window (or remove it, if you do not use it).

[MiRai]

Just as a reference, this was resolved in another thread:

viewtopic.php?f=14&t=6923