ppascoe@bjudev.UUCP (Phillip Pascoe) (05/06/91)
Hello,
I recently received Netware 386 3.11 and am having difficulties in
getting it to pass IP packets even after reading the TCP/IP supervisor's
guide. I have been using FTP Software's PC/TCP product along with the
NE1000 packet driver interface to work with a UNIX box located on the same
network as the Novell file server and both coexisted fine. I set the 3.11
software up on a temporary machine to learn about it before putting it in
production. My setup looks like this logically:
3.11 server
A NE2000 ip=192.88.127.50
B NE2000 ip=192.88.127.51
On side A
UNIX host ip=192.88.127.1
PC WS 1 ip=192.88.127.3
On side B
PC WS 2 ip=192.88.127.52
PC WS 3 ip=192.88.127.53
My AUTOEXEC.NCF looks like this:
file server name TEST
ipx internal net 850
load NE2000 port=300 int=2 frame=ETHERNET_802.3
bind IPX to NE2000 net=999
load NE2000 port=320 int=3 frame=ETHERNET_802.3
bind IPX to NE2000 port=320 int=3 frame=ETHERNET_802.3 net=851
load NE2000 port=300 int=2 frame=ethernet_ii name=ip2000
load NE2000 port=320 int=3 frame=ethernet_ii name=ip2001
load tcpip forward=yes rip=yes
bind ip to ip2000 addr=192.88.127.50
bind ip to ip2001 addr=192.88.127.51
mount all
The problem is that no IP packets are getting from side A to side B, I can
PING from PC WS 2 to 192.88.127.51 but not to 192.88.127.50 (ARP fails). I
can PING from PC WS 1 to 192.88.127.50 but not to 192.88.127.51. I can
PING from PC WS 1 to UNIX host, but PC WS 3 cannot. I feel that the IP
router in 3.11 is not routing the IP packets. I have tried various
combinations of the load parameters for the TCPIP.NLM and for BIND to no
avail. I used the example network files found in /etc/examples and removed
the internet example names that did not apply. What part of the manual did
I miss? Any thoughts would be greatly appreciated. Please email
responses. Thanks.
--
-----------------------------------------------------------------------------
Phillip Pascoe Bob Jones University Greenville, SC
uunet!bjudev!ppascoe Opinions are my own.
-----------------------------------------------------------------------------skl@wimsey.bc.ca (Samuel Lam) (05/07/91)
I think you need a separate IP network number on each side of the 3.11 server. i.e. The class C network number 192.88.127 can only be used on one side, you will need to get another (new) class C network number for use on the other side. ...Sam -- <skl@wimsey.bc.ca> -- <skl@wimsey.bc.ca>