NTLM: automatic logon sometimes fails

Answer: For SMB signing the traffic to the authentication server is coded by a login name and a password (the first one that tries to login). Other users have an other login / password combination and are not authenticated: logging in is denied. After a while the first session seems to take 1 minute (or more) and then a new encryption session is created. The same story can happen, but when only 1 person has to login additionally, it now works correctly. To prevent this situation from happening, you can process the following work-around. The application server needs to be stopped before changes are made to the configuration. Open the file topdesk.conf in the installation folder. Look up the line starting with: # Java Additional Parameters. Once you have found this line, please add the following: wrapper.java.additional.1=-Djcifs.smb.client.domain=your domain wrapper.java.additional.2=-Djcifs.smb.client.username=a user that can log in wrapper.java.additional.3=-Djcifs.smb.client.password=the password of this user If you are already using another additional parameter, then you will need to change the numbering to .2, .3 and .4. After saving the file the applicationserver can be restarted. If you still use version 4.1 or lower, please do the following: The application server needs to be stopped before changes are made to the configuration. Open the file applicationserver.ini in the installation folder. The following information (including a login name and password for the domain) has to be in the applicationserver.ini (additional VM_OPTIONS): -Djcifs.smb.client.domain=your domain -Djcifs.smb.client.username=an existing user name -Djcifs.smb.client.password=corresponding password These lines should follow each other, only having an interspace between them. The account could be a dummy AD account, it does not have to be a real account. After this the applicationserver can be restarted.