Issue with connecting to SQL Server 2017 for Linux
up vote
-1
down vote
favorite
I have installed SQL Server 2017 on Linux Ubuntu together with SQL Command Line Tools.
Instantly after setting up and normal configuration I am unable to connect to it using the command line tools.
I am getting the following error:
How can I fix this issue?
sql-server linux
add a comment |
up vote
-1
down vote
favorite
I have installed SQL Server 2017 on Linux Ubuntu together with SQL Command Line Tools.
Instantly after setting up and normal configuration I am unable to connect to it using the command line tools.
I am getting the following error:
How can I fix this issue?
sql-server linux
add a comment |
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
I have installed SQL Server 2017 on Linux Ubuntu together with SQL Command Line Tools.
Instantly after setting up and normal configuration I am unable to connect to it using the command line tools.
I am getting the following error:
How can I fix this issue?
sql-server linux
I have installed SQL Server 2017 on Linux Ubuntu together with SQL Command Line Tools.
Instantly after setting up and normal configuration I am unable to connect to it using the command line tools.
I am getting the following error:
How can I fix this issue?
sql-server linux
sql-server linux
asked Nov 11 at 7:41
Alex
129211
129211
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Look here:
Configure a Windows Firewall for Database Engine Access
Configure a Server to Listen on a Specific TCP Port
Specifically:
Can not connect to MS SQL from Ubuntu sqlcmd
client
The fix for letting the Ubuntu client connect was to set "Listen to
All" to No in the SQL Server Configuration Manager > SQL Server
Network Configuration > Protocols for [instance name]. And under IP
Address change 127.0.0.1 to the [ip] used to connect. Don't forget to
restart the SQL Server!
Other tip: check your firewall (or temporaly disable it for testing).
Also allow remote connections in SQL Server properties > Connections.
See above posts.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Look here:
Configure a Windows Firewall for Database Engine Access
Configure a Server to Listen on a Specific TCP Port
Specifically:
Can not connect to MS SQL from Ubuntu sqlcmd
client
The fix for letting the Ubuntu client connect was to set "Listen to
All" to No in the SQL Server Configuration Manager > SQL Server
Network Configuration > Protocols for [instance name]. And under IP
Address change 127.0.0.1 to the [ip] used to connect. Don't forget to
restart the SQL Server!
Other tip: check your firewall (or temporaly disable it for testing).
Also allow remote connections in SQL Server properties > Connections.
See above posts.
add a comment |
up vote
0
down vote
Look here:
Configure a Windows Firewall for Database Engine Access
Configure a Server to Listen on a Specific TCP Port
Specifically:
Can not connect to MS SQL from Ubuntu sqlcmd
client
The fix for letting the Ubuntu client connect was to set "Listen to
All" to No in the SQL Server Configuration Manager > SQL Server
Network Configuration > Protocols for [instance name]. And under IP
Address change 127.0.0.1 to the [ip] used to connect. Don't forget to
restart the SQL Server!
Other tip: check your firewall (or temporaly disable it for testing).
Also allow remote connections in SQL Server properties > Connections.
See above posts.
add a comment |
up vote
0
down vote
up vote
0
down vote
Look here:
Configure a Windows Firewall for Database Engine Access
Configure a Server to Listen on a Specific TCP Port
Specifically:
Can not connect to MS SQL from Ubuntu sqlcmd
client
The fix for letting the Ubuntu client connect was to set "Listen to
All" to No in the SQL Server Configuration Manager > SQL Server
Network Configuration > Protocols for [instance name]. And under IP
Address change 127.0.0.1 to the [ip] used to connect. Don't forget to
restart the SQL Server!
Other tip: check your firewall (or temporaly disable it for testing).
Also allow remote connections in SQL Server properties > Connections.
See above posts.
Look here:
Configure a Windows Firewall for Database Engine Access
Configure a Server to Listen on a Specific TCP Port
Specifically:
Can not connect to MS SQL from Ubuntu sqlcmd
client
The fix for letting the Ubuntu client connect was to set "Listen to
All" to No in the SQL Server Configuration Manager > SQL Server
Network Configuration > Protocols for [instance name]. And under IP
Address change 127.0.0.1 to the [ip] used to connect. Don't forget to
restart the SQL Server!
Other tip: check your firewall (or temporaly disable it for testing).
Also allow remote connections in SQL Server properties > Connections.
See above posts.
answered Nov 11 at 7:56
paulsm4
75.9k999122
75.9k999122
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53246761%2fissue-with-connecting-to-sql-server-2017-for-linux%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown