May 9, 2010 at 2:37 pm
Hi,
We have clustered sql server 2005 default instance on node1 and named instance on node2.
I'm able to connect default cluster instance on node1 from my laptop using windows authentication but not the named instance on node2.
Remote connections are enabled on both the nodes and I created a user abc\scott in both instances and I'm trying to connect both the instances from my laptop using abc\scott. I'm able to connect default instance but not named instance. Getting below error while connect to clustered named instance:
TITLE: Connect to Server
------------------------------
Cannot connect to emvs1\ins1.
------------------------------
ADDITIONAL INFORMATION:
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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
Please advice
May 9, 2010 at 5:17 pm
There are a whole bunch of things that could br going on here.
First some questions. Is this a new cluster you have just built, or an existing cluster just experiencing new issues?
Have you tried logging onto the node and trying to connect from there?
If you fail both instances over to the same node do you still have an issue?
Have you checked the cluster configuration? All the IP adresses and the port numbers?
There are probably more things that could be asked, but you need to do some testing to see when you can and when you can't connect to the server. With the little bit of information you have given, and the intricacies of clusters I doubt anyone will be able to give you much help without more details.
Leo
When all else fails...read the manual.
Leo
Nothing in life is ever so complicated that with a little work it can't be made more complicated.
May 10, 2010 at 6:26 am
Have you tried connecting via IP?
IP\<named instance>
also try using the port#
IP,port
which will work the same as
IP\<named instance>,port#
If it works using the IP, you can try the full instance name with the port
myserver\<named instance>,port
or
myserver,port#
As said in the previous post, it could be a number of things but trying my suggestions will help troubleshoot.
May 10, 2010 at 12:25 pm
Its working when I provided the below
myserveramed instance
But the same is NOT working when I accessed through VPN. From VPN the below is working myserver\<named instance>,port.
What should I do to connect to myserveramed instance via VPN? I do not want to use port from VPN too.
May 10, 2010 at 12:35 pm
I'm not sure how to get around this using VPN. Perhaps someone else knows.
You could always create a local alias (with working connection) on the laptop, then you won't need to add the port when connecting.
Name the alias:myserveramed instance
May 10, 2010 at 1:08 pm
You could always create a local alias (with working connection) on the laptop, then you won't need to add the port when connecting.
please advice me on how to do the above? I never created & used alias names!
Thanks
May 10, 2010 at 1:25 pm
1. Start Sql Server Configuration Manager (Start-Programs - Microsoft SQL Server - Configuration Tools
2. Expand SQL Native Client Configuration (32 bit)
2a. Expand SQL Native Client Configuration
Note: You'll want to create an alias in each of the Step 2 if you're running 64 bit. They should be the exact same name.
3. Right Click Alias
4. New Alias
5. Provide a name. This can be any name you want but in your case this will be the sql instance name that you want to use in your connections.
6. Type the port# (your production instance shouldn't be using dynamic ports on a cluster)
7. Type the ServerName (this is the actual sql server instance). You can also use the IP address.
If necessary, Repeat Steps 3 through 7 for Step 2a.
May 10, 2010 at 1:26 pm
May 10, 2010 at 2:23 pm
Mani-584606 (5/10/2010)
Its working when I provided the belowmyserveramed instance
But the same is NOT working when I accessed through VPN. From VPN the below is working myserver\<named instance>,port.
What should I do to connect to myserveramed instance via VPN? I do not want to use port from VPN too.
Is your server on the other side of a firewall from the VPN? Could this bee causing an issue?
Leo
Leo
Nothing in life is ever so complicated that with a little work it can't be made more complicated.
May 10, 2010 at 4:04 pm
Type the port# (your production instance shouldn't be using dynamic ports on a cluster)
Steve,
Our Production cluster instances are using Dynamic ports since they configured. In this can I create alias or not?
Thanks
May 12, 2010 at 5:42 am
Yes, you can still create an alias but each time you take the sql server instance "offline", you'll need to change the port in your alias unless a different port doesn't get assigned.
You should consider using a fixed port for your instance especially if you're currently using the default port (1433).
June 2, 2010 at 12:20 pm
1. Start Sql Server Configuration Manager (Start-Programs - Microsoft SQL Server - Configuration Tools
2. Expand SQL Native Client Configuration (32 bit)
2a. Expand SQL Native Client Configuration
Note: You'll want to create an alias in each of the Step 2 if you're running 64 bit. They should be the exact same name.
3. Right Click Alias
4. New Alias
5. Provide a name. This can be any name you want but in your case this will be the sql instance name that you want to use in your connections.
6. Type the port# (your production instance shouldn't be using dynamic ports on a cluster)
7. Type the ServerName (this is the actual sql server instance). You can also use the IP address.
Hi,
I went through the above thread and the forum member Steve, is suggesting NOT to have Dynamic ports for clustered sql server instances (Point 6 in above). Could you advice why we can not have dynamic ports for clustered sql server instances?
because we have 6 clustered named instances and all of them are using dynamic ports..
Is there any security risk involved?
June 2, 2010 at 1:19 pm
It is a MS best practice to use static ports and also for security regardless of whether sql server is running on a cluster.
1. It's better to open one hole in the firewall than a range. Say you're running sql server on port 3872 then that's all the network group needs to open up rather than a range of ports for sql server.
2. You should not be using the "default" ports because they are commonly known and the first ports attacked by hackers.
More articles:
http://www.networkworld.com/community/node/24989
http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=114180
http://www.sqlserverfaq.net/tag/dynamic-port/
How To:
http://support.microsoft.com/kb/823938
NOTE: I've always changed the port after the sql server is initially installed as part of our install procedures. If the server was already in production I would be very cautious because applications might have difficulty connecting depending on how their connections are being made.
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply