Troubleshooting DataConnector

First try to ping the server, if the ping is successfull go to step 2.

Step 1. (Ping failed) Opening a Port in the Firewall

By default, the Windows firewall is turned on and will block connections from another computer. To connect using TCP/IP from another computer, on the SQL Server computer you must configure the firewall to allow connections to the TCP port used by the Database Engine. The default instance is listening on TCP port 1433, by default. If you have named instances or if you changed the default instance port, the SQL Server TCP port may be listening on another port. See Get the SQL Server instance TCP port.

If you are connecting to a named instance or a port other than TCP port 1433, you must also open the UDP port 1434 for the SQL Server Browser service. For step by step instruction on opening a port in the Windows firewall, see Configure a Windows Firewall for Database Engine Access.

This error usually means that the SQL Server computer can't be found or that the TCP port number is either not known, or is not the correct port number, or is blocked by a firewall.


Step 2. (Ping successfull) Can't reach SQL server with DataConnector.

  1. Open SQL Server Configuration Manager.

  2. Using Configuration Manager, in the left pane expand SQL Server Network Configuration, and then select the instance of SQL Server that you want to connect to. The right-pane lists the connection protocols available. Shared Memory is normally enabled. It can only be used from the same computer, so most installations leave Shared Memory enabled. To connect to SQL Server from another computer, you normally use TCP/IP. If TCP/IP is not enabled, right-click TCP/IP, and then click Enable.

  3. If you changed the enabled setting for any protocol, restart the Database Engine. In the left pane select SQL Server Services. In the right-pane, right-click the instance of the Database Engine, and then click Restart.

Using Telnet to Test Open Ports

Enabling telnet client through Command Prompt:

If you want to enable Telnet via the command line, open the Command Prompt with elevated privileges (“as Administrator”) and run the following command:

Dism /Online /Enable-feature /FeatureName:TelnetClient

One of the biggest perks of Telnet is with a simple command you can test whether a port is open. Issuing the Telnet command telnet [domainname or ip] [port] will allow you to test connectivity to a remote host on the given port. 

Issue the following command in the Command Prompt:

telnet [domain name or ip] [port]

Put the IP address or domain name of the server you’re trying to connect to in place of [domain name or ip], and replace the second brackets with the port number on the remote machine, connection to which you want to test.

For example, to verify connection to on port 25, issue the command:

telnet 25