Profile Picture

Remote SQL Data Store Test Connection failed

Posted By neo 4 Years Ago
Message
neo
Supreme Being (3,749 reputation)Supreme Being (3,749 reputation)Supreme Being (3,749 reputation)Supreme Being (3,749 reputation)Supreme Being (3,749 reputation)Supreme Being (3,749 reputation)Supreme Being (3,749 reputation)Supreme Being (3,749 reputation)Supreme Being (3,749 reputation)
Posted Tuesday July 09 2013
I've encountered a remote sql connection issue.

The database server is on a remote machine with default tcp port 1433.
When turn off the firewall on remote machine, RightEdge SQL Data Store Test connection always successful.
When turn on the firewall on remote machine (but allow SQL Server port to pass), RightEdge sometimes successful, sometimes failed, depending on the sequence of actions.
If RE test connection is first run against firewall-on, it always fails.
If RE test connection first run against firewall-off, so that it was successful at the first time; then turn on the firewall, and test connection run again, it will be success.

Just to make sure, the management studio on RE machine always can connect to the remote database, irregardless of firewall on or off, which shows that the firewall configuration seems to be correct.
And RE on the database server using the same SQL Store configuration always success with its firewall on/off.

http://www.rightedgesystems.com/forums/Topic10090-7-1.aspx?Highlight=connection+failed
seems to provide few things to check, but if either those fails, the ssms shouldn't be always be able to connect, right?

RE's failed message is:
Connection failed!
A network-related or instance-specific error ... provider: SQL Network Interface, error: 26 - Error Locating Server/Instance Specificed)

Edited: Tuesday July 09 2013 by neoaries
neo
Supreme Being (3,749 reputation)Supreme Being (3,749 reputation)Supreme Being (3,749 reputation)Supreme Being (3,749 reputation)Supreme Being (3,749 reputation)Supreme Being (3,749 reputation)Supreme Being (3,749 reputation)Supreme Being (3,749 reputation)Supreme Being (3,749 reputation)
Posted Wednesday July 10 2013
This issue is solved by specifying port in the server address. Perhaps it's the windows firewall's issue, as ssms seems to have a similar problem.


Similar Topics


Reading This Topic


2005-2017 © RightEdge Systems