469,317 Members | 1,916 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,317 developers. It's quick & easy.

can not access clustering SQL Server after relocation

Hi all:

I have a clustering SQL Server on Node1 and Node2, the Node1 has named
Instance1 and Node2 has named Instance2, no default instance. We
tested it that everthing is OK, then we decide to move to DR location.

The relocation kept the same virtual and phusical server name, and we
did not change SQL Server server network utility. But server IP
addresses were changed(vitual and physical). We can start the
clustering SQL Server as before, and everything looks like well.

However the users can not access it remotely, and they did not change
the client network utility. But if I login the server,I can access it
from Query Analyzer even though ther is not client network utility
setup on the server. I can ping the vitual server name, how can I make
sure the ports are working well? (We did not use the default port for
named instance).

I remember I did input the virtual server IP address when I installed
the clustering SQL Server. Of course, it was change after relocation.
Is it the reason for failed remote login? If it is, how to fix it?

Does anyboday know there is document for clustering SQL Server
relocation?

Thanks
Willie
Jul 20 '05 #1
1 1900
w2***@hotmail.com (willie) wrote in message news:<66**************************@posting.google. com>...
Hi all:

I have a clustering SQL Server on Node1 and Node2, the Node1 has named
Instance1 and Node2 has named Instance2, no default instance. We
tested it that everthing is OK, then we decide to move to DR location.

The relocation kept the same virtual and phusical server name, and we
did not change SQL Server server network utility. But server IP
addresses were changed(vitual and physical). We can start the
clustering SQL Server as before, and everything looks like well.

However the users can not access it remotely, and they did not change
the client network utility. But if I login the server,I can access it
from Query Analyzer even though ther is not client network utility
setup on the server. I can ping the vitual server name, how can I make
sure the ports are working well? (We did not use the default port for
named instance).

I remember I did input the virtual server IP address when I installed
the clustering SQL Server. Of course, it was change after relocation.
Is it the reason for failed remote login? If it is, how to fix it?

Does anyboday know there is document for clustering SQL Server
relocation?

Thanks
Willie


This article might help:

http://support.microsoft.com/default...&Product=sql2k

Simon
Jul 20 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by Nico de Groot | last post: by
3 posts views Thread by Shabam | last post: by
5 posts views Thread by Paul Shaw | last post: by
14 posts views Thread by Sean C. | last post: by
11 posts views Thread by chmmr | last post: by
3 posts views Thread by dejavue82 | last post: by
1 post views Thread by CARIGAR | last post: by
reply views Thread by zhoujie | last post: by
reply views Thread by suresh191 | last post: by
reply views Thread by harlem98 | last post: by
reply views Thread by harlem98 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.