|
|
|
|
|
|
|
|
 |
 |
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [FW1] Not able to log into NT domain when Secure Remote is installed
My company is having this problem as well. When we have Secure Remote installed on all adapters we cannot see the NT domains. We we install it only on the dial-up adapter we can see the NT domains. We also have a Novell client we log into and we thought our problem was connected with that. I do have an open support call with Checkpoint to try to resolve this problem. Wendy >>> "Croft, Ed" <[email protected]> 02/01/01 08:12PM >>> My company has Secure Remote (versions 4174, 4166, 4165, etc...) for users that have DSL connections from their homes. This works fairly well and they are able to log onto the NT domain from inside the F/W, or from their DSL connections outside of the F/W (using NT4 and SDL). We have had this solution in place for approx. 6 months. The other day I needed to add some more networks to my encryption domain that was defined under the VPN tab of the F/W node in the Policy Editor. I saved the changes and applied the ruleset. Now I can't get logged onto the NT domain from a client running Secure Remote, but I do get my DHCP information and I can ping by IP address and name. If I uninstall the Secure Remote software, I can then log onto the NT domain. Is there ANY way that the additional networks I added to the encryption domain on the F/W could have anything to do with the client not being able to log onto the NT domain? (I have tried updating the site, blowing away the site and recreating it, and reinstalling the software from scratch on the clients). According to our vendor support (Verisign), the change that I made to the encryption domain should not have had any affect on this problem. But, they also said that I would have problems logging into the NT domain with the Secure Remote software installed on all adapters. I can't believe that this would work flawlessly for the last 6 months and then all of a sudden stop. I am wondering if I should completely remove the encryption domain and then start over from the beginning, but I would like input from people that have more experience with Checkpoint / Secure Remote. Thanks in advance for any ideas that y'all can think of... -Ed ================================================================================ 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 ================================================================================
|
||||||||||
 |
 |
 |
 |
 |
 |
 |
 |
 |
|
