| |
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [FW-1] IP Pool NAT for SecuRemote users with LinkSys Routers
- To: [email protected]
- Subject: Re: [FW-1] IP Pool NAT for SecuRemote users with LinkSys Routers
- From: "Laverty, Jim" <[email protected]>
- Date: Wed, 17 Oct 2001 15:00:14 -0400
- Reply-to: Mailing list for discussion of Firewall-1 <[email protected]>
- Sender: Mailing list for discussion of Firewall-1 <[email protected]>
- Thread-index: AcFXLHNehZwzGh+wQKapjJj5QrAYQA==
- Thread-topic: [FW-1] IP Pool NAT for SecuRemote users with LinkSys Routers
Upgrade your Linksys firmware (to version 1.39 or newer) to get around
this problem. I history serves me, it was a NAT issue with the
firmware. I've been using a Linksys at home without any problems, until
SP5.
Now we're having issues with service pack 5 and yesterday's sp5-hotfix
for the panics :)
With SDL we're seeing fragmentation with and without the modzap for
fragmentation. The policy rollouts don't seem to panic the Nokia's
anymore ;) Both the 4185 and 4188 SR clients have having problems over
high bandwidth connections (T1's). We're seeing 8-12 minute logins as
we were experiencing 1.5 - 2 minute logins until SP5.
-----Original Message-----
From: Mailing list for discussion of Firewall-1
[mailto:[email protected]]On Behalf Of Kevin
Martin
Sent: Thursday, October 11, 2001 5:52 PM
To: [email protected]
Subject: Re: [FW-1] IP Pool NAT for SecuRemote users with LinkSys
Routers
Does your Terminal Servers need to be able to do reverse name resolution
and
have you assigned dummy names to the addresses in the "pool" range?
Kevin Martin [email protected]
Stafford Trading Inc. Chief Security Officer
Chicago, IL 60604 TEL230 S. LaSalle, Ste. 688
-----Original Message-----
From: Orr, Paul [mailto:[email protected]]
Sent: Wednesday, October 10, 2001 10:54 AM
To: [email protected]
Subject: [FW-1] IP Pool NAT for SecuRemote users with LinkSys
Routers
We turned on IP Pool NAT for our SecuRemote users recently and it worked
like a champ, with the exception of our LinkSys router users.
With IP Pool NAT enabled the LinkSys users are able to get to our
windows shares, as well as open Outlook and attach to Exchange. What
they can no longer do is access any of our Terminal Servers. We turned
off the IP Pool NAT and we regain access to the Terminal Servers. It's
confusing, because it's only the Terminal Servers that drop out. I
would have thought that everything would stop working.
Any insight would be greatly appreciated.
Thanks,
Paul Orr
[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
========================================================================
========
===============================================
To unsubscribe from this mailing list,
please see the instructions at
http://www.checkpoint.com/services/mailing.html
===============================================
|
|
