Article View: comp.os.os2.networking
Article #605Re: ODINSUP problems
From: Nick Holford
Date: Tue, 01 Sep 1992 05:35
Date: Tue, 01 Sep 1992 05:35
25 lines
1577 bytes
1577 bytes
>In article <5306@blue.cis.pitt.edu.UUCP>, sillett@edc3jr.gsph.pitt.edu (Robert >L. Sillett) says: >> >>I've configured IBM's TCP/IP 1.2.1 to run along with the Novell >>Requester on the same NIC (3C503) using ODINSUP. It works great -- >>for 90 or seconds. Then all the TCP/IP+NFS functions stop working. I >>know that this is a known problem to IBM & Novell; however, is it a >>problem with the 3COM drivers or with the software? I just got ODINSUP installed yesterday and had the same problem with a NE2000 NIC i.e. TCP/IP works for a minute or so then dies. Anybody got a solution for an NE2000? Of course to get that far I had to learn that Figure 6.1 p 6-4 in the NW Requester manual has the sequence of ODINSUP.SYS and NE2000.SYS reversed so that the CONFIG.SYS as illustrated doesnt work! (Thanks to hamish@waikato for getting me out of that one) BTW why does NW spell it requestER and IBM spell it requestOR (TCP/IP docs). Does Novell, er, know how to spell, or, did IBM get it right? -- Nick Holford, Dept Pharmacology & Clinical Pharmacology University of Auckland, Auckland, New Zealand INTERNET: n.holford@aukuni.ac.nz
Technical Details
Message-ID:
<1992Sep1.053518.6409@ccu1.aukuni.ac.nz>Path:
arc1-ca.pugleaf.net!sparky!uunet!wupost!waikato.ac.nz!aukuni.ac.nz!nholfordReferences:
<5306@blue.cis.pitt.edu.UUCP> <92244.093804U37127@uicvm.uic.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!wupost!waikato.ac.nz!aukuni.ac.nz!nholford Newsgroups: comp.os.os2.networking Subject: Re: ODINSUP problems Message-ID: <1992Sep1.053518.6409@ccu1.aukuni.ac.nz> From: nholford@ccu1.aukuni.ac.nz (Nick Holford) Date: Tue, 1 Sep 1992 05:35:18 GMT References: <5306@blue.cis.pitt.edu.UUCP> <92244.093804U37127@uicvm.uic.edu> Organization: University of Auckland, New Zealand. Lines: 25