Return
-
Title
Firewall causes "Login has timed out" (SQL state : HYT00) error when adding a SQL Server agent -
Description
Unable to add Foglight SQL Server agent to monitor SQL Server instance. It failed with exception "Login has timed out". It also failed with same error message when adding the instance using shortname, FQDN, or IP address.
The following error message was seen in the DBSS-Installer agent log:
ERROR [FglAM:IncomingMessage[5]-50] com.quest.qsi.fason.sqlserver.installer.validation.DBSSDbValidator - Validation failed: cannot establish a DB connection to host testing.prod.corp.com with profile MSSQLProfile{host='testing.prod.corp.com', instance= 'TEST', username='AD\foglight', authType= 'WINDOWS_CUSTOM', port= '8000' useNTLMv2= 'true', socketTimeout= '900', secureConnection= 'OFF' }com.quest.qsi.fason.framework.connections.common.exceptions.FrameworkException: Failed to establish a SQL-Server JDBC connection protocol to Host [testing.prod.corp.com\TEST], user account [AD\foglight] . Reason : [[Foglight][SQLServer JDBC Driver]Login has timed out.- Profile:MSSQLProfile{host='testing.prod.corp.com', instance= 'TEST', username='AD\foglight', authType= 'WINDOWS_CUSTOM', port= '8000' useNTLMv2= 'true', socketTimeout= '900', secureConnection= 'OFF' }]. . [SQL-Server Error Code = 0. SQL state : HYT00] -
Cause
There was no firewall's inbound rule to allow TCP connection in addition to UDP connection to port 8000 on SQL Server host testing.prod.corp.com. Connection between SQL Server hosts is established via UDP (such as SQL Server Management Studio). This could be the reason why UDL / JDBC connection test are failing as they rely on TCP. -
Resolution
Please verify in Firewall (launch wf.msc) to confirm if there are inbound rules to allow both UDP and TCP connections on the SQL Server port for the SQL Server host(s) in question.
Exclusions may also be set limiting access for specific users or processes (i.e. using IPTABLES).