home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.novell
- Path: sparky!uunet!spool.mu.edu!uwm.edu!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!iguana.cis.ohio-state.edu!cantor
- From: cantor@iguana.cis.ohio-state.edu (scott eric cantor)
- Subject: Windows for Workgroups + Netware
- Message-ID: <1992Dec21.182325.4304@cis.ohio-state.edu>
- Sender: news@cis.ohio-state.edu (NETnews )
- Organization: The Ohio State University Dept. of Computer and Info. Science
- Date: Mon, 21 Dec 1992 18:23:25 GMT
- Lines: 23
-
- Our group has a couple copies of WfW to play around with, and I was
- wondering if anyone else had had problems using their IPX over NDIS module.
- I've gotten a modicum of Netware support using ODINSUP to run the NetBEUI stack
- while using ODI for Netware, but WfW doesn't really "know" that I'm attached to
- Netware. My problem at this point is that I can't afford to switch to an NDIS
- driver, because I need TCP/IP over ODI.
- To that end, I've experimented with Microsoft's bundled MSIPX stack,
- but NETX hangs when I try to connect. I've checked the PROTOCOL.INI file
- thoroughly, and I'm sure I've changed every reference to an NDIS driver to
- X3C503 for the 3Com ODI driver. Everything loads without errors, until I
- try to connect.
- If anyone has any experience with this, drop me a line. Thanks...
-
-
- [-------------------------------------------------------------------------]
- [ Scott Cantor UNIX is a small, fast, efficient ]
- [ Ohio State University operating system upon which every ]
- [ Columbus, Ohio graduate student in the universe has ]
- [ played pin the tail on the donkey. ]
- [ cantor@cis.ohio-state.edu ---- a UNIX guru ]
- [-------------------------------------------------------------------------]
-
-
-