mudfrog
asked on
SonicWALL 4200 RDP to TS Farm
Please help!
Currently there is an issue with our SonicWALL 4200 VPN appliance.
Its quite random but is causing major frustration.
The SonicWALL 4200 is configured with a TSFARM RDP - Java connection for all users who connect to the appliance.
There is a problem where the user will connect to the SonicWALL VPN fine then there is a global TSFARM - RDP using Java (3 load balanced Remote Desktop Server all running Windows Server 2008).
If the user logs in with there Active Directory account and doesn't get connected straight away, it comes up with a second login screen asking to authenticate with there AD credentials again. Password only as Username already filled out.
The problem is that if they do get the second login prompt something odd is happening with the Shift and Caps lock keys so it randomly thinks the caps lock is on when the shift key is pressed.
Now this causes issues with the password due to it using complexity with uppercase, lowercase and numerics required.
It then fails to login to the server because of this issue.
But on random occasions it will login fine with the initial RDP connection and will then work OK.
We thought it was perhaps Java being funny and have reinstalled it on various machines.
It's really frustrating as the Directors are the main users of it.
Currently I am asking them to keep logging off the RDP session if they get the second login happen.
Then keep trying until the first login is successful.
Any ideas with this weird caps lock/shift key issue would be appreciated.
Thanks,
Rich
Currently there is an issue with our SonicWALL 4200 VPN appliance.
Its quite random but is causing major frustration.
The SonicWALL 4200 is configured with a TSFARM RDP - Java connection for all users who connect to the appliance.
There is a problem where the user will connect to the SonicWALL VPN fine then there is a global TSFARM - RDP using Java (3 load balanced Remote Desktop Server all running Windows Server 2008).
If the user logs in with there Active Directory account and doesn't get connected straight away, it comes up with a second login screen asking to authenticate with there AD credentials again. Password only as Username already filled out.
The problem is that if they do get the second login prompt something odd is happening with the Shift and Caps lock keys so it randomly thinks the caps lock is on when the shift key is pressed.
Now this causes issues with the password due to it using complexity with uppercase, lowercase and numerics required.
It then fails to login to the server because of this issue.
But on random occasions it will login fine with the initial RDP connection and will then work OK.
We thought it was perhaps Java being funny and have reinstalled it on various machines.
It's really frustrating as the Directors are the main users of it.
Currently I am asking them to keep logging off the RDP session if they get the second login happen.
Then keep trying until the first login is successful.
Any ideas with this weird caps lock/shift key issue would be appreciated.
Thanks,
Rich
ASKER
It seems to be worse the more complex the password is with the second prompt.
If you have various capital letters and the more you have to press the shift button seems to be an issue.
Random is an understatement.
If you have various capital letters and the more you have to press the shift button seems to be an issue.
Random is an understatement.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I think I may try and log a call with Dell who have taken over the support of these SonicWall appliances.
have you check you session persistence type? I.E stateful and stateless session must be handled differently.
ASKER
I can't see the session persistence setting on the 4200.
I'm not sure it has that feature tbh.
I'm not sure it has that feature tbh.
I'm not that familiar with the SonicWALL 4200 but from what you discribed this issue really does sound like a persistance issue.
ASKER
On initial connection I connected to TER-001 server.
I then authenticated with my AD account and it then prompted for a second login but put me onto TER-002 server. This is where the issue with the caps lock and shift key causes issues.
I then tried it and initially got logged onto TER-003. It then prompted for a second login but had redirected my session to the TER-001 server.
Ahhhh!