RE: FW1 on NT and setting the external interface

["Joe Ippolito" <joe () joesnet com>]

All you need is the name of the NIC.  Do an ipconfig and copy the text for
just the NIC name.  For example:

C:\>ipconfig

Windows NT IP Configuration

Ethernet adapter E100B1:

        IP Address. . . . . . . . . : 1.0.0.1
        Subnet Mask . . . . . . . . : 255.0.0.0
        Default Gateway . . . . . . : 1.0.0.2

Ethernet adapter E100B2:

        IP Address. . . . . . . . . : 2.0.0.1
        Subnet Mask . . . . . . . . : 255.0.0.0
        Default Gateway . . . . . . :

If the external interface has the 1.0.0.1 address on an Intel Pro 100b you
would simply put nothing but "E100B1" in the external.if file without the
quotes.  If it was the third 3COM 3c905 it would look something like "El903"
(I believe).  The gotcha on the 3COM is that it is a lower case "L" not the
number one.  That is why I say to copy and paste it just like you probably
do with Check Point's license keys.  That is if you are a less than perfect
typsit like me.  :-)



-----Original Message-----
From: owner-firewall-wizards () lists nfr net
[mailto:owner-firewall-wizards () lists nfr net]On Behalf Of Thomas Crowe
Sent: Tuesday, August 17, 1999 5:07 AM
To: Firewall-Wizards@Nfr. Net
Subject: FW1 on NT and setting the external interface


I have a NT 4.0 server running FW1 and keep getting messages about not
enough client licenses. I have traced this to not having the external
interface set. However when I create and edit the external.if in $FWDIR/conf
I still get the same problem.  I have tried all of the following formats for
naming the interface:  The NT name (Cpqnet01), the FW bound name
(FW-Cpqnet01), the name assigned to it in the gateway properties (External),
I believe I even tried the IP address. All to no avail.  Another part of
this is that I ma protecting my internal LAN from multiple external
wans/lans so how do I also assign multiple external interfaces in the
external.if

Thomas Crowe
Production Network Systems Administrator
BellSouth Online