I am trying to register a sql cluster (SQLVS01) on a server that is on
the other end of an IPSec tunnel. The goal is secure transaction
replication of seperate publications in both directions. I am not
having any trouble registering the remote sql server (SQL03) at the
cluster location but when I try to register the virtual sql server
(SQLVS01) at the remote location, Enterprise Manager hangs.
I put a packet sniffer on both ends, and it appears that when I try to
register the virtual server, it sends the request from the virtual IP,
but responds with the actual IP that is currently running, but I am
relatively inexperienced in sniffing packets.
The IPSec tunnel is between a PIX 515 and a PIX 506 and appears to be
solid.
Ideas?
Brian Russell
StandardCall
You might want to post this to the custering group
(microsoft.public.sqlserver.clustering).
I don't even know how to spell custering.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Brian" <brian.russell@.standardcall.com> wrote in message
news:5a7d7734.0409170613.5f4b21fb@.posting.google.c om...
> I am trying to register a sql cluster (SQLVS01) on a server that is on
> the other end of an IPSec tunnel. The goal is secure transaction
> replication of seperate publications in both directions. I am not
> having any trouble registering the remote sql server (SQL03) at the
> cluster location but when I try to register the virtual sql server
> (SQLVS01) at the remote location, Enterprise Manager hangs.
> I put a packet sniffer on both ends, and it appears that when I try to
> register the virtual server, it sends the request from the virtual IP,
> but responds with the actual IP that is currently running, but I am
> relatively inexperienced in sniffing packets.
> The IPSec tunnel is between a PIX 515 and a PIX 506 and appears to be
> solid.
> Ideas?
> Brian Russell
> StandardCall
No comments:
Post a Comment