Join us at Gartner SEC London and discover how LevelBlue can help you secure what’s next. Learn More
Access immediate incident response support, available 24/7
WTS is a Window Terminal Server process that normally runs on all windows computer. The latest version (2.0.10) of the Trustwave Authenticator needs that process (WTS) to be active and running and if you look in the Authenticator.log on the computer you will notice the authenticator trying to check if the WTS is registered and active. On computer a where WTS is disabled you will notice the following entries:
L2 2012-10-10 10:53:00 3584 Startup: Init() L1 2012-10-10 10:53:00 3584 AppShutdown: AppShutdown::Initialize setting up shop... L1 2012-10-10 10:53:00 3584 Startup: registering for WTS notifications. L1 2012-10-10 10:53:00 3584 Startup: registering for WTS notifications failed. Retrying (attempt 1). L1 2012-10-10 10:53:01 3584 Startup: registering for WTS notifications failed. Retrying (attempt 2). L1 2012-10-10 10:53:02 3584 Startup: registering for WTS notifications failed. Retrying (attempt 3). L1 2012-10-10 10:53:03 3584 Startup: registering for WTS notifications failed. Retrying (attempt 4). L1 2012-10-10 10:53:04 3584 Startup: registering for WTS notifications failed. Retrying (attempt 5). If you are using the 2.0.4 authenticator or a prior version of the authenticator disabling the WTS on the computer would not impact the authenticator from working but if you are using the later version of the authenticator such as the 2.0.10 then you might see the logs above because the authenticator needs to check if the WTS is active and running. If it is not running or its disabled that would cause the authenticator to fail.
To contact LevelBlue about this article or to request support: