Checkpoint FW-1 does not scan traffic originating from a modem. One way
of handling this is to install a terminal server/modem pool that has some
security features to observe traffic originating from the modem. The
second approach is to attempt to eliminate all modem transaction based
applications and speak with the vendor to see if the applications are
compatible with a modem pool or a modem server.
If you are accessing IBM Advantis/Mainframe network, IBM acquired IVANS a
while back which distributed a product called IBM Passport. IBM Passport
has both Async and TCP/IP options available. It works quite well with a
modem server for the Async portion and the TCP/IP addresses are routeable
through a commercial firewall.
If you are accessing legacy mainframe application through dial-up modems,
there are some common transparent modem shims available that work with
some of the medium sized modem servers. Basically the modem shim is an
application that is installed on the pc that tricks the pc in thinking a
physical modem is still attached. In other words, a Communication port
redirector.
Before scenario:
After scenario:
Modem Shim application resides on the Client PC.
Most of the common modem shim applications can utilize NT Authentication
databases, which provides authentication and authorization. If
implemented correctly, you can also log to a central system logging
facility.
Hope this helps,
/mht
"McEve" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
02/20/00 09:21 AM
To: <[EMAIL PROTECTED]>
cc:
Subject: Firewall1 problem
Hello
Typical scenario is this:
A LAN, connected to the internett through a leased line, Firewall1
installed
to scan all traffic going through the leased line. Some workstations also
have modems installed. Is it possible for Firewall1 to pick up and scan
the
traffic from and to the workstations when they connect using the modem,
through a different line?
background for my question:
I do support for an application that connects to a mainframe for data
transfer. This application will not be able to communicate with our host
if
there is a proxy or firewall between the client and our host, so they use
the modem to connect instead of the leased line. However, some customers
are
still unable to connect to the mainframe, and upon further investigation,
we
find a route in the routingtable pointing out host straight to the IP of
the
firewall.
I don't know Firewall1, and can't find an answer to how this route
appears,
effectively causing the communication to the mainframe to fail. Anybody
with
knowledge of firewall1 that can expain to me how we can avoid this route
being created in the route table? Configuration in Firewall1? or with the
client?
Any help would be great
thank you
Eve
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
