From: "Rodney Gustafson" 
Subject: BorderManager Setup
Date: 1999/02/01
Message-ID: #1/1
NNTP-Posting-Date: Mon, 01 Feb 1999 22:30:36 PDT
Newsgroups: fido.novell

Had an interesting problem today.  I went to setup BorderManager for the
first time.  This is going into an environment with a Netware 5.0 file
server, Groupwise 5.5, and NT 4.0 Workstations.  The BorderManager machine
will be a runtime 4.11 on a Compaq box.  2NIC's - one Compaq on Mainboard,
one 3Com 905B-Tx.  One of these cards will connect to the LAN, with a
static, non-internet routable IP address.  The other card will connect to a
DSL "modem".

Ok, so I installed the runtime 4.11 server on this box, got the nics
configured, could ping internal and external ip's from the Compaq machine.
Then i installed BorderManager, and so began the downward spiral.  Once the
installation was complete, or somewhere along the way, both NIC's got hosed.
Neither would function properly, and both claimed hardware
conflicts.....couldn't connect to NDS, couldn't sync the time, couldn't even
LOAD ping.nlm, much less get a response.  Downing and rebooting did nothing.
Even went so far as to remove the Wan NIC to see if the Lan NIC would then
work.

I have since rebuilt the Compaq with the runtime 4.11 installation, and have
it functioning without BorderManager installed.  I'm uncertain whither I hit
some wierd fluke last time, or whether this is a known problem with a
resolution, or whether I did something painfully obvious to an experienced
BM person.

Any ideas would be very appreciated.

Rod Gustafson
Data Management Consultants, Inc.
rod@dmcwest.com