Have got multiple SQL environments, both 2000 & 2005. Of these two are
clusters, one 2000 & one 2005.

Over remote VPN connection I can connect to every non-clustered server but
can't to either cluster. I've made sure that local & remote connections are
enabled on the clusters.

I have no problems connecting to both clusters on my local network so I'm
definitely connecting with the correct virtual servername.

Anybody had this issue before?

Thanks, Andy.

Hi Andy

Although I have never tried this I don't think there should be anything that
stops you doing it. How are you connecting to the Clustered instance
(connection string or SQLCMD command) ? Which protocol are you using/enabled?
Which port is being used? Are there any firewalls? Is the name being
resolved/can you connect to the IP address?

John

"AndyT" wrote:

Have you tried connecting to one of the clustered instances from a node
within the cluster that currently does not currently own the SQL Server
instance (the so-called "passive") node? If that works, then I wonder if
there is a firewall rule between where you are and where the cluster is that
is preventing you from getting to the cluster. However, if you can't get to
SQL server from another node in the cluster, it suggests that SQL is not
listening for remote connections. Be sure to check the SQL Server error
log. It says what protocols it's actually listening on. Be sure to do a
tracert on the SQL Server virtual IP.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"AndyT" <tipton (AT) tpg (DOT) com.au> wrote


Have got multiple SQL environments, both 2000 & 2005. Of these two are
clusters, one 2000 & one 2005.

Over remote VPN connection I can connect to every non-clustered server but
can't to either cluster. I've made sure that local & remote connections are
enabled on the clusters.

I have no problems connecting to both clusters on my local network so I'm
definitely connecting with the correct virtual servername.

Anybody had this issue before?

Thanks, Andy.

Could be a firewall issue. When you connect to a cluster, it listens on the
virtual IP. Replies are sent from the regular IP address, according to the
packet headers. This drives some firewalls batty. See your network admin
about allowing the physical IP as well as the virtual one to have access
from the outside.

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP



"AndyT" <tipton (AT) tpg (DOT) com.au> wrote