Follow these steps:

1. To clear the way for a problem user account to log on to Windows:
   
   • Verify "Log on locally" rights
   • Go to Windows/Control Panel/Administrative Tools
   • Under Local Security Policy/Local Policies/Audit Policy: turn on audit for "Audit account logon events" and "Audit logon events" (both Success and Failure)
   • Log on again and it will fail but now the reason for the failure will be recorded
   • Check Control Panel/Administrative Tools/Event Viewer under the Security section for the reason
2. If you are successful in step 1 and are now able to log on to Windows:
   
   • Check that the problem user account is also in the Aspera User Manager
   • Run sshd in debug mode:
     
     • Stop the sshd service
     • Open a command window and run: "C:\Program Files\Aspera\FASP\usr\sbin\sshd.exe"
     • Login again and check the output of the sshd server run in console mode

   Note: Aspera will install an SSH service for user authentication and setup of transfer sessions. On Windows 2003 Server the SSH service cannot run as the regular SYSTEM account as services generally do because of security restrictions.

   You must create a user account to run the SSH service: if Aspera's clients will need to access network resources (such as transferring files to or from a Windows share), create a domain account that has proper access to these resources; otherwise, you can create a local account.

   You must create this user sshdproc or sshdproc@lab.example.com before the installer can proceed. This account will be made a member of the local Administrators group and granted the following rights:

   • Adjust memory quotas
   • Create a token
   • Log on as a service
   • Replace a process level token

   Further Note: you can later change the user account under which the SSH service runs. From the Services panel / OpenSSH Service / Log On tab. The new user account must be a member of the local Administrators group or the service will not start.