Username modified by 2X after update

After update to Client7.xx users are having trouble connecting. The username has @xxx where xxx = domain name added. e.g. gazguru@blahblah instead of just gazguru. I am not using SSO.
I have un-installed the client and re-installed but it has not helped.
The properties for the connection do not show the addition but the properties for the desktop shortcut do.
If I remove the @blahblah it works but as soon as I run the 2X program first it reconfigures the desktop shortcut.
Server version is 6.2
Can anyone help?

 

Hi there,

What is the problem with the username having the domain appended to it?

Nixu

 

domain name appended to username

The user is logging into a w2K Terminal Server in an NT domain. This has worked well for a couple of years but it will not accept user@xxx format.
When a shortcut to the program ie. MYOB is activated it errors and presents the RDP login screen. The user has to remove the @xxx part and then enter their password.
This may be acceptable for other networks but it does not work well for us.

 

URGENT URGENT

This is no longer just an annoyance. It is now an operational issue.
PLEASE ANSWER ASAP!!

 

Hi,
V7 2X Client is in Beta and should not be used in lice environnment.
Just specify domain you want to use in 2X Console and disable "Use client domain if specified"

 

Thanks for the help

Thanks for the help.
Version 6.2 does the same thing. Your advice about changing console settings worked.
What problems will I face with V7? SHould I un-install it and reapply V6?
V7 was installed on one machine only after the problem surfaced in V6.2. I assumed that the update through the client would be the same as the download version and thought I was reapplying the same version.

 

Re: Thanks for the help

same option is on 7, and I am sure something will be done for this before th release

 

Recommend to downgrade to V6.2
As I said, V7 is Beta and meant for other version of 2X AS.

 

Problem not corrected

Unfortunately I spoke too soon. I followed the fix offered but it has made no difference. I was tricked by the fact that once authenticated on the server, the authentication persists for some time and subsequent connections work without the problem.
My other clients are having the same problem. They are all 6.2.

Update,
I spoke too soon again.
It seems that you have to remove any references to the domain in the client as well. This has fixed it for the moment, time will tell.