TCP/IP Routing
Mark K Hall
with a class "A" liscense of 69.0.0.0 with a subnet of ff.ff.0.0.
I have three cards binded with the names IP_SALES, IP_OPCS, and
IP_TECH and will refer to the nets with the name following the
underscore.
Initially when I set it up SALES was on a 69 net and OPCS was using a
real class "C" liscense before we moved behind the firewall and our
stations could connect through the server to our Unix boxs on the
OPCS net with no problems. Now that we have moved the OPCS to a 69
address, the clients on the SALES net can no longer ping/telnet to
any station on the OPCS net...but I seem to be able to ping from the
OPCS net to any station on the SALES net.
I'm running all the latest and greatest client files and I have Novell's
TCPIP.NLM loaded at the server...the following IP related autoexec.ncf
commands follow:
LOAD C:3CX89 SLOT=3 FRAME=ETHERNET_II NAME=IP_SALES
LOAD C:3CX89 SLOT=4 FRAME=ETHERNET_II NAME=IP_OPCS
LOAD C:3CX89 SLOT=5 FRAME=ETHERNET_II NAME=IP_TECH
LOAD SNMP
LOAD TCPIP FORWARD=YES RIP=YES
BIND IP TO IP_SALES ADDR=69.1.1.0 MASK=FF.FF.0.0
BIND IP TO IP_OPCS ADDR=69.2.1.0 MASK=FF.FF.0.0
BIND IP TO IP_TECH ADDR=69.3.1.0 MASK=FF.FF.0.0
I'm also only using Novell's TCP client files as a stack only, I run
third party apps for telnet, but I don't think software and clients
have anything to do with my problem. Also I'm using Novell's DOS
ping command to test with to keep it simple. The NET.CFG file has
all the appropriate lines for TCP/IP and the stations point to the
server NIC as the router.
Please help!
Lennart Regebro
>BIND IP TO IP_SALES ADDR=69.1.1.0 MASK=FF.FF.0.0
>BIND IP TO IP_OPCS ADDR=69.2.1.0 MASK=FF.FF.0.0
>BIND IP TO IP_TECH ADDR=69.3.1.0 MASK=FF.FF.0.0
Beware that not all drivers seem to be able to handle addresses with 0-bytes
in it. I have had similar problems with that. Try using addresses 69.1.1.1,
69.2.1.1 and 69.3.1.1 instead.
--
Lennart Regebro <Lennart...@scs.no>
Moderator of comp.os.netware.announce.
Send mail to cona-r...@scs.no for more info.