[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [FW1] SecuRemote implementation problems
I had exactly the same problem. If you have a static IP address, and your destination is to a computer on the same subnet, the client tries to route through the local NIC instead of the dial up adapter. I "fixed" the problem by changing the NIC confiuration to DHCP when I was out of the office and switching back to a static IP address when back in the office. The DHCP request fails, but that does not matter. Since this is a routing problem and not a client problem, I doubt that a different client would fix the problem. Good luck, David Hoober > -----Original Message----- > From: Martin, Kevin T [SMTP:[email protected]] > Sent: Friday, June 01, 2001 11:56 AM > To: [email protected]; [email protected] > Subject: RE: [FW1] SecuRemote implementation problems > > > Stephen, > For your winnt and win2k users you should be able to setup hardware > profiles that include/exclude the necessary interfaces and then load > Securemote on the interface that needs to be used at home. Then the users > just need to login to the correct profile. > > Kevin > > -----Original Message----- > From: Felicetti, Stephen A. [mailto:[email protected]] > Sent: Thursday, May 31, 2001 3:49 PM > To: ''[email protected]' ' > Subject: [FW1] SecuRemote implementation problems > > > Hi everyone... > > For the past couple weeks, I've been attempting to get a handle on > SecuRemote. > I'm able to establish the connection using Win98, WinNT, and Win2k. Using > Hybrid mode IKE. I manually distribute the userc.c file to each client. > *However*, only Win98 is working 100%, but only as long as I disable the > internal NIC interface (which has a static IP address for our internal > network) This will be a problem for the end-users when they travel between > home and office. No explanation needed there, I'm sure... So that's one > problem. > > With both WinNT and Win2k, I also have to disable the internal NIC > interface > (same reasons as above). But I'm not able to communicate with any of our > public web servers. They work fine *before* the VPN is established, but > not > afterward. The FW log shows the initial http connection going through, but > then no more traffic is passed to the client, and it times out. Strange > thing is....ftp and telnet work fine. > > Is anyone out there successfully using this product in a multiple OS > environment? And if so, have you experienced any of these problems? > > At this point, I doubt I'll be able to release this to my users and will > be > forced to look for another 'client to site' VPN client. > From messages I've read on the list, this wont be easy. > But I've found one company that claims they have tested it against > CheckPoint and will be releasing it in June. www.neon.com. Anybody know > anything about it? > > Any words of encouragement are appreciated. > > Thanks, > Steve > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Stephen A. Felicetti Fox Chase Cancer Center > Sr. Network Engineer(v) > Research Information Technology Facility(f) > [email protected] > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > > ========================================================================== > ====== > 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 ================================================================================
|