February 15, 2019 at 5:25 pm
I installed my first instance of SQL server on Linux to experiment it.
The Linux is installed using Virtualbox on my windows 10 host. The edition I installed is developer edition of SQL server 2017.
The install is done, and I can connect to the database using sqlcmd on the local instance.
Now I want to try to connect remotely using SSMS or sqlcmd on my another workstation to the Linux SQL instance. They are on the same domain network. Any else I need to do and what is the Linux command. THanks
But I failed with below info:
TITLE: Connect to Server
------------------------------
Cannot connect to redhatSQL.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)
------------------------------
The network path was not found
------------------------------
BUTTONS:
OK
------------------------------
February 16, 2019 at 2:24 am
sqlfriends - Friday, February 15, 2019 5:25 PMI installed my first instance of SQL server on Linux to experiment it.
The Linux is installed using Virtualbox on my windows 10 host. The edition I installed is developer edition of SQL server 2017.
The install is done, and I can connect to the database using sqlcmd on the local instance.Now I want to try to connect remotely using SSMS or sqlcmd on my another workstation to the Linux SQL instance. They are on the same domain network. Any else I need to do and what is the Linux command. THanks
But I failed with below info:
TITLE: Connect to Server
------------------------------Cannot connect to redhatSQL.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)
------------------------------
The network path was not found
------------------------------
BUTTONS:OK
------------------------------
Quick question, have you configured the network settings for the VirtualBox instance?
😎
February 17, 2019 at 10:42 am
I just used the default, NAT. Then I changed to bridge. I am able to use sqlcmd in the red hat instance to connect a server on our network but not the other way around..
I am wondering if the client access through tcpip is enabled or not since I installed the developer edition.
Is there a way in the rehat sql instance to check tcpip enabled or Nottingham for network client access?
Thanks
February 18, 2019 at 11:38 am
Sorry above post I accidently used my old account when using cellphone. Ignore that.
-- But see below-----------------------
I just used the default, NAT. Then I changed to bridge. I am able to use sqlcmd in the red hat instance to connect a server on our network but not the other way around..
I am wondering if the client access through tcpip is enabled or not since I installed the developer edition.
Is there a way in the rehat sql instance to check tcpip enabled or Not for network client access?
I see in the mssql-conf file there is no setting about it.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply