SSO with remote laptops

  • Thread starter Thread starter markaarnold
  • Start date Start date
M

markaarnold

I've noticed sometimes my Win7 laptop users will start 2x at home and the 2x client returns a bad username/password error. If they enter their username and password they can connect, but it's a pain because they don't have to in the office. It's as though SSO isn't able to authenticate them when remote. Is there a way to correct this?

Thanks
Mark
 
I thought the point of SSO was not to provided credentials at all. When user laptops are on the LAN 2x connects them straight away with no logon required.
 
What version are you using? So I take it they are VPNing prior to 2Xing. Maybe you have a Windows GPO setting that is interfering with this? You also stated "sometimes" which could mean the DC never authenticated with the laptop user prior to execution. Thus, it asks for a username and password. I would verify with your event logs and see if they are in fact authenticated prior to this issue. Bump up auditing on the laptops temporarily and check to see what's going on.
 
markaarnold said:
I thought the point of SSO was not to provided credentials at all. When user laptops are on the LAN 2x connects them straight away with no logon required.
Click to expand...

SSO uses the Windows Authentication credentials when you connect to a remote server. When user are at the office the y are first authentication with the domain controller (when you start the operating system), this information is used when you start an application or desktop and SSO is enabled thus you dont need to enter the credentials again).

If you are at home usually you dont have a domain controller and you are authenticated to the local users, so when you start a remote app with SSO the credentials will not match. If you are connecting from home, I suggest you disable SSO and preconfigure the username and password

cheers
 
Actually at home my users are doing one of two things to authenticate to the domain: using cached domain credentials or authenticating against the domain via Windows7 DirectAccess. In no case do my users authenticate against the local SAM database. I gather these must not provide the hooks SSO is looking for. Perhaps if 2x supported DirectAccess (requires IPv6) or could pull the credentials from the cached copy this would work.

Mark
 
You must log in or register to reply here.
Back
Top