June 3, 2003 at 2:31 pm
Keep getting the above error trying to connect to a server remotely. Works locally.
If I move the group to failover node,
acts the same. Remote connections fail,
local succeed. Reviewed knowledge base 328306 with no luck.
June 3, 2003 at 2:35 pm
How you are connecting to the server? Terminal server? Remote Desktop? Is the tools installed on the server? Also if yes try changing the protocol
Shas3
June 4, 2003 at 6:12 am
I have an active/active cluster setup.
I can access one instance from either node,
but the other instance is only accessible
if you login locally.
June 4, 2003 at 6:33 am
Because your SQL Servers are in active/active, I assumed you have one default inatance and one named instance. you are able to access the default instance that uses TCP port 1433. The named instance is using another TCP port which you acn find it from SQL Server errorlog. You can work around by creating alias with client network utility in your client machine with the correct TCP port number and connect it with the alias.
Make sure you use correct SQL Server virtual server name.
Have you tried to connect it with virtual IP address?
Edited by - Allen_Cui on 06/04/2003 07:10:39 AM
June 4, 2003 at 9:05 am
This worked!
Thanks
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply