When I try to access a named instance of Microsoft SQL server 2008 R2 SP2 on the local network, I have no problem. But when access it outside office from the internet, I can not connect to the database server.
It send back the "famous" following error:
A network-related or instance-specific error occured while establishing a connection to SQL Server.
When I try to connect to a named instance in a SQL SERVER hosted in a azure VM I get this message:
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.
I've just built a virtual SQL Server 2 node cluster using VMWare workstation.
I have tried disabling firing wall and checked sqlbrowser is started but for some reason I cannnot connect to my datbase... called server_name\sqlexpress..
I have a virtual machine and a full scale MS SQL Server 2008 R2 running on it... and I have several other vm running sqlexpress. they run fine and I can connect to them using sqlexpress... but when i try to access from sqlserver...
I'm trying to connect to my remote mssql server for my GunZ private server, but for some reason i get the following error
Cannot connect to 94.xx.xx.xx.
ADDITIONAL INFORMATION:
A connection was successfully established with the server, but then an error occurred during the login process.
I'm trying to diagnose an issue at a customer site.
Until yesterday evening, I was able to connect to my server from my local machine. Now, I get the following error:
A connection was successfully established with the server, but then an error occurred during the pre-login handshake.
I am trying to connect to a remote MS SQL Server 2008 SP3 x86 Instance using it's name.
At the first glance all seems to work well (e.g.
We have ran into this error, trying to connect to WSUS server:
Can't connect to SQL server may not be running
Please verify that SQL server is running and configured correctly on
the server. Contact your network administrator if the problem
persists.
The only thing that changed was the name of the server. It is Windows 2008 R2 x64 Enterprise edition.