Connection string with non-default port are failing
Closed this issue · 2 comments
cviorel commented
When defining a connection string with a non-default tcp port, the connection fails.
e.g. 192.168.1.250,10002
Expected Behavior
the connection to the database should be done on port 10002 instead of the default 1433
Current Behavior
Possible Solution
Steps to Reproduce
connect to a sqlinstance on a non-standard tcp port
e.g.
192.168.1.250,10002
<fqdn>,<tcp_port>
R0tenur commented
cviorel commented
Indeed, my version was not the latest one.
After upgrading, I can confirm it's working as expected.