-
Notifications
You must be signed in to change notification settings - Fork 191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to connect to server on custom port #163
Comments
This works for me:
You should make sure to prefix with |
I have the same problem.
The above command gives the following error message.
The standard
I also tried what @chriswolf-nrg suggests by adding a protocol prefix
The above command gives the same error message as that of first |
The version that works for me is |
My |
I have the same issue with |
It works for me with that comma separation (even without double quotes). The issue I had is that a comma separator is not intuitive. I first assumed there was some other flag ( I think this needs to be documented. PR #522 does that. (But it hasn't been merged, and I don't know why.) |
Hi,
I`m having problems with connecting to SQL Server On Linux using mssql-cli using Ubuntu 16.04.
This is not related to firewall etc, as connection from same machine using mssql tool works fine.
Steps to reproduce:
mssql-cli -S HOST,PORT
Expected result:
Successful connection
Actual result:
Connection did not succeed. Error message: Connection Timeout Expired. The timeout period elapsed during the post-login phase. The connection could have timed out while waiting for server to complete the login process and respond; Or it could have timed out while attempting to create multiple active connections. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=111; handshake=363; [Login] initialization=4; authentication=8; [Post-Login] complete=14033;
The text was updated successfully, but these errors were encountered: