Network Connection Test

If you are having problems connecting a PC to your server, you can do a network test that will bypass ROBOTILL. That will allow you to rule out any issues with the network or SQL Server.

Testing using PowerShell

On the PC you are trying to connect to the server, in the Windows search bar type 'PowerShell' and press ENTER. Windows PowerShell will open.
At the prompt, type: test-netconnection -computername [SERVER NAME] -port [PORT NUMBER]

• Replace [SERVER NAME] with your server name. See where to find your server name
• Replace [PORT NUMBER] with the port number your SQL server is using. If you haven't changed the SQL port yet, you should use the default port number: 1433

See the example below where our server name is 'DEMIPC' and we are using the default SQL port number.

Successful Test

A successful test will return a result where it says TcpTestSucceeded: True

That means there is no problem with your network and the PC managed to connect to the SQL port where SQL server is listening. If you still have connection problems it will not be a network issue but some other problem like the wrong SQL Server password.

Troubleshooting a failed test

If you get 'PingSucceeded: False it could be one of the following issues:

• You are using the wrong server name.
• The computers are not connected to the same network.
• The networks are not set to private.
• Network discovery and/or file sharing is not on.
• There is a problem with the network.

If you get PingSucceeded: True but you get TcpTestSucceeded: False it means the server is on the network but the port is not accessible. It could be one of the following issue:

• There is not an inbound rule for this port in Windows Firewall on the server PC. If ROBOTILL installed SQL server for you the port rule would have been added automatically. If you installed SQL server directly or if you changed the port number, you have to add the rule to Windows Firewall on the server PC.
• A third party firewall that comes with some Anti-Virus software is blocking the port. You will need to add a rule for this port in the software you are using for a firewall on the server PC.
• There is a problem with SQL server - the SQL service is not running, TCP/IP is not enabled or it is not configured to listen to the port number you specified.
• If it is none of the above, it can be that your router software is blocking the port and you need to open the port in your network router's configuration.