Xref: utzoo comp.protocols.tcp-ip:16077 comp.protocols.tcp-ip.ibmpc:5821 comp.protocols.misc:1281
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!ucdavis!csusac!sactoh0!jaj
From: jaj@sactoh0.sac.ca.us (Jelle A. Jorritsma)
Newsgroups: comp.protocols.tcp-ip,comp.protocols.tcp-ip.ibmpc,comp.protocols.misc
Subject: Running TCP/IP on Novell workstations(Netware 3.1)
Keywords: TCP/IP
Message-ID: <1991May13.171033.8038@sactoh0.sac.ca.us>
Date: 13 May 91 17:10:33 GMT
Organization: Sacramento Public Access Unix
Lines: 32

We are starting a project to network our Novell workstations to
other hosts(Unisys A-series,IBM AS400, Unix servers,etc) via
TCP-IP. We've got an evaluation package from FTP and all we want to
do initially is just to tie in two stations on the Novell network
thru TCP/IP. We are able to bring up just the TCP/IP on the
stations or just Netware but not both(which is our goal). The
ethernet cards we are using are ne2000 and we have ne2000 packet
driver. We also have gone thru the SHGEN to generate a new IPX
shell. Listed below is what's in the autoexec.bat:
REM NE2000 using IRQ=5, I/O=320h 0h320h
ne2000 -n 0x60 0x05 0x320h 
ipx
NET3  

Everything loaded fine, until net3 which returns File Server not
found.
Supposedly, the ne2000 packet driver's -n option would allow it to
deal with the 802.3/Ethernet II(used by TCP/IP) without
reconfiguring the server. FTP's suggestion was that I try
reconfiguring the LAN driver on the server to recognize the two
protocols. Unfortunately, the cards we are using in our servers do
not support ETHERNET II. 

Has anybody out there encountered this problem and found a solution
without reconfiguring the server???
All help would be greatly appreciated!!! 


-- 
---------------------------------------------------------
=======jelle jorritsma======jaj@sactoh0.SAC.CA.US========
---------------------------------------------------------