Everything on the server seems to be set up correctly, I am not doing any filtering. On the client I am receiving error message 'Invalid username/password'. All of the settings on the client seem to match the server. I have attempted several user/password combinations, including administrator, but continue to get same error message. Would appreciate any suggestions.
Hi there, Make sure what domain it being used when authentication is done. In the "connection", "publishing agent" settings you have the domain settings. If "Use client domain if specified" is on the domain specified by the user is used. If A specific domain is used is set make sure it is correct, press the ... button and it should set it correctly. All trusted domains will authenticate with any trusted domain that has that user. I suggest to use a CORRECT specific domain. Nixu
Is the machine where the application server is installed, joined with a domain or with a workgroup? Nixu
The server is joined to a domain. The server is currently running W2K, Citrix Metaframe. The server is currently hosting all of our published applications via Citrix. Everything on the Citrix side is working fine.
Make sure that the Gateway settings are correct: "Console->Connection settings->Client Gateway->Advanced->2x Publishing Agent" is the same as "Console->Connection settings->Publishing agent ->2x publishing agent port". Nixu
I have the same issue. The problem exists when I fire up the application and enter my credentials. I get prompted with an Invalid Username/Password error message. I am on the domain. The correct domain is specified. The advanced client gateway settings look correct.
I have seen this non-discript error when the user account you are trying to contact the publishing agent with is locked out or if an password change is needed on the account. It will not show any published applications and will give the invalid username/password error. If you go to a web page or launch the app from a pre-existing 2XA shortcut, I could then see that a password had been changed or the account was locked out because the user was making a connection to the terminal server. Maybe there is a way that 2X can provide some better messaging in these scenerios and maybe find a way to allow remediation of the problems.