You can use either of these two options
Option 1
----------
Create an alias on client machine
1. Open SQL Server Configuration Manager
2. Expand SQL Native Client Configuration
3. Right click Aliases--> New Alias
4. Alias Name: <Name of the Cluster>
4. Port No:1433
5. Protocol: TCP/IP
6. Server: <IP Address>
Option 2
----------
Add entey for IP mapping in the hosts file located on client machine
C:\WINDOWS\system32\drivers\etc\hosts
--
Regards,
Manoj Raheja
MCDBA, MCITP
"geek-y-guy" wrote:
> > 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?
> >
>
> Sorry, I realize now that the cluster IP will work for remote
> connections...but is this the correct way to connect, or is there a "better
> practice"?
>
>
> >> Stay informed about: best practice for remotely connecting to Cluster with Clie..