Yes, one of you will have to change your address blocks as far as VPN-1 is concerned.
Chris -----Original Message----- From: Tim Jones [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 15, 2001 1:54 PM To: [EMAIL PROTECTED] Subject: [FW-1] SecureClient encryption domains and NAT'd user networks. Hello. I've run into an issue with SecureClient 4.1 that I'm hoping someone can help me with. Our encryption domain is 192.168.0.0. I'm wondering how we can allow a client whose home network uses addresses in this range to access the encryption domain. Whenever the client tries to ping something in the encryption domain, the traffic doesn't go through the VPN, and I'm not 100% sure why. Are there issues with using SecureClient from a network in the same subnet as the encryption domain? Thanks! __________________________________________________ Do You Yahoo!? Find the one for you at Yahoo! Personals http://personals.yahoo.com =============================================== To unsubscribe from this mailing list, please see the instructions at http://www.checkpoint.com/services/mailing.html =============================================== =============================================== To unsubscribe from this mailing list, please see the instructions at http://www.checkpoint.com/services/mailing.html ===============================================
