Network Management

Cannot connect to a SQL server using Windows authentication when specifying a machine name

When you select a machine name in your Windows credentials for your SQL server, you receive a Connection Timeout Expired error. This usually occurs when your Orion server and your SQL server are on different subnets.

First published date

10/12/2018 8:54 PM

Last published date

4/1/2019 7:47 PM

Overview

When specifying a machine name in your Windows credentials for your SQL server, such as hostname\administrator, you may receive an error like the following:

Can not connect to the SQL Server. The original error is: Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in time. The duration spent while attempting to connect to this server was - [Pre-Login] initialization = 18066; handshake = 14340;

Product section

Network Performance Monitor

Cause

This generally occurs when your Orion server and SQL server are placed on different subnets and the SQL server hostname cannot be resolved by the Orion server.

Resolution

You can resolve this issue in multiple ways.

Resolve this locally to the Orion server

You will need to repeat one or both methods on any other Orion servers you create.

Disable NetBIOS over TCP/IP. See https://technet.microsoft.com/en-us/library/cc940063.aspx for more information (© 2019 Mircrosoft, available at https://technet.microsoft.com, obtained on January 21, 2019).
Add an entry to your hosts file to map the IP address of your SQL server to the machine name you used.

Resolve this for multiple Orion servers

Create a DNS record for the SQL server's machine name.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.