[THIN] Re: Access Gateway 4.2
- From: "Steve Greenberg" <steveg@xxxxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Fri, 23 Feb 2007 08:59:19 -0700
If you have multiple CAG's the client connect list is automatically
populated with both IP addresses for auto failover purposes. This feature is
not well explained or document, but it is how it works!
Steve Greenberg
Thin Client Computing
34522 N. Scottsdale Rd D8453
Scottsdale, AZ 85262
(602) 432-8649
www.thinclient.net
steveg@xxxxxxxxxxxxxx
_____
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Schneider, Chad M
Sent: Friday, February 23, 2007 8:24 AM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Access Gateway 4.2
Something I have found.
Access Gateway.
If I connect to the Access Gateway VPN (Secure Access Client), I connect to
my site2.domain.com. If I connect to site2.domain.com, using the connection
to the Web Interface, it connects me to the other appliance we have. I see
the 1494 connection on site1.domain.com, using the Access Gateway Admin
terminal, remote monitor.
What would cause this?
Chad Schneider
Technology Analyst/Citrix Admin.
Bemis Company, Inc.
920-303-7609
- References:
- [THIN] Access Gateway 4.2
- From: Schneider, Chad M
Other related posts:
- » [THIN] Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- » [THIN] Re: Access Gateway 4.2
- [THIN] Access Gateway 4.2
- From: Schneider, Chad M