home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.os2.networking
- Path: sparky!uunet!utoday!news
- From: ehall@cmpny.sscnet.ucla.edu (Eric Hall)
- Subject: Re: TCPIP 1.2.1 with Lan Manager
- Reply-To: ehall@cmpny.sscnet.ucla.edu (Eric Hall)
- Organization: Network Computing Magazine
- Date: Sat, 07 Nov 92 21:46:40 GMT
- Message-ID: <1992Nov07.214640.22551@utoday.com>
- References: <73591@hydra.gatech.EDU>
- Sender: usenet@utoday.com (Usenet News Administrator)
- Lines: 19
-
- > For the most part I am using the NDIS drivers that came with LanMan 2.1
- > rather than the set that came with IBM TCP/IP. I haven't checked the
- > rev levels of the NDIS drivers that came with each. But each will work
- > individually with the LanMan supplied NDIS drivers.
-
- Try using just IBM's stack, with LAN Manager's REDIR.IFS. This probably won't
- work if you have to go back and add the LM atalk stuff or other dealies, but it
- might isolate it down. If you can get the IBM stack working, and then get lanman
- on top of that, and *then* get TCP/IP stuff going...
-
- Just a thought. BTW, I could never get it going here either. IBM sez they've
- got customers that do it, but it's not a supported config (go figure), and
- wouldn't give us names.
-
-
- Eric Hall
- Dir, East Coast Labs
- Network Computing Magazine
- 516-562-5288
-