Pete,
I don't think that it's a route issue(was it?) more than
it's a DHCP issue. There was a bug (since fixed) where
the OS would not give up an address upon shutdown
or on bootup if it wasn't allowed to keep/couldn't find a
DHCP server.
I did a quick check for the Q# on MS site, but no luck.
Anyone have that?
Robert
- -
Robert P. MacDonald, Network Engineer
e-Business Infrastructure
G o r d o n F o o d S e r v i c e
Voice: +1.616.261.7987 email: [EMAIL PROTECTED]
>>> Peter Goodridge <[EMAIL PROTECTED]> 9/29/00 1:15:02 PM >>>
>
>I've been seeing this behavour on SecRemote since
>build 4005. I understand it more of windows issue.
>Windows remembers the routes across reboots, even
>though the ip address has changed. When you take the
>laptop home windows will send the traffic to the
>ethernet card, because that's where it sent it before.
>
>To fix it you can use winipcfg to do a release all
>before dialing in, or under NT use route -f.
>
>HTH,
>Pete Goodridge
>
>--- Dan Hitchcock <[EMAIL PROTECTED]> wrote:
>> If the machine already has an address bound to any
>> of its adapters that is
>> inside the encryption domain (as would be the case
>> in the "take the PC home"
>> scenario, SecuRemote will never prompt for
>> authentication at all, as it will
>> assume that encryption is not required. Amit, can
>> you ping anything on the
>> internal network from the SR client by IP address?
>> If so, your issue may be
>> name resolution. If not, maybe Gibson is right, and
>> this is new behavior in
>> the latest versions of SR.
>>
>> Dan Hitchcock
>> CCNA, MCSE
>> Network Engineer
>> Xylo, Inc. (formerly employeesavings.com)
>> 425.456.3970
>> The work/life solution for corporate thought leaders
>>
>>
>> -----Original Message-----
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED]]
>> Sent: Wednesday, September 27, 2000 5:58 AM
>> To: [EMAIL PROTECTED];
>> [EMAIL PROTECTED]
>> Subject: RE: [FW1] Securemote Issue....
>>
>>
>>
>> I would suggest that you either make sure that
>> SecuRemote is bound only to
>> dial-up adapters or release the IP address from the
>> NIC when you bring the
>> machine home.
>>
>> > -----Original Message-----
>> > From: Amit Saha [ mailto:[EMAIL PROTECTED]
>> <mailto:[EMAIL PROTECTED]> ]
>> > Sent: Wednesday, September 27, 2000 6:52 AM
>> > To: Fw-1-Mailinglist (E-mail)
>> > Subject: [FW1] Securemote Issue....
>> >
>> >
>> >
>> > Hello All,
>> >
>> > we have Checkpoint 4.1 SP1 and we are using
>> securemote to
>> > connect to our
>> > internal LAN via internet. However, there are some
>> laptops
>> > which are used in
>> > office as well as home. I have bound the
>> securemote to the
>> > dial-up adapter.
>> > (OS is windows 98). When i am using the laptop in
>> the office,
>> > i am able to
>> > connect to Internal network thru lan card which is
>> fine. Now,
>> > i take the
>> > laptop to my house and i connect to internet. Then
>> i try to
>> > connect to my
>> > web intranet server, securemote pops up the auth
>> screen.
>> > However, after
>> > successful authentication, i am not able to
>> connect to the
>> > site. I believe,
>> > its still trying to got thru the lan card to
>> connect to the
>> > intranet web
>> > server. Can somebody help me with this, as to
>> whether its a problem to
>> > securemote configuration.
>> >
>> > Warm Regards,
>> >
>> > Amit Saha
========================
================================================================================
To unsubscribe from this mailing list, please see the instructions at
http://www.checkpoint.com/services/mailing.html
================================================================================
