 | |
best practice for remotely connecting to Cluster with Client GUI?
microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
best practice for remotely connecting to Cluster with Client GUI? -
01-04-2008
, 04:30 PM
#2
| |||
| |||
|
|
Hi All: I have an active/passive SQL 2005 Cluster set up on a subnet that with a local Active Directory domain. Any computers in the domain can connect to it using "SQLCluster" SQL Mgmt Studio and connect with Windows Authentication. This subnet is connected to a remote location with a point-2-point VPN. All protocols are allowed through the VPN. The remote location has an SBS2003 server acting as the domain controller for the computers there. If a user in the remote domain wants to connect to the server using Mgmt Studio, they can't connect "SQLCluster" and they can't connect with "SQLCluster.[clusterdomain].local" because the SBS server doesn't know how to find it obviously. Question is, what is the appropriate way to connect? Using the IP address I believe is not recommended because the connection will break if the Cluster fails over to the second server. What is the best practice for giving them access? |
connections...but is this the correct way to connect, or is there a "better
practice"?
#3
| |||
| |||
|
|
Hi All: I have an active/passive SQL 2005 Cluster set up on a subnet that with a local Active Directory domain. Any computers in the domain can connect to it using "SQLCluster" SQL Mgmt Studio and connect with Windows Authentication. This subnet is connected to a remote location with a point-2-point VPN. All protocols are allowed through the VPN. The remote location has an SBS2003 server acting as the domain controller for the computers there. If a user in the remote domain wants to connect to the server using Mgmt Studio, they can't connect "SQLCluster" and they can't connect with "SQLCluster.[clusterdomain].local" because the SBS server doesn't know how to find it obviously. Question is, what is the appropriate way to connect? Using the IP address I believe is not recommended because the connection will break if the Cluster fails over to the second server. What is the best practice for giving them access? |
connections...but is this the correct way to connect, or is there a "better
practice"?
#4
| |||
| |||
|
|
Hi All: I have an active/passive SQL 2005 Cluster set up on a subnet that with a local Active Directory domain. Any computers in the domain can connect to it using "SQLCluster" SQL Mgmt Studio and connect with Windows Authentication. This subnet is connected to a remote location with a point-2-point VPN. All protocols are allowed through the VPN. The remote location has an SBS2003 server acting as the domain controller for the computers there. If a user in the remote domain wants to connect to the server using Mgmt Studio, they can't connect "SQLCluster" and they can't connect with "SQLCluster.[clusterdomain].local" because the SBS server doesn't know how to find it obviously. Question is, what is the appropriate way to connect? Using the IP address I believe is not recommended because the connection will break if the Cluster fails over to the second server. What is the best practice for giving them access? |
connections...but is this the correct way to connect, or is there a "better
practice"?
#5
| |||
| |||
|
|
Hi All: I have an active/passive SQL 2005 Cluster set up on a subnet that with a local Active Directory domain. Any computers in the domain can connect to it using "SQLCluster" SQL Mgmt Studio and connect with Windows Authentication. This subnet is connected to a remote location with a point-2-point VPN. All protocols are allowed through the VPN. The remote location has an SBS2003 server acting as the domain controller for the computers there. If a user in the remote domain wants to connect to the server using Mgmt Studio, they can't connect "SQLCluster" and they can't connect with "SQLCluster.[clusterdomain].local" because the SBS server doesn't know how to find it obviously. Question is, what is the appropriate way to connect? Using the IP address I believe is not recommended because the connection will break if the Cluster fails over to the second server. What is the best practice for giving them access? |
connections...but is this the correct way to connect, or is there a "better
practice"?
#6
| |||
| |||
|
|
Hi All: I have an active/passive SQL 2005 Cluster set up on a subnet that with a local Active Directory domain. Any computers in the domain can connect to it using "SQLCluster" SQL Mgmt Studio and connect with Windows Authentication. This subnet is connected to a remote location with a point-2-point VPN. All protocols are allowed through the VPN. The remote location has an SBS2003 server acting as the domain controller for the computers there. If a user in the remote domain wants to connect to the server using Mgmt Studio, they can't connect "SQLCluster" and they can't connect with "SQLCluster.[clusterdomain].local" because the SBS server doesn't know how to find it obviously. Question is, what is the appropriate way to connect? Using the IP address I believe is not recommended because the connection will break if the Cluster fails over to the second server. What is the best practice for giving them access? |
connections...but is this the correct way to connect, or is there a "better
practice"?
#7
| |||
| |||
|
|
Hi All: I have an active/passive SQL 2005 Cluster set up on a subnet that with a local Active Directory domain. Any computers in the domain can connect to it using "SQLCluster" SQL Mgmt Studio and connect with Windows Authentication. This subnet is connected to a remote location with a point-2-point VPN. All protocols are allowed through the VPN. The remote location has an SBS2003 server acting as the domain controller for the computers there. If a user in the remote domain wants to connect to the server using Mgmt Studio, they can't connect "SQLCluster" and they can't connect with "SQLCluster.[clusterdomain].local" because the SBS server doesn't know how to find it obviously. Question is, what is the appropriate way to connect? Using the IP address I believe is not recommended because the connection will break if the Cluster fails over to the second server. What is the best practice for giving them access? |
connections...but is this the correct way to connect, or is there a "better
practice"?
#8
| |||
| |||
|
|
Hi All: I have an active/passive SQL 2005 Cluster set up on a subnet that with a local Active Directory domain. Any computers in the domain can connect to it using "SQLCluster" SQL Mgmt Studio and connect with Windows Authentication. This subnet is connected to a remote location with a point-2-point VPN. All protocols are allowed through the VPN. The remote location has an SBS2003 server acting as the domain controller for the computers there. If a user in the remote domain wants to connect to the server using Mgmt Studio, they can't connect "SQLCluster" and they can't connect with "SQLCluster.[clusterdomain].local" because the SBS server doesn't know how to find it obviously. Question is, what is the appropriate way to connect? Using the IP address I believe is not recommended because the connection will break if the Cluster fails over to the second server. What is the best practice for giving them access? |
connections...but is this the correct way to connect, or is there a "better
practice"?
#9
| |||
| |||
|
|
Hi All: I have an active/passive SQL 2005 Cluster set up on a subnet that with a local Active Directory domain. Any computers in the domain can connect to it using "SQLCluster" SQL Mgmt Studio and connect with Windows Authentication. This subnet is connected to a remote location with a point-2-point VPN. All protocols are allowed through the VPN. The remote location has an SBS2003 server acting as the domain controller for the computers there. If a user in the remote domain wants to connect to the server using Mgmt Studio, they can't connect "SQLCluster" and they can't connect with "SQLCluster.[clusterdomain].local" because the SBS server doesn't know how to find it obviously. Question is, what is the appropriate way to connect? Using the IP address I believe is not recommended because the connection will break if the Cluster fails over to the second server. What is the best practice for giving them access? |
connections...but is this the correct way to connect, or is there a "better
practice"?
#10
| |||
| |||
|
|
Hi All: I have an active/passive SQL 2005 Cluster set up on a subnet that with a local Active Directory domain. Any computers in the domain can connect to it using "SQLCluster" SQL Mgmt Studio and connect with Windows Authentication. This subnet is connected to a remote location with a point-2-point VPN. All protocols are allowed through the VPN. The remote location has an SBS2003 server acting as the domain controller for the computers there. If a user in the remote domain wants to connect to the server using Mgmt Studio, they can't connect "SQLCluster" and they can't connect with "SQLCluster.[clusterdomain].local" because the SBS server doesn't know how to find it obviously. Question is, what is the appropriate way to connect? Using the IP address I believe is not recommended because the connection will break if the Cluster fails over to the second server. What is the best practice for giving them access? |
connections...but is this the correct way to connect, or is there a "better
practice"?
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.