Closed cviorel closed 4 years ago
Duplicate of #10 and #15 You are probably using an old version, please have a look under the tab releases in this repo.
Indeed, my version was not the latest one. After upgrading, I can confirm it's working as expected.
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>