I'm wondering how he is configuring the interface to the OS in question. I'n windows OS' this is done via one of the control panels <network>, It's not done from the commandline as it can be in unix and unix-like OS'. If he;s not seeing the interface, I'm suspecting that he has not done the prepetory work as you mention here and perhaps does not understand the underpinnings of the OS in question. Just a guess...
Thanks, Ron DuFresne On Wed, 2 Jan 2002 [EMAIL PROTECTED] wrote: > > > > --__--__-- > > Message: 2 > Date: Sun, 23 Dec 2001 21:55:57 -0800 > From: "vishwas asemend" <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: One Simple Question > > Hi Gurus > > It's very simple question and i don't know it's firewall question or > win2000 and if it's win2K ques then Please forgive me ..... > > I was trying to install checkpoint FW1 on WIN2000 advance server with > limited license (25-50 users) > I have installed the firewall but in the FW configuration we have to give > "name of external i/f" so i went in command prompt and typed > "ipconfig" ...but to my surprise the interface name was not there by > default..so i have tried with all 2000 machines i am having but it din't > show the interface name and i have tried all possible options of ipconfig. > Then i have tried in NT machine and YES, it's there by default. > > After that I have given the interface name since my NT and 2000 NIC's are > same of DLINK. so by seeing on NT I have given the interface name on 2000 > but I was not able to install the rulebase since no bindings was there > between interface name and ip addr. > > I think some registry settings are there to set up and bind the interface > name with ip??? > > can anyone guide me in this particular case ???? > > Thanks in advance > > Regards > Vish > > > Hi Vish... > > I read over your issue and have a couple ideas to throw at ya. First, > before you install Checkpoint make sure that the machine your installing on > is properly networked. Be sure to turn IP forwarding on between the NIC's. > Send out a ping or something on each network to be sure that you can > communicate with each respective network. > In WIN 2000, to get the interface name, try the ROUTE command: c:/>route > print > This will give you your routing tables and Interface names. Here's an > example > > C:\>route print > =========================================================================== > Interface List > 0x1 ........................... MS TCP Loopback interface > 0x1000003 ...00 00 76 4e ea f9 ...... EL5560 3Com 10/100 Mini PCI Ethernet > Adapter > 0x1000004 ...00 b0 d0 a6 86 64 ...... EL90BC7 3Com EtherLink PCI > 0x1000005 ...00 00 83 62 44 fc ...... el575nd528 FE575 Ethernet Adapter > =========================================================================== > > In this case my outside NIC is the EL5560 > > Then, once you have your "external I/F" name run the CPconfig on the box > and make sure that it's on the External I/F tab (In CP2000). > If your running CPNG, this is not found in CPCONFIG, rather it's defined in > the actual FW object in the policy editor. (Manage/ Network objects/ > Topology) > > Hope this helps! > Good Luck, > Kevin > > > > > > > > _______________________________________________ > Firewalls mailing list > [EMAIL PROTECTED] > http://lists.gnac.net/mailman/listinfo/firewalls > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ "Cutting the space budget really restores my faith in humanity. It eliminates dreams, goals, and ideals and lets us get straight to the business of hate, debauchery, and self-annihilation." -- Johnny Hart ***testing, only testing, and damn good at it too!*** OK, so you're a Ph.D. Just don't touch anything. _______________________________________________ Firewalls mailing list [EMAIL PROTECTED] http://lists.gnac.net/mailman/listinfo/firewalls
