[comp.protocols.tcp-ip.ibmpc] SUMMARY OF RESPONSES: NOVELL/TCP-IP/PACKET DRIVER

daved@usperb.Dayton.NCR.COM (Dave Dresselhouse) (07/16/90)

Thanks to all who responded to my question concerning NETWARE and the
Packet Driver coexistance. A summary of the responses follows:

Frances Selkirk  (fks@vax.ftp.com)
                 Suggested installing a second interface card in the
                 server, and configuring it to 8137 protocol with
                 econfig. This would leave the first card as 802.3
                 allowing access from other workstations as normal.

Keith Brown      (keith@novell.com)
                 Assuming that the IPX.COM on the workstation is a
                 "stock" model, it should be "econfig"able. If after
                 running econfig on the Server, the Packet Driver
                 doesn't work, then econfig IPX.COM so that the
                 workstation talks 8137. Using the econfiged IPX.COM,
                 econfig the Server to put it back to 802.3.

John Breeden     (netcom!jbreeden@apple.com)
                 Suggests three potential problem areas that may be the
                 cause of NET3 hanging:
                     (1) Hardware/Software configuration conflict or
                         misconfiguration.
                     (2) Weird PC architecture in the BIOS or memory
                         management area.
                     (3) Bad Packet Driver or BYU Shell code.
                 John also mentioned that the PD software that FTP
                 Software distributes is an older version (5). Version
                 6 can be obtained from sun.soe.clarkson.edu.

                 (mrichey@orion.oac.uci.edu)
Mark Eggers      (meggers@mothra.nts.uci.edu)
                 Outlined the procedure to make a backup copy of the Netware
                 OS. If the workstations get locked out of the Server due
                 to the econfig to 8137, then boot the Server from the
                 backup to put everything back the way it was.
                     (1) Boot the Server with DOS.
                     (2) Put in the backup copy of net$os.exe.
                     (3) Start the Server.
                     (4) Mark net$os.exe sharable and copy it to the Server's
                         hard disk.
                     (5) Mark net$os.exe nonsharable.
                     (6) Down the Server.
                     (7) Re-boot the Server.

Dave Cohen       (cohend@dg-rtp.dg.com)
Alan Strassberg  (alan@oetl.scf.lockheed.com)
Joe Doupnik      (JRD@cc.usu.edu)
                 Suggested making a copy of net$os.exe on a floppy, and
                 running econfig on the copy. If the PD software fails,
                 just re-boot the Server from the hard disk and everything
                 will be as it was.

And Last, but not Least:
Todd Tannenbaum  (tannenba@cae.wisc.edu)
                 Provided a modified version of the NE1000 packet driver
                 that converts between 802.3 and 8137 protocols on-the-fly.
                 Using this code on the workstation removes the requirement
                 to modify anything on the Server. This is the approach I
                 took - and everything works like a champ!

Once again, thanks to all who responded!

-------------------------------------------------------------------------------
Dave Dresselhouse                          dave.dresselhouse@Dayton.NCR.COM
NCR Corporation, U. S. Group
Dayton, OH
-------------------------------------------------------------------------------