thanks, I will check that out Steve Greenberg Thin Client Computing 34522 N. Scottsdale Rd. suite D8453 Scottsdale, AZ 85262 (602) 432-8649 (602) 296-0411 fax steveg@xxxxxxxxxxxxxx _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Jeff Durbin Sent: Wednesday, November 09, 2005 6:39 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Access Gateway 4.1 I think you're supposed to exempt the CAG client completely as far as the software firewall is concerned. There's some info in the CAG documentation towards the end. They mention a bunch of software firewalls, but I don't think they specifically address the Windows firewall. JD _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Steve Greenberg Sent: Wednesday, November 09, 2005 9:08 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Access Gateway 4.1 I hadn't seen this, this is good to know. Do you have to configure any specific inbound/outbound exceptions? Steve Greenberg Thin Client Computing 34522 N. Scottsdale Rd. suite D8453 Scottsdale, AZ 85262 (602) 432-8649 (602) 296-0411 fax steveg@xxxxxxxxxxxxxx _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Jeff Durbin Sent: Wednesday, November 09, 2005 7:28 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Access Gateway 4.1 The Windows software firewall. Same thing applies to any software firewall on your client. _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Steve Greenberg Sent: Tuesday, November 08, 2005 9:04 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Access Gateway 4.1 What firewall are you referrring to? Steve Greenberg Thin Client Computing 34522 N. Scottsdale Rd. suite D8453 Scottsdale, AZ 85262 (602) 432-8649 (602) 296-0411 fax steveg@xxxxxxxxxxxxxx _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Jeff Durbin Sent: Tuesday, November 08, 2005 8:33 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Access Gateway 4.1 This behavior will result if you don't allow the CAG client as an exception to the Windows firewall. If you configure your firewall to allow exceptions, then make the connection with the client, it should ask you if you want to allow the CAG client as an exception. Answer yes. _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Steve Greenberg Sent: Tuesday, November 08, 2005 3:42 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Access Gateway 4.1 Did you enable/disable the Split DNS setting and see if that changes the behavior?? Steve Greenberg Thin Client Computing 34522 N. Scottsdale Rd. suite D8453 Scottsdale, AZ 85262 (602) 432-8649 (602) 296-0411 fax steveg@xxxxxxxxxxxxxx _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Schneider, Chad M Sent: Tuesday, November 08, 2005 1:03 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Access Gateway 4.1 FQDN, outside points to 68.X.X.X address. Internal it is an internal address, of course. _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Schneider, Chad M Sent: Tuesday, November 08, 2005 1:53 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Access Gateway 4.1 From internal, I ping www.bemis.com <http://www.bemis.com/> , I get 192.x.x.x address, while within CSA connection from internet, I ping www.bemis.com <http://www.bemis.com/> and I get 68.XXX address?? _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Steve Greenberg Sent: Tuesday, November 08, 2005 1:43 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Access Gateway 4.1 Are you about trying to ping the CAG, or, internal addresses from the outside? Steve Greenberg Thin Client Computing 34522 N. Scottsdale Rd. suite D8453 Scottsdale, AZ 85262 (602) 432-8649 (602) 296-0411 fax steveg@xxxxxxxxxxxxxx _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Schneider, Chad M Sent: Tuesday, November 08, 2005 12:39 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Access Gateway 4.1 Yes. _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Steve Greenberg Sent: Tuesday, November 08, 2005 1:34 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Access Gateway 4.1 Did you click the option to allow ping and on the admin page? Steve Greenberg Thin Client Computing 34522 N. Scottsdale Rd. suite D8453 Scottsdale, AZ 85262 (602) 432-8649 (602) 296-0411 fax steveg@xxxxxxxxxxxxxx _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Schneider, Chad M Sent: Tuesday, November 08, 2005 12:17 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Access Gateway 4.1 Had a demo unit put in. Can make the Secure Access connection fine, open to all IP/port. Can resolve names internal, but can't successfully ping. Any ideas? I thought this thing was supposed to be easy to configure. :-)