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 have downloaded Microsoft SQL Server 2008 and also Microsoft SQL Server R2.
My server name is local. When i try to connect, it shows the following error:
Cannot connect to (local).
===================================
A network-related or instance-specific error occurred while
establishing a connection to SQL Server. The server was not found or
was not accessible.
I'm trying to diagnose an issue at a customer site.
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 installed the first default intsance on top of a windows cluster and all was well. I passed the validation test, and was able to connect and ping my vco name of ticcluster and ip of 10.0.113.224.
I added added another instance through the sql cd, advanced prepare and configure an failover instance.
I'm in the process of configuring a sort-of Beowulf cluster, the major difference being that I want to be able to add nodes from any network. Because of this I can't run DHCP on the server to inventory all the nodes.
New nodes would run a package or script to configure SSH, MPI, NFS and the like. During installation they'll require the IP address of the server.
We have just installed two Windows 2008R2 Enterprise machines with identical hardware. When running the cluster validation everything is ok.
It should be simple, so it is just most likely my approach being totally off and someone will hopefully prod me into the right direction.
We have a Zabbix 2.0.3 server instance set up monitoring a bunch of different servers, but now we need to set it up to monitor and notify any alerts in regards to the SQL Server 2008 R2 Failover Active-Passive cluster.
Essentially, this is a 2 servers cluster,