May 6, 2005 at 1:21 am
We have 2 nodes sql 2000 server cluster on Windows2003.
The problem is when in QA I try to connect to virtual SQL server and typing IP address the following error appears:
Unable to connect to sql server xx.xx.xx.xx
Server: Msg 14, Level 16, State 1
[Microsoft].[ODBC SQL Server Driver].[DBNETLIB]Invalid Connection
Interesting thing is that when I try to open the second virtual server I've got other error, not the same:
Unable to connect to sql server xx.xx.xx.xx
Server: Msg 17, Level 16, State 1
[Microsoft].[ODBC SQL Server Driver].[DBNETLIB]SQL server doesnt exists or access denied
When I connect to them typing their names not IP addresses all works fine. Does anyone has any ideas?
Thanks
May 6, 2005 at 5:47 am
Hi Vidaz,
Please check the Virtual IP address, by which you are connecting on Query Analyser. If the IP address by which you are attempting to connect to Query Analyser it is not for SQL Server resource, it will connect.
Have a look on the SQL Server Error log when the SQL Server Services are started, it would have the entry for the IP on which the SQL Server listening on. Otherwise if it is Microsoft Cluster look on Cluster administrator and find out the IP for SQL Server defined there.
Basically all the resource on Cluster will have a separate Virtual IP address defined for it.
May 6, 2005 at 6:10 am
Yes, Siva, I've allready checked these IP addresses. It doesn't work. Neither physical nor virtual. On sql server log it's said that one node listen to xx.xx.xx.x1 :1433 , other node- xx.xx.xx.x2:1424
These ports have been assigned dynamically.
When I try to connect from cluster node to outside SQL server by its IP address all works fine.
The connecting method using IP addresses doesn't work when I attemp to connect from outside to cluster nodes and inside the cluster between 2 nodes
May 6, 2005 at 6:32 am
I have a suspicion that there is a named instances issue...
May 6, 2005 at 9:04 am
If you are attempting to connect to the servers you should also include the named instance in the connection.
xxx.xxx.xx.x will not work.
xxx.xxx.xx.x\Instancename will work.
May 8, 2005 at 11:20 pm
Yes it's working. Thanks. It also works with IP and port number through the server alias
October 11, 2005 at 9:37 am
I got the same problem.
Trying to connect to a virtual server from a different server.
I can ping the virtual IP address, but cannot connect.
Get an error message saying the username or password is incorrect or the server does not exist. I am trying to connect using \\VirtualSvrName\InstanceName
I checked Cluster Admin and I have the right IP Address and it pings everytime from the server I am trying to connect from.
Any idea's?
Clive
October 11, 2005 at 12:50 pm
Dont use \\VirtualSvrName\InstanceName through QA just use VirtualSvrName\InstanceName
October 12, 2005 at 2:44 am
Sorry, typo by me!
Not using \\VirtualSvrName\InstanceName. I am trying to connect with VirtualSvrName\InstanceName
October 12, 2005 at 7:15 am
Have you tried connecting using the ipaddress\instancename ?
October 12, 2005 at 7:19 am
Yup, and that works! I tried this when I got in...Forgot to update the forum.
Thanks for your input tho!
October 12, 2005 at 9:32 am
If you are able to connect using the IP address, but not the instance name, check that the virtual server name has been entered into dns correctly (try pinging it and making sure that it comes back with the correct ip)
October 25, 2005 at 11:22 am
I am trying to connect to a instance of SQL 2000 on a webserver and also am having difficulty. I am using QA and when trying to connect I put the IP address\instance name into the field "SQL Server" and using Windows Authentication. I cannot connect. I get an error "Invalid connection". Any ideas?
Thanks.
Alex
October 25, 2005 at 12:18 pm
Is the webserver in the same domain? And do you have rights?
The other thing to check is that you are not blocked by a firewall and that you are using tcp/ip to connect. Are you able to ping the ip address of the sql server from your machine?
October 12, 2007 at 6:58 am
Hi I'm having a the same issue too. I have a webserver out in the DMZ, our network guys tell me that the port or rule has been set up to allow netowork connections from the webserver to the cluster. I try to ping the cluster by virtual name and virtual IP but it times out?
I can connect to the cluster from nodes inside the DMZ but not from the DMZ itself.
The webserver can connect to other clusters on our network so the network guys are telling me that its a cluster issue.
any ideas?
TIA
Go PATS
Viewing 15 posts - 1 through 15 (of 15 total)
You must be logged in to reply to this topic. Login to reply