We experience problems with running NC followed by WSAM in our SA6000 active/active cluster (v6.3). We have several IVS's in our cluster. We intend to use one IVS as a home office solution and run NC giving access to all our enterprise network resources. In order to administrate some restricted network resources we normally use WSAM on another IVS. When NC already started, we need to access the login page for the WSAM IVS on another node in the cluster for this to be successful. Accessing the login page for WSAM IVS on the same physical node in the cluster does not work. In an earlier upgrade (v5.3 or v5.4) we could run NC followed by WSAM on two IVS's on the same physical node. Anyone experiencing the same?
Sorry if I made myself unclear. We are running Network Connect through IVS1 on node 1 in the cluster. We then try to log in to IVS2 on node 1 in the cluster. We don't reach the login page. The sslvpn node is forwarding the DNS request and response for the login page of IVS2 but when the client tries to send a SYN to the IP-address of IVS2 the ssl vpn node does not respond to the client nor forward the SYN. We try to log in to several other IVS'es on the same node but we can't reach any sign in page. What we can reach on the same node is a secondary portal on IVS1.
So I guess this has nothing to do with running SAM after NC because we don't even reach the sign in page for the other IVS. As I can see this is a matter of accessing two IVS'es at the same time on the same node.
Hey Kath - I don't have any IVS established on my boxes so can't do a direct test. BUT! a few questions:
1- Can you login if you use a seperate browser - IE FF for IVS1, node1 and IE for IVS2, node1?
2- Could you ever do this before?
Trying to isolate is it an issue with client or server.
we tried to login to IVS1 with IE and login to IVS2 with FF, but no luck. We haven't tried with different browsers earlier. And I'm not 100% sure if it has ever worked...