Hello Seniors, Greetings!! Hope all is well.

I am trying to create Data Source for "MS SQL Server" for Guardium VA, However upon testing data source, I am getting "time out" error as mentioned below. Firewall Ports and User\pwd is okay. Can anyone suggest on this error OR Did anyone face such error in their Env, Can please suggest me. thanks in advance. 

Could not connect to: 'jdbc:guardium:sqlserver://X.X.X.X:1435;CryptoProtocolVersion=TLSv1,TLSv1.1,TLSv1.2' for user: "VA USER". DataSourceConnectException: Could not connect to: 'X.X.X.X:1435' for user: 'VA USER' within timeout period of: 60 seconds. TimeoutException: null."

Hello Akash,

can you check the PORT of MSSQL , by default it should be 1433, unless they have changed to 1435 ,

------------------------------
MAHESHKUMAR M
------------------------------

Original Message:
Sent: 4/27/2022 7:08:00 AM
From: MAHESHKUMAR M
Subject: RE: Guardium VA - Getting Time Out Error while Testing the Data Source

Hello Akash,

can you check the PORT of MSSQL , by default it should be 1433, unless they have changed to 1435 ,

Hello Akash,

Is this first time you are connecting to this SQLServer instance? 
Can you try telnet to this port 1435 from guardian ?

Thank you

------------------------------
MAHESHKUMAR M
------------------------------

Original Message:
Sent: Wed April 27, 2022 07:29 AM
From: Akashkumar Parmar
Subject: Guardium VA - Getting Time Out Error while Testing the Data Source

Hello Mahesh,

Thank you for the response. Yes, the Port is correct it is user defined not the default one. Let me know if you know any other cause for this. thank you.

 

 

------------------------------
Akashkumar Parmar
------------------------------

Original Message:
Sent: 4/27/2022 7:08:00 AM
From: MAHESHKUMAR M
Subject: RE: Guardium VA - Getting Time Out Error while Testing the Data Source

Hello Akash,

can you check the PORT of MSSQL , by default it should be 1433, unless they have changed to 1435 ,

------------------------------
MAHESHKUMAR M
------------------------------

Original Message:
Sent: 4/28/2022 4:42:00 AM
From: MAHESHKUMAR M
Subject: RE: Guardium VA - Getting Time Out Error while Testing the Data Source

Hello Akash,

Is this first time you are connecting to this SQLServer instance? 
Can you try telnet to this port 1435 from guardian ?

Thank you

There can be multiple reasons you receive connection timeout.  The obvious is ensuring SQL services are running and that you can connect to the SQL instance from something like SQL Server Management Studio (SSMS).  First I'd start with ensuring the IP/Port/Service Name are correct.  This is easy code to use to identify the IP and port.  You'll want to be sure the FQDN resolves to the IP from the script below.

SELECT local_net_address,
local_tcp_Port,
count(*) as connections
FROM sys.dm_exec_connections
WHERE local_tcp_port is not null
GROUP BY local_net_address, local_tcp_Port

You would use service name instead of port if you're using named instances in MS SQL.

Also validate that your connection properties are correct.  We use the following.  You can try adding only AuthenticationMethod then also try adding encryptionMethod and validateServerCertificate.  Consider changing validateservercertificate to false.

Here is what our current connection properties are:
AuthenticationMethod=ntlm2java;encryptionMethod=SSL;validateServerCertificate=true

You should only be using the datadirect driver and not the jTDS driver that is manually uploaded.  The jTDS driver was deprecated years ago and I don't think it supports some of the latest encryption protocols.  I believe IBM will be replacing the jTDS MS SQL driver upload for the MS SQL jdbc driver in the future.

The username if using the datadirect driver you can use the 'domainname\username'.  Or you can add domain=domainname to the connection properties.

------------------------------
Walter York
------------------------------

Original Message:
Sent: Wed April 27, 2022 07:08 AM
From: MAHESHKUMAR M
Subject: Guardium VA - Getting Time Out Error while Testing the Data Source

Hello Akash,

can you check the PORT of MSSQL , by default it should be 1433, unless they have changed to 1435 ,

------------------------------
MAHESHKUMAR M
------------------------------

Original Message:
Sent: 4/28/2022 4:15:00 PM
From: Walter York
Subject: RE: Guardium VA - Getting Time Out Error while Testing the Data Source

There can be multiple reasons you receive connection timeout.  The obvious is ensuring SQL services are running and that you can connect to the SQL instance from something like SQL Server Management Studio (SSMS).  First I'd start with ensuring the IP/Port/Service Name are correct.  This is easy code to use to identify the IP and port.  You'll want to be sure the FQDN resolves to the IP from the script below.

SELECT local_net_address,
local_tcp_Port,
count(*) as connections
FROM sys.dm_exec_connections
WHERE local_tcp_port is not null
GROUP BY local_net_address, local_tcp_Port

You would use service name instead of port if you're using named instances in MS SQL.

Also validate that your connection properties are correct.  We use the following.  You can try adding only AuthenticationMethod then also try adding encryptionMethod and validateServerCertificate.  Consider changing validateservercertificate to false.

Here is what our current connection properties are:
AuthenticationMethod=ntlm2java;encryptionMethod=SSL;validateServerCertificate=true

You should only be using the datadirect driver and not the jTDS driver that is manually uploaded.  The jTDS driver was deprecated years ago and I don't think it supports some of the latest encryption protocols.  I believe IBM will be replacing the jTDS MS SQL driver upload for the MS SQL jdbc driver in the future.

The username if using the datadirect driver you can use the 'domainname\username'.  Or you can add domain=domainname to the connection properties.