Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!cs.utexas.edu!uunet!mcvax!sunic!kth!draken!ttds!perand
From: perand@ttds.UUCP (Per Andersson)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Novell and TCP/IP
Message-ID: <1237@ttds.UUCP>
Date: 19 Aug 89 00:58:26 GMT
References: <55684@tut.cis.ohio-state.edu> <18985@mimsy.UUCP>
Reply-To: perand@ttds.UUCP (Per Andersson)
Organization: The Royal Inst. of Techn., Stockholm
Lines: 27

In article <18985@mimsy.UUCP> chenn@tame.cs.umd.edu (Jenn-San Peter Chenn) writes:
>
> I would like to make more infomation about tcp/ti on ibmpc. With or 
>W/O Novell. What HW or SW do I need? Who is selling them ? Thank you.


One thing you might want to try is using a packet driver ( See packet driver 
announcements ). This allows you to let your own PC run both IPX and , for 
example NCSA Telnet simultanously ( is my spelling correct ? ). You have
to get a special version of IPX from Novell of course. And you might have to
change the drivers on the server too. I think you have to have the type-field/
length field in the ethernet frames set to 8137, which is assigned to Novell.
In some versions of Novells drivers the field is interpreted as a length field
( that's 802.3 i think ). In this case you can run applications which support 
packet driver from your local disc. If you run them from the server you will 
need a server that support RARP or something equal. This because if you, 
as you can do in NCSA Telnet, put a fixed IP-number in a configuration file, 
all clients starting the program will get the same IP-number. BANG - goes your 
network. I have been running this configuration for a couple of weeks and it
has been working really well.

Per
-- 
Per Andersson
Royal Institute of Technology, Stockholm, Sweden
perand@admin.kth.se, @tds.kth.se, @nada.kth.se 
or perhaps {backbone}!sunic!ttds!perand