Authentication Failure

[south_leys]

After upgrading to 4.1 when loading the program up random machines will say authentication failure - incorrect connection password. If we then click connect the machines connect with no problems.

We didn't have this problem in version 4.0 and earlier.

[Andy]

Hi

Can you confirm if you are using the 'Auto Connect to found clients' option?

If so, does this problem occur if you switch this option off and just connect manually after the program has found the clients.

This might help us find out what could be causing this.

Many thanks,

Andy

[south_leys]

Yes we are using the auto connect to found clients option.

The problem still occurs if we switch this option off and connect manually.

[Martin Marcil]

Hi,

I got the same problem here.

5 machines out of 30 can't get connected.
No password have been entered.
I leave both fields blank.
Autoconnect is on.

Authentification failure
Unable to connect to host. (10061)
Invalid connection password

I uninstalled AB stuff. Manually deleted the folders.
Manually cleaned the registry.

Nothing works.

What's next?

Thx.

Martin

[Martin Marcil]

Just tried turning automatic connecting off and tried to connect manually.

didn't change anything.
didn't work.

Ciao,

Martin

[Aileen]

We have not made any changes at all between version 4.0 and 4.2 to the part of the program which covers connection passwords. Here are some things to look at if you cannot connect to a few machines.

1. If your teachers have access to administrative rights in AB Tutor Control, could they have inadvertently changed the password on just a few selected machines? We would always recommend limiting access rights.

2. Have you set connection passwords on all your client machines? Is it possible that someone (a student?) may have been able to connect to a client without a password and to change it to a password of their own choosing? We cannot emphasise how important it is to set connection passwords on clients for security reasons.

3. Is there a chance that someone may have clicked on the 'Save and Apply to Selected Clients' when they meant to select 'Save?' Or could a new connection password have been transmitted to all selected clients - when the few suspect machines were not connected?

4. Have you set up classroom group passwords? Could these have been somehow corrupted, possibly during the software update? It is worth trying deleting temporarily any group passwords set and seeing if you are now able to connect. (See menu - Groups, Manage Groups; then select each classroom in turn and delete ||||||| from the 'classroom connection password box' and click on OK). Could someone have intended to set up a classroom group password, and have instead transmitted a new connection password to a subset of computers? Also, is it possible that two administrators might have set different classroom passwords for the same machines - the last classroom password set will override the earlier one.

5. Did you try to solve the problem by re-installing AB Tutor Control without setting a new connection password at installation? This will not work, because any fresh installation of AB Tutor Client will always pick up the previously set connection password and use that as default unless a new (non-blank) connection password is set at install.

6. If you really cannot find the connection password set on the rogue machines, the only solution is to re-install AB Tutor Client on those machines, setting your non-blank chosen connection password at installation. Unfortunately, by design, there is no way to 'see' the password set on clients.

Let me know if none of the above suggestions help.

Aileen

[Martin Marcil]

Nothing worked.

Anything else?

What ports is using ABTutor?

Where the password in? Registry? CMOS or BIOS?

Probably Registry.

Is it possible to let me know where?

Also, ABTutor just told me to validate the license within the next 7 days. What is this? I got a valid version of ABTutor!

Thx.

Martin

[south_leys]

The passwords are not the issue as if they fail to connect on startup we can then click connect again and they connect fine.