I have Ubuntu installed on my laptop, and I'm developing a web application with java, using eclipse, and I want to connect, with sql server. To do this I have installed sql server 2012 in my virtual machine(Virtual box).
I have installed windows 7. I'm using Bridged Adapter setting, to receive ip from dhcp.
I have tested connection with ping command and is running successful, but when I run my application I have this error: Unknown server host name 'PEACH-PC'
the PEACH-PC is the
have you added Peach-PC variable in the etc/hosts file? that may be the case. If not add the ip and the variable there.
Related
How do I enable remote access to my mongo db server running on my own personal windows machine? I’ve read that I need to bind my IP address to 0.0.0.0 in a config file. I found some instructions online for Linux. But I am running a windows server. Any tips?
I'm currently having a Macbook Pro M1 as my development machine, running Docker on Mac for my containerised applications and Windows 11 VM using Parallels as my development environment. In this Windows VM lies the SQL Server database that Docker needs to connect to. To those who may be unaware, no, the M1 chip doesn't support nested virtualisation.
Therein lies my question: how do I establish a connection from Docker through the MacOS host to SQL Server in Windows VM?
Points that I'm aware of:
There is no direct connection between Docker and Windows
Docker has its own subnet assigned by default e.g. 192.168.65.0/24
Parallels uses shared network by default, which places the Windows VM in an invisible subnet e.g. 10.211.55.x
Parallels support bridged network but ideally would like the corporate VPN to just be in the MacOS host
Inside Mac's host file, an entry exists to resolve the private IP of the Windows VM to a hostname e.g. 10.211.55.x windows-11.shared
Docker uses a specific hostname to establish a connection to the MacOS host i.e. host.docker.internal
SQL Server is configured to accept TCP connections through port 1433
Using the connection string Server=windows-11.shared;Database=xxx;User ID=xxx;Password=xxx throws the "Server not found" error because no direct connection
Advice greatly appreciated!
I want to ask you about a problem.
I have developed a windows application that uses a SQL Server database with SQL Server authentication (with a username and password) to log in.
The database is located on a local server which uses the same network as my company computers.
Now I have published the application and installed it on my computer (where I developed it and in which I also have the SQL server installed).
I also installed the application on the computers of some colleagues who do not have any program installed (they do not have Visual Studio or SQL Server installed).
When I try to log in to the application from my computer everything works fine.
(I can enter in application and database communication works very well).
But when I try to log in to the application from other computers (with the same user which I used on my computer before), it does not work.
I get this error:
Named pipes provider error 40 could not open a connection to SQL Server
I did these steps on the server where the application is located as:
Enable TCP / IP in SQL Server Configuration
Open Port in Windows Firewall 1433
Allow remote connections to this server
Can you help me with any suggestions?
I would try creating a ODBC connection to your machine from the client as a quick test - using the ODBC control panel. If that works, then check your connection string in the app. Maybe it's configured as a local connection? (The connection string would be my first guess.)
There are so many things that can be wrong that it a guessing game. This link might help.
https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/troubleshoot-connecting-to-the-sql-server-database-engine?view=sql-server-ver15
I just installed MSSQL on debian 8 (64bit) fallowing this steps on this link. It installs ok, no errors, I can also use sqsh -S localhost -U sa and it connects and I can execute SQL commands normaly. I choose to install SQLExpress license, so I suppose that instance name is "\SQLEXPRESS"
I install MSSQL server on my "mini computer" that is connected to my router (which sets DHCP). With other devices connected to this router I can ping this "mini computer" and also in other side, from "mini computer" I can ping other devices. All devices are in Workgroup, and not in Domain. Also I can connect with SSL to this "mini computer".
But If I want to connect from my Windows computer from Microsoft SQL Server Management Studio, I get error, that I cannot connect to this "mini computer": The parameter is incorrect! What I am doing wrong, is it possible to make connection like this, or I have to have domain server?
when you get a message :
the connection is established, but an existing connection was forcibly closed by the remote server
that means the connection is correct but this error could happen sometime for windows version, try it with other windows version and other SSMS version.
I'm not able to connect SQL Server hosted in Ubuntu 16.04 using my program, I believe its because the TCP/IP is disabled for the instance I try to connect (Protocols for SQLEXPRESS under SQL Server network configuration).
How I'm sure because I tried to connect my program to SQL Server that hosted in Windows and it able to connect.
Example my instance name is SQLEXPRESS, so I'm trying to connect through SSMS by using IP Adress\SQLEXPRESS and it fails. But I am able to connect to the SQL if I use IP address only as the server name.
I tried to search about sqlcmd for enable the tcp/ip but all of them just show the guide to change the ports.
So, how can I enable tcp/ip connection for ip\SQLEXPRESS instance in Ubuntu 16.04?
picture below just an example on enabling tcp/ip for the sql instance in windows
I believe the reason why this doesn't work on linux is because it doesn't have a SQL Server Browser application that Windows has available. This application redirects the requests to 1433 to whatever random port it's listening to currently -- this is why it will only connect when the port is specified. In my case this stinks because I'm having to work around an ancient application that we don't have the source code for. I'm thinking about writing a little application that will redirect the default traffic to the correct port for linux msssql.