Re: [FW1] NIC problem with WIN2k

["Neo" <checkpoint_guru@FW1-NOSPAMhotmail.com>]

What's really wierd about the whole thing, is IF you have a CD that has
CPFW1 sp1, then the installation on WIN2k will not work.  It will install,
but you will get nothing but mem dumps and the good ol' blue screens when it
tries to reboot.  I downloaded the zip file from Checkpoint's site for CPFW1
sp2 and installed it and everything worked fine.  So I called our reseller
and requested them to send us a new CD with a newer service pack.  They sent
me the SP2 CD.  I tried to install Checkpoint on WIn2k off of this CD and
NO, it wouldn't install.  So you are correct.  I'm not sure why the Firewall
will install correctly from the zip file from Checkpoints site and not from
the CD media, but I do know it works.  This is something I think checkpoint
might want to look into.

But for exact installtion instructions, i Installed the CPFW-1 sp2 on my
machine.  Upgraded to SP3.  Installed MGMT clients sp2, then upgraded that
to SP3 and everything seems to work fine.  I didn't have to install on NT
first.

Let me know if you need any help...make good backups first!!!!


----- Original Message -----
From: "Jonah Kowall" <jkowall@psteering.com>
To: "Neo" <checkpoint_guru@hotmail.com>; "checkpoint"
<fw-1-mailinglist@beethoven.us.checkpoint.com>
Sent: Thursday, May 31, 2001 10:38 AM
Subject: RE: [FW1] NIC problem with WIN2k


I stand corrected, I believe you are right.  Doesn't the installer for
4.1 complain about windows 2000?  Do you need to install it on NT, run
the service pack for firewall-1, and do an OS upgrade?

-----Original Message-----
From: Neo [mailto:checkpoint_guru@hotmail.com]
Sent: Thursday, May 31, 2001 10:33 AM
To: Jonah Kowall; checkpoint
Subject: Re: [FW1] NIC problem with WIN2k


I beg to differ...

Even in the courseware, it is tought as a new operating system for
CP2000, unless the books are wrong.  I sure hope not, because that would
mean I'm teaching my students the wrong information...

On another note, the firewall runs fine on Win2k, only with a few
problems like the one I had a question about.  I prefer to run it on
Solaris or Redhat, but unfortuanetly, I do not make the final decision
for my company.


----- Original Message -----
From: "Jonah Kowall" <jkowall@psteering.com>
To: "Neo" <checkpoint_guru@hotmail.com>; "checkpoint"
<fw-1-mailinglist@beethoven.us.checkpoint.com>
Sent: Wednesday, May 30, 2001 6:06 PM
Subject: RE: [FW1] NIC problem with WIN2k


You can't run checkpoint on W2k, its not approved, and will not run
properly.  The next version should support W2K.

-----Original Message-----
From: Neo [mailto:checkpoint_guru@hotmail.com]
Sent: Wednesday, May 30, 2001 10:37 AM
To: checkpoint
Subject: [FW1] NIC problem with WIN2k


Hello all,

I have a question for you guys.  Currently my company is using WinNT, CP
FW-1, SP3.  We are migrating to Win2k.  The firewall has 4 NICS, and the
CP license is bound to the NIC facing the internet.  My problem is
this...Under windows 2000, Win2k does not recognize the NIC as being
enabled if the Cable or connection is down (ie. "ipconfig /all = "cable
disconnected")..which means that if our link or connection goes down on
the NIC that the Firewall is licensed to, Windows will not recognize
that NIC.  This means that Checkpoint will not recognize that the
firewall has a license and thus not allowing us to control policy for
traffic flow thought the other 3 NICS.  It will give you the error, "no
license for user interface".

Besides plugging a loopback cable into the NIC if the connection happens
to go down, does anybody have any other suggestions on how to make Win2k
recognize the IP's of the NICs, even if the cables are disconnected?

Thank you,

Aeon





================================================================================
     To unsubscribe from this mailing list, please see the instructions at
               http://www.checkpoint.com/services/mailing.html
================================================================================