Message-ID: <67BAFB085CD7D21190B80090273F74A45B7D29@emwatent02.meters.com.au> From: "Da Silva, Joe" To: "'opendos AT delorie DOT com'" Subject: RE: Information on networking with drdos Date: Fri, 3 Nov 2000 15:33:55 +1100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Reply-To: opendos AT delorie DOT com OK, thanks for that Sho. Your assessment of our IT people is sadly accurate - or to be more precise, it's kind of what I suspected, but then I really don't know enough to make such a judgement ... So basically, the Novell Client 32 software, although it also has TCP/IP capability, cannot talk to an NT LAN using TCP/IP ... sad! Yes, I currently use the M$ Client for DOS stuff to access the LAN, however, as I indicated in another thread earlier (about NetWare), this uses much more memory than I would like (basically, I end up with no UMB space left), whereas the Client32 stuff I had used (with NetWare) lived in extended memory (and was better behaved as well). This means that normally I have to start "Basic" services only - "Full" services (eg. e-mail) chews up conventional memory as well ... and as for the pop-up to tell me of incoming mail, forget it, that's even more memory wasted! As for doing stuff with the server, not only is that beyond my level of expertise, but I'm not one to go fooling around where I don't belong. And as for getting the IT people to change stuff, the "politics" of this place are such that any future network problem would then be blamed on this - ie. me! Regards, Joe. > -----Original Message----- > From: Sho NAKAGAMA [SMTP:nakagama AT email DOT njin DOT net] > Sent: Friday, 3 November 2000 1:42 > To: 'opendos AT delorie DOT com' > Subject: RE: Information on networking with drdos > > > Assuming you mean the Novell client accessing the NT LAN, no, unless > you've purchased "NT Gateway Services for Netware" and they've installed > it on their NT server (which btw allows access to both netware and NT > resources from either a netware or nt only client). > > You could use MS Lan Manager for DOS (I'm not even so sure it's still > availible) which allows access to the NT side of stuff (only). > > There is as far as I know, no known way under DOS to access two services > which use the same basic protocol, unless you use two network cards, and > after all that was said and done with the like 2k of free conventional > memory you'd be left with..shall we say why bother. > > Why your "IT" people would ever even have bothered to try is a good > question for your HR people. Thats not "next to nothing about DOS" thats > "next to nothing about networks and servers." > > I can think of several schemes to make it work, most of which would be > unstable (as in less stable than the NT server to begin with). > > The top suggestions in a nutshell? (in order of probable stability) > > 1) Find a copy of Lan Manager for DOS, and accept that it kinda sucks, and > that depending on the NT server's setup, it may not run at all (MS, as we > all know, doesn't support DOS). Hopefully your NT people are well versed > in the earlier versions of the LAN Manager protocols (especially encrypted > password exchange) > > 2) Install Gateway Services on the NT server (caution though that this is > really intended to give NT clients access to Netware resources, not the > other way around). > > 3) Install Linux, do your DOS stuff in a DOSEMU session (works suprisingly > well btw...hey runs Wordperfect and Doom) then you can access whatever the > linux OS can see (which is pretty much about everything). Works best when > you have a second network card for DOS, as well as a seperate HD (doesn't > need to be big though, just something DOS thinks it owns). > > 4) Find an extra machine, install Caldera Open(fill in one of their linux > dists) get the 3 license version of their Netware 4 compatible server and > using SMB, mount the NT shares and then reexport them with the Netware > server. > > 5) Sneak in late at night and and reinstall Netware on all the servers. > > > Sho > > > On Thu, 2 Nov 2000, Da Silva, Joe wrote: > > > As a mere network user, there's much I don't understand about these > > networks. So perhaps you (or someone else on the list) could tell me > > if it's possible to use the Novell Client32 for DOS stuff on a Windoze > > NT LAN (TCP/IP)? > > > > You see, a few months ago, the Microserfs in charge decided to scrap > > our little Novell 4 network and integrate it and a couple of other > little > > networks (of various flavours) into a larger NT network. The IT people > > (who know next to nothing about DOS stuff), tried at the time to get > > the Client32 stuff to work with the NT LAN, but were unable ... :-( > > > > Regards, > > Joe. > > > > > -----Original Message----- > > > From: Sho NAKAGAMA [SMTP:nakagama AT email DOT njin DOT net] > > > Sent: Thursday, 2 November 2000 3:30 > > > To: opendos AT delorie DOT com > > > Subject: Re: Information on networking with drdos > > > > > > > > > Actually you can just download the last dos/win client (2.71 I > > > believe) and it comes with tcpip.exe , iptunnel.exe and what not. 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) > > > > > ---- snip ---- > > > > ------------------------------------------------------------------------- > Rutgers University Library Systems > > Member > NJIN - New Jersey Inter-campus Network > GDC - GateDaemon Consortium Research Programmer > ------------------------------------------------------------------------- > GBH(tm) KoX ARSCC FDFNet (irc.gbhnet.org) >