[THIN] Re: Access Gateway 4.2
- From: Jeremy Saunders <jeremy.saunders@xxxxxxxxxxx>
- To: thin@xxxxxxxxxxxxx
- Date: Sat, 24 Feb 2007 09:22:32 +0900
Hi Chad,
I'm a bit confused by the way you've worded your question, but it sounds
like a DNS issue to me. Can you ping site2.domain.com under the different
scanarios and see what it returns? Also do it from the desktop of the CAG
and the WI server.
Cheers.
Kind regards,
Jeremy Saunders
Senior Technical Specialist
Infrastructure Technology Services
(ITS) & Cerulean
Global Technology Services (GTS)
IBM Australia
Level 1, 1060 Hay Street
West Perth WA 6005
Postal: PO Box 525, West Perth WA
6872
Visit us at
http://www.ibm.com/services/au/its
P: +61 8 9261 8412 F: +61 8 9261 8486
P: (Reception) +61 8 9261 8420 E-mail:
M: TBA jeremy.saunders@xxxxxxxxxxx
"Schneider, Chad
M"
<CMSchneider@Bemi To
s.com> "'thin@xxxxxxxxxxxxx'"
Sent by: <thin@xxxxxxxxxxxxx>
thin-bounce@freel cc
ists.org
Subject
[THIN] Access Gateway 4.2
24/02/2007 12:24
AM
Please respond to
thin@xxxxxxxxxxxx
g
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
SBC SITES ONLY GOOGLE SEARCH: http://www.F1U.com
************************************************
For Archives, RSS, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://www.freelists.org/list/thin
************************************************
- 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