Mail Archives: opendos/2000/11/01/13:39:16
> Actually you can just download the last dos/win client (2.71 I
> believe)
That's the latest Client32, yes. Will those drivers work with the 16-bit
ODI stack though? The Client32 comes with a 16<->32bit shim, so they might
well.
> and it comes with tcpip.exe , iptunnel.exe and what not.
You can get TCP/IP.EXE from Lineo's FTP server as well. It's also in an
update to LAN Workplace in Novell's File Finder, but that probably requires
one to have a LWP licence.
> You
> probably need to use nwip.exe but it's apt to be very slow starting up
> during its search for a DSS server (I suppose you could just set the DSS
> server to 127.0.0.1 so it times out quicker)
NWIP has a tendency to be nasty - at least, it did when I used it. I tried
NWIP and IPTUNNEL, neither of which worked brilliantly, so I stuck to
running Intranets on TCP/IP and the NetWare on IPX/SPX on the same network.
> I never ran PNW, I know the client would almost certainly work, but I'm
> not so sure about the server aspect, because at some point (with any of
> the encapsulation schemes) something has to strip out the IPX packets from
> the ip frames. I don't know if nwip.exe will do that, normally it's the
> nwip.nlm on the novell server which does it.
Well, it must do (at least some of the time) - it encapsulates the IPX in IP
to send to the server, the server processes the request and replies in the
same manner, so the client then needs to retrieve the IPX packet.
> I guess you can always just
> try pointing the two machines at each other and see what happens.
It might work. I doubt there'd be any support for it, so you'd be on your
own.
> I've only use iptunnel for server-server connections, so again I don't
> know if you can say take two pnw machines, point their iptunnel's at each
> other and make it work.
Again, I don't see any reason why it wouldn't work - but it might be slow
enough to warrant using plain IPX/SPX.
> webspyder alone won't work because you need a working ipx subsystem which
> will only happen if you load something which looks to the vlm's as a real
> ipx device.
Well, the WebSpyder package I have includes a REMOTE.EXE (which does PPP
over a modem and installs itself as an MLID in the LSL), PKT2ODI (which
takes packet driver requests and passes them to the ODI stack), and then the
normal VLMs on top of that. You can replace REMOTE.EXE with any other
MLID - I have an EtherLink III in that machine, so I used 3C5X9.COM - and
it'll work over a local network. Most of those MLIDs come with DR-DOS, or
can be found for a few Kbs downloaded from the manufacturer.
[On Novell - the message I sent agreeing with this arrived an hour and a
half after the others I sent at the same time...]
> BTW, Novell support is expensive, so is Netware, so is hiring a CNE. If a
> netware admin needs to call support more than 1 or 2 hours a year, he
> should be replaced.
Especially with the amount of help you can get for nothing on the 'net.
I've never needed to call support, for just that reason.
> If you want to make the argument that say the 3.12 -> 3.2 upgrade is a bug
> fix (which it mostly is) which is very expensive (which it relatively is)
It's about 30 UKP for the CD-ROM, last time I checked. I think you can just
pay that if you're doing a straight 3.12/x -> 3.2/x upgrade. Otherwise, you
need the licenses on top of that (e.g. 3.12/25->3.12/50, which I needed last
year, was around 5,000 UKP).
> and should really be just downloadable to any site running any legal copy
> of netware 3, then I'll agree with the extorsion comments.
It is freely downloadable - apart from SYSCONW, which is hardly an essential
tool. 3.2 is basically the minimum patch list for 3.12 (the majority of it
is in the files 312PTD.EXE, LIB312.EXE, NWPAUP1A.EXE, IPXRTR.EXE, ODI33G.EXE
and possibly a few more, with the rest being in the File Finder under
NetWare 3.12). The only real difference between a 3.2 CD-ROM and a set of
ZIP files from support.novell.com is that the CD-ROM has a PINSTALL.NLM so
you can install it in INSTALL.NLM->Product Options, and it's all automated
(whereas the others are basically unzip to directory, copy to SYS:, then
LSWAP LOADER.EXE SERVER.EXE).
Regards,
Ben A L Jemmett.
(http://web.ukonline.co.uk/ben.jemmett/, http://www.deltasoft.com/)
- Raw text -