![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi, I a a two node win 2003 cluster running active / active with serveral SQL 2000 virtual servers between them. I have noticed the following and am wondering if this is correct behaviour and if not how I correct it: 1) If I start up enterprise manager and go to register one of the Virtual servers, it is not automatically found to be added but normally connects OK if I type in the virtual server/Instance. 2) The virtual servers are not able to be connected to from client PC's without running cliconfg.exe and alias being created with the alias name the same as the virtual server/instance and the connection actually including the port number that SQL virual server is on. Any guidance appreciated. Jon |
#3
| |||
| |||
|
|
Hi Generally, we have all our developers use "virtualname\instancename, portnumber" to connect to our servers as we have a number of firewalls that might not let port 1434 traffic though. Also check that MDAC 2.6 or later are on the client machines. EM not showing all the instances can be caused by 1434 issues too, like with clients. Regards -------------------------------- Mike Epprecht, Microsoft SQL Server MVP Zurich, Switzerland IM: mike (AT) epprecht (DOT) net MVP Program: http://www.microsoft.com/mvp Blog: http://www.msmvps.com/epprecht/ "Jon" <Jon (AT) discussions (DOT) microsoft.com> wrote in message news:49FA6D93-EF9B-4F19-8DC5-C5BCBA4590E9 (AT) microsoft (DOT) com... Hi, I a a two node win 2003 cluster running active / active with serveral SQL 2000 virtual servers between them. I have noticed the following and am wondering if this is correct behaviour and if not how I correct it: 1) If I start up enterprise manager and go to register one of the Virtual servers, it is not automatically found to be added but normally connects OK if I type in the virtual server/Instance. 2) The virtual servers are not able to be connected to from client PC's without running cliconfg.exe and alias being created with the alias name the same as the virtual server/instance and the connection actually including the port number that SQL virual server is on. Any guidance appreciated. Jon |
#4
| |||
| |||
|
|
Hi Generally, we have all our developers use "virtualname\instancename, portnumber" to connect to our servers as we have a number of firewalls that might not let port 1434 traffic though. Also check that MDAC 2.6 or later are on the client machines. EM not showing all the instances can be caused by 1434 issues too, like with clients. Regards -------------------------------- Mike Epprecht, Microsoft SQL Server MVP Zurich, Switzerland IM: mike (AT) epprecht (DOT) net MVP Program: http://www.microsoft.com/mvp Blog: http://www.msmvps.com/epprecht/ "Jon" <Jon (AT) discussions (DOT) microsoft.com> wrote in message news:49FA6D93-EF9B-4F19-8DC5-C5BCBA4590E9 (AT) microsoft (DOT) com... Hi, I a a two node win 2003 cluster running active / active with serveral SQL 2000 virtual servers between them. I have noticed the following and am wondering if this is correct behaviour and if not how I correct it: 1) If I start up enterprise manager and go to register one of the Virtual servers, it is not automatically found to be added but normally connects OK if I type in the virtual server/Instance. 2) The virtual servers are not able to be connected to from client PC's without running cliconfg.exe and alias being created with the alias name the same as the virtual server/instance and the connection actually including the port number that SQL virual server is on. Any guidance appreciated. Jon |
#5
| |||
| |||
|
|
Hi Mike, Another poinr - I am not a developer (I'm the network infrastructure manager) how would the developers specify the port number in their app if it is writen in house? Thanks, Jon "Mike Epprecht (SQL MVP)" wrote: Hi Generally, we have all our developers use "virtualname\instancename, portnumber" to connect to our servers as we have a number of firewalls that might not let port 1434 traffic though. Also check that MDAC 2.6 or later are on the client machines. EM not showing all the instances can be caused by 1434 issues too, like with clients. Regards -------------------------------- Mike Epprecht, Microsoft SQL Server MVP Zurich, Switzerland IM: mike (AT) epprecht (DOT) net MVP Program: http://www.microsoft.com/mvp Blog: http://www.msmvps.com/epprecht/ "Jon" <Jon (AT) discussions (DOT) microsoft.com> wrote in message news:49FA6D93-EF9B-4F19-8DC5-C5BCBA4590E9 (AT) microsoft (DOT) com... Hi, I a a two node win 2003 cluster running active / active with serveral SQL 2000 virtual servers between them. I have noticed the following and am wondering if this is correct behaviour and if not how I correct it: 1) If I start up enterprise manager and go to register one of the Virtual servers, it is not automatically found to be added but normally connects OK if I type in the virtual server/Instance. 2) The virtual servers are not able to be connected to from client PC's without running cliconfg.exe and alias being created with the alias name the same as the virtual server/instance and the connection actually including the port number that SQL virual server is on. Any guidance appreciated. Jon |
#6
| |||
| |||
|
|
Hi, I a a two node win 2003 cluster running active / active with serveral SQL 2000 virtual servers between them. I have noticed the following and am wondering if this is correct behaviour and if not how I correct it: 1) If I start up enterprise manager and go to register one of the Virtual servers, it is not automatically found to be added but normally connects OK if I type in the virtual server/Instance. 2) The virtual servers are not able to be connected to from client PC's without running cliconfg.exe and alias being created with the alias name the same as the virtual server/instance and the connection actually including the port number that SQL virual server is on. Any guidance appreciated. Jon |
![]() |
| Thread Tools | |
| Display Modes | |
| |