
------------------------------------------------------------
NW411.DOC -- 19971211 -- Email thread on (Intra)NetWare 4.11
------------------------------------------------------------

	Feel free to add or edit this document and then email
	it back to faq@jelyon.com




Date: Mon, 21 Oct 1996 15:04:52 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Client for 4.11?

>>That doesn't really make sense.  Why would Novell make the Win95
>>client32 any different for Intranetware (4.11) versus the older versions
>>of Netware.  The client32 found in Intranetware should work with all
>>previous versions of Netware.  The same should go for nwadmin.
>>It would be crazy for Novell to create an nwadmin program in
>>Intranetware that can't also work with Netware 4.1 servers.
>
>Well, you need the new client to run the new NWAdmin and NDSMGR, as told to me
>by our local Novell SE, and they work fine accessing a pure 4.10 tree as well
>as a mixed 4.1/4.11 test tree.  I can't see any reason to believe that the 4.11
>client/nwadmin are incompatible with a 4.10 network, it would be suicide for
>Novell to do this.
>
>>They won't work on it.  4.11 has some changes in its NDS to support
>>some of the Intranetware features (web server, ftp server etc...) .
------------
	If you don't have NW 4.11 then there isn't a need to worry about
the matter. If you do have NW 4.11 then the question has been answered by
simply trying things. If you have NW 4.11 beta then it's not finished and
waiting for the formal release is wisest.
	For those who have NW 4.11 but for some strange reason have not
tried these things:
	Client32 is needed to run ndsmgr (aka: partmgr in GUI clothing) and
nwadmn95 (public\win95, slicker nwadmin), and nwadmn3x (public). Nwadmin is
still present (public) as before. The Client32 material on the NW 4.11 CDROM
is not required per se.
	If you try to run ndsmgr16 (public) under Win31 with VLMs it will
likely hang the machine in a permanent search of the swap file, or so it
occurs here. Since ndsmgr is basically partmgr, hence rarely used, this is
not a problem (or it is not a problem in my own work).
	These items work with NW 4.11, NW 4.10, NW 3.12 servers, but of course
the NDS part applies only to NW 4 servers. Do not discard syscon on NW 3
servers.
	Personally I much prefer VLMs so I can get real work done. Thus
netadmin/partmgr suit my needs reasonably well, and nwadmin is called in
only when block changes are quicker by marking a bunch of items. Each to
his/her own tastes.
	Joe D.

------------

Date: Mon, 21 Oct 1996 19:40:02 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Client for 4.11?

	Additional information on the matter.
	If one loads up the Windows 3 .dll/.386 components from the DOS/Win
Client32 distribution in NW 4.11 then ndsmgr16 and nwadmn3x (see above)
will run ok in Win 3.1 using VLMs. I spent an hour plus this afternoon
checking on this.
	Caution: my poor windows\system directory is so cluttered with
things from goodness knows where, particularly beta test items, that it
is difficult for me to state positively yes or no on some items without
doing a fresh installation of Windows. I have no interest in that lovely
task just to answer a question on the listserver. Hence, please try these
things yourself and maybe educate everyone else with the results.
	Joe D.

------------------------------

Date: Sat, 26 Oct 1996 08:44:44 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Mixing 4.10 & 4.11

>Q1: Is it possible to install a 4.11 server into an existing 4.10
>tree ? any pitfalls ? can DS.NLM 5.01 and 5.70 coexist ?

	Yes, they may be in the same tree and coexist.

>Q2: If so, are there (and would it be possible and wise to use them)
>superior NDS management tools on that 4.11 server, to sort out a problem
>on my tree (illegal and hidden object, prevents me from replicating one of
>the partitions).

	The NW 4.11 client-based tools also work on NW 4.10, and vice versa.
I can't answer problem of illegal/hidden objects, and you may have to call
Novell to get those problems solved.
	Joe D.

------------------------------

Date: Tue, 29 Oct 1996 17:19:53 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Client 32 for DW 2.1 vs 2.11

>Ive just been to ftp.novell.com and saw that there are 2 versions
>of the 32-bit Client for Dos/Win namely cl32dw21 and cl32dw211.
>I went to the new one and went to the webpage and got the TID
>(2915626) and it mentions that it is the same as the one in
>INW / NW 4.11.
>
>We are planning to deploy this throughout our organisation, and
>were wondering if there are any issues using this with our
>existing NW4.10 / 3.12 / 3.11 (all 3.x  to be upgraded to 4.10 first
>then all later to 4.11).
>
>What are the significant differences (bug fixes??) between 2.1
>and 2.11??
----------
	I can't give you a list, but I can indicate a couple of things.
	NW 4.11 is a target as the stable platform with the bugs fixed,
before moving to the next level of file serving techniques. Items long
delayed have been poured in, and as expected, the rules change some here
and there (meaning also the API's change with them). We see the after
effects in recent updates to NW 3.x and 4.1 in say Mathlib and Clib and
lan drivers and disk drivers. Thus Client32 too is evolving to accomodate
the most recent APIs.
	It is my impression that NW 4.00, 4.01, 4.02, and even 4.10 should
be thought of as steps along the path to the 4.11 target, much as happened
in the NW 300 series. That's all I'd like to say on this topic.
	The other thing is be cautious about using Lanalyzer and Client32.
The packet bytes LZFW gets are often overlayed by the next packet, making
the current one only partially correct. I suspect this is a problem only
in the way LZFW gets a look at packets enroute to protocol stacks, and
not what the protocol stacks get. LZFW works fine with VLMs.
	Joe D.

------------------------------

Date: Fri, 1 Nov 1996 14:27:33 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: NetFRAME & nam41 ?s

>>If anybody is thinking of applying this patch, a new version of it was put
>>up on Novell's ftp site within the past few days.  The new instructions for
>>applying the patch are significantly different from the old ones, and you
>>will want to read them before proceeding or you may have serious problems
>>afterwards.
>
>The patch has fixed two big bugs that affected us severely: a) long (+31)
>character files names no longer  crash Macs, and, b) SMS-based backup
>applications can now successfully backup files with double-byte character
>names (for example, Japanese Macintosh file names).
>
>That said, I'm not very eager to have to recreate all my volume in order to
>install the patch. If Novell is recommending this, it raises an interesting
>question: what should we do if upgrading a 4.1 server to 4.11? 4.11's OS2 &
>Mac name space files have the same enhancements as are in the nam41 patch
>set. Do they have the same problems when installed over the old 4.1
>versions? Hmm....
---------
	I suspect the same rules apply: rebuild the volume from scratch
or be sorry later. Given the seriousness of rebuilding NW 4 volumes one
would have hoped for a roll-over utility which tweaked each namespace
entry from old to new form while the server ran without users. Such things
are not difficult to write.
	In the meanwhile, a suggestion is to install 4.11 (a roll-over
affair), backup things to tape, rebuild the volume (be nice to your NDS
superiors), restore from tape. The new TSANDS/TSA410 routines "should"
make this painless, but the proof is in the pudding.
	Joe D.

------------------------------

Date: Sat, 2 Nov 1996 14:07:38 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: NetFRAME & nam41 ?s

>>	I suspect the same rules apply:
>>rebuild the volume from scratch or be sorry later. Given the seriousness
>>of rebuilding NW 4 volumes one would have hoped for a roll-over utility
>>which tweaked each namespace entry from old to new form while the server
>>ran without users. Such things are not difficult to write.
>>	In the meanwhile, a suggestion is to install 4.11 (a roll-over
>>affair), backup things to tape, rebuild the volume (be nice to your NDS
>>superiors), restore from tape. The new TSANDS/TSA410 routines "should"
>>make this painless, but the proof is in the pudding.
>>	Joe D.
>
>Joe, someone had mentioned doing it with DSMAIN...  Is this possible, if so how?
-----------
	Golly, DSMAINT has a full set of documentation which some of us
view as required reading material for NW 4.x admins. It removes directory
services from the server and puts the vitals into an ordinary file, just
as the docs explain. It might work in this case, it might not do what
we want, I have not had the need to experiment.
	There are some fundamental concepts involved here which need to
be appreciated before tinkering. Prior to NW 4.11 backups of material on
NDS volumes was by Object ID number (emphasis on "number") rather than both
name and number. Restoration of names created New Numbers, and objects
kept their old numbers, hence we lost correspondence between names and object
ownerships. NW 4.11 SMS compliant backups are "supposed" to retain both name
and number and reunite them upon restoration. I say supposed to because that's
the design goal, the assurance of the design team (which whom I discussed this
and other matters), but which I have not put to the test here, emphasis on
test here. I am running 4.11/beta, no 4.11/release has appeared here, and
we never fully trust betas.
	Further, NW 4.11 backups are supposed to be very clever and smart
about integrating information back into the tree, rather than simply dump an
old NDS data set on the site and be horribly out of sync. Is your tape backup
software SMS compliant? Because we may not be very sure then we also make
a complete backup with NW 4.11 Sbackup, which is SMS compliant.
	With me so far? Good.
	Why did I say what I did in the next to top paragraph quoted above?
To get the NDS name/number correspondence established and then preserved
to tape, which NW 4.11 can do but 4.10 cannot.
	At this point I would strongly recommend building a test server
upon which to try the steps. I'm fresh out of flat space and power strip
outlets to create yet another server at my place. Thus we have to rely
on others, perhaps your site.
	Finally, after thinking about the situation again last night I
feel even more strongly that Novell should create an in-place-upgrade
utility for this particular namespace change. There are just too many
doubts and failure points rebuilding production machinery running NDS.
	Joe D.

------------------------------

Date: Sat, 2 Nov 1996 16:20:29 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: NetFRAME & nam41 ?s

>>	Further, NW 4.11 backups are supposed to be very clever and smart
>>about integrating information back into the tree, rather than simply dump an
>>old NDS data set on the site and be horribly out of sync. Is your tape backup
>>software SMS compliant? Because we may not be very sure then we also make
>>a complete backup with NW 4.11 Sbackup, which is SMS compliant.
>
>Well I'm still running Netware 4.1.  And Arcserve6 is SMS Compliant
>
>>	Why did I say what I did in the next to top paragraph quoted above?
>>To get the NDS name/number correspondence established and then preserved
>>to tape, which NW 4.11 can do but 4.10 cannot.
>>	At this point I would strongly recommend building a test server
>>upon which to try the steps. I'm fresh out of flat space and power strip
>>outlets to create yet another server at my place. Thus we have to rely
>>on others, perhaps your site.
>>	Finally, after thinking about the situation again last night I
>>feel even more strongly that Novell should create an in-place-upgrade
>>utility for this particular namespace change. There are just too many
>>doubts and failure points rebuilding production machinery running NDS.
>
>Joe,
>If I know that I don't have names longer than 31 characters and I only have
>the Mac Name space added, I shouldn't see any problem or should I?  I also
>just started adding windows 95 machines to the net, and I'm going to add
>the OS2 namespace, in that case I think I'm OK, it's just the mac name
>space...  I have the sys volume duplexed.  I'm thinking of splitting the
>drives, and deleteing the netware partition on one, the recreating it and
>adding the name spaces to it.  Then re-duplexing the drives.  When the
>drives are back in synch, I split them up delete the other partition, add
>the name spaces and re-duplex...  Would that work?
-----------
	Nope. Duplexing is a controller level affair, for the most part,
where one drive is forced to be a copy of another. I don't see that this
attacks the problem of recreating a NW volume with the new mac.nam and
retain the old data's NDS name<->number association. Duplexing is not a
high level file by file copy scheme, it's a low level disk block by block
duplication similar to mirroring. Maybe I missed something in passing.
	The fundamental, deep down, bedrock, problem is retaining the
above association, and the SMS part of NW 4.10 can't do it.
	If you don't have NW 4.11 then my suggestions do not apply and I
wish you success recreating the volumes. Rather than put up with more
speculation from me I suggest folks don their thinking caps, do thorough
backups, cross fingers, and run a few tests. There may be a way through
this obstacle course, but if so it is not apparent to me.
	Joe D.

------------------------------

Date: Fri, 8 Nov 1996 10:24:56 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: NAM41A.EXE namespace upgrade

	Some thought in the clear light of morning:
	Archive file nam41a.exe says rebuild a NW volume from scratch
and add the extra namespace modules afterward. That's scary.
	The problem is the old extra name space structures seem to be off by
one. Ok, understandable. Using the new extra name space structures does not
require rebuilding a NW volume from scratch, however, despite the advice
in the nam41a.exe archive file.
	One first backs up the extra name space files, run Vrepair to
remove those name spaces, install the replacment *.nam files, reboot
the server, ADD NAME SPACE again, restore from tape. That keeps NDS
intact, plus all those ordinary files too. Goodness knows what happens
to the "other" fork of Mac files, but maybe it's all ok in the end.
	Removing extra namespaces by way of Vrepair takes us back to
the same point as if we had never added them or basically as if we had
rebuilt the volume without them. Thus a volume rebuild isn't helping
nor necessary, unless I am missing something fundamental here.
	Upgrading from 4.10 to 4.11 by a rollover does not change the
file system nor disk structure. Thus one needs to get the namespace
material in good shape before upgrading.

	To Novell: I think the docs in nam41a.exe should be carefully
rewritten and reviewed to indicate the situation in plain English and
lead folks though the least destructive upgrade process.
	Joe D.

------------------------------

Date: Tue, 12 Nov 1996 10:55:06 -0500
From: Clay Gibney <GIBNEY@WOODSROGERS.COM>
Subject: Netware 4.11 upgrade

I did my first of three Netware 3.12 to 4.11 (IntraNetware) upgrades
last night and was pleasantly surprised.  Finally, Novell has an
upgrade that actually works well and without pain!.  And the
Netware 4.11 support pack was easy to install too!

The server upgrade had potential for failure as the existing
3.12 server has Btrieve applications, SoftSolutions SEM NLM's,
Groupwise NLM's, and Palindrome backup NLM's.

The only thing that we had a problem with was the Palindrome,
and we have already found the update/patch needed to get it
working again when upgrading from 3.x to 4.x.
And when a Palindrome process abended (which normally
would have halted the whole server), what a pleasant surpise
to see Netware 4.11 only terminate the offending process and
keep on running.

Hurray for Novell.

------------------------------

Date: Mon, 18 Nov 1996 07:52:00 -0500
From: Dennis Large <wdlarg01@homer.louisville.edu>
To: netw4-l@bgu.edu
Subject: Re: IPXRTR

>Would someone briefly explain to me what the IPX NLSP Router (IPXRTR.nlm)
>does in IntranetWare? Do you _need_ it or is it just used for advanced
>routing? Also, what's the equivalent of this in a 3.x environment? Did it
>also exist in 4.1 or is it new to 4.11? Thanks again!

I believe they actually started the project in 3.12, but at any rate I
think retrofits to 3.x are available. What it was designed to do was lower
the network traffic by replacing RIP/SAP with on-request event-driven
updates.

Unfortunately, in short, it's broken. It's not that it breaks the network
or anything, it just doesn't eliminate the traffic as it should,
replacing it with other stuff, and can under certain circumstances even
increase traffic.

No, you don't _need_ it.

------------------------------

Date: Wed, 4 Dec 1996 17:51:42 EST
From: Jayson Agagnier <jaysona@PILS.COM>
Subject: Re: IntranetWare Web server audit trail (fwd)

>Does the Web server keep a log of http usage ?
>
>A customer intend to setup a IntranetWare Web server.  He wants to:
>
>1. keep a record of events such as, how long has someone been surfing,
>how long has the browser been idle, etc.  Purpose is to terminate any
>idle connection & release the locked resources for other users.
>
>2. produce a periodic statistics of the web access usage.

There are three basic logs kept in VOL:WEB\LOGS

They are: Access.log
	  Debug.log
	  Error.log

The contents of the log files can be viewed using the NetWare Web Server
Manager program located in SYS:System\Public and is called WebMgr.Exe.

------------------------------

Date: Thu, 5 Dec 1996 21:08:08 -0500
From: "MICHAEL D. SETZER II" <MICHAEL@GCCCC.GUAM.NET>
Subject: Re: COPYING NETWARE 4.1 LICENSE - (JCMD DIR CAN WORK ON 4.11)

>It works with 4.11, it's just not quite as user-friendly as it used to
>be.  Under 4.11, DIR in JCMD is broken, and NWSHELL is completely broken.
>JCMD's ATTR command is a workable replacement for DIR.

If you do DIR, it doesn't work, but if you do DIR *.*, it does.

Ran into the other night in my Networking class, setup a Server
with our new 4.11, and was showing them JCMD. Dir gave nothing, but
tried DIR *.* and it worked.

------------------------------

Date: Sat, 7 Dec 1996 03:52:51 -0600
From: mark rogowski <markrog@MB.SYMPATICO.CA>
Subject: MPR 3.1 PPP Dynamic Addressing

Does anyone know of, or has anyone written an NLM that will work with
Intranetware MPR to accept a dynamic IP address from an ISP?

Its unfortunate that the current version doesn't support this,
especially since Novell claims they support "small business".

I don't know too many small businesses who will run out, spend thousands
of dollars on Netware, then go out and drop another pile of cash for a
high-speed link for Internet access, because the packaged software
doesn't support an inexpensive method of connection.

------------------------------

Date: Mon, 9 Dec 1996 21:15:58 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Adding another Netware 4.1 server

>We just got a new server, and before I added the server to the network
>I was wondering if I needed to know anything in particular before I
>installed the 4.1 software.  Will NDS take care of adding the server to
>the tree?  I'll be doing tons more reading, just wanting to know if there
>are any pifalls which I may run into that only an experienced Novell
>person might have encountered.

	Nothing particular to know beyond which O/OU will be its home.
NW 4 installations are very boring affairs, autopilot stuff. There is a
point where you are asked to login to the level above as admin of it
and then the server tries to join the tree. Joining may take quite some
time, particularly if the new server's clock is way off network time.
The advice is to hang in there, and keep hanging until the system
stabilizes. One can toggle round to the colon prompt and watch or help a
little during this phase.
	So, yes, the server grafts itself onto the tree you choose (one
of the existing variety or a new tree if you so desire).
	I've done NW 4.xx installations so many times I don't give it much
thought beyond "Why the heck can't we do with fewer NLS files being loaded"
and trivia such as that.
	Oh yes. There is a real gotcha waiting to trap folks. When
configuring the lan adapter(s) there is a panel asking about node address.
Don't touch that item! It really means the hardware/MAC address of the
board and that should never be changed. Now, there, you have something to
look forward to and chuckle about.
	If you'd like to practice the whole thing disconnect the machine
from the network and install the server into its very own tree. Then, when
done, reinstall NW and ensure you destroy and recreate the NW volume
(otherwise NDS files remain to haunt you through time). Installation takes
about 30-45 minutes or so.
	Novell is getting better/slicker about installation on each NW
version.
	Joe D.

---------

Date: Tue, 10 Dec 1996 08:49:58 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Adding another Netware 4.1 server

>>	If you'd like to practice the whole thing disconnect the machine from
>>the network and install the server into its very own tree. Then, when done,
>>reinstall NW and ensure you destroy and recreate the NW volume (otherwise
>>NDS files remain to haunt you through time). Installation takes about 30-45
>>minutes or so.
>>	Novell is getting better/slicker about installation on each NW version.
>>	Joe D.
>
>OUCH!  Delete the SYS: volume?  Why???  Does it really keep old DS database
>files around when you removed DS?  If so, why?  Seems a dire waste of space.
>My plan here has been to add to R&D tree, configure apps, etc., test, then
>remove from R&D and add to production tree.  I'd hate to have to restore the
>SYS volume in all this.  Perhaps I misunderstood your post...?  Just
>moderately incredulous...
>
>Lindsay
----------
	A volume deletion and recreation is the only way I know of to
completely remove old NDS traces. Since installation is nearly automatic
and not very lengthy why make a fuss over this part? After all, the point
is to see the installation process from start to finish in detail, and only
afterward to avoid mistakes in making a guaranteed clean installation. Short
cuts aren't here.
	Joe D.

------------------------------

Date: Tue, 10 Dec 1996 13:52:47 -0800
From: "Robert S. Sfeir" <robert@BUYSIDE.COM>
Subject: Re: Adding another Netware 4.1 server

>	A volume deletion and recreation is the only way I know of to
>completely remove old NDS traces. Since installation is nearly automatic
>and not very lengthy why make a fuss over this part? After all, the point
>is to see the installation process from start to finish in detail, and only
>afterward to avoid mistakes in making a guaranteed clean installation. Short
>cuts aren't here.
>	Joe D.

I'm happy to announce that Joe was right (as usual) and it took a whole 30
minutes to install.  There is really not much setup required for users to
access it except for modifying login scripts.  I think I just discovered the
beauty of NDS... Same tree, same login name, same resources same
everything!...  I knew that before but you never really reallize it until
you add one or 2 more servers.  Patches too the longest to install... Weird!
I also took care of the MAC.NAM file first before install, I reallized the
program will want to put the old name in first, then I'd have to go through
heck to get things back where they were...  Bring on the IntranetWare
upgrades!

------------------------------

Date: Tue, 17 Dec 1996 08:25:38 -0800
From: Floyd Maxwell <floyd@DIRECT.CA>
Subject: IntranetWare 4.11 Online Docs problems

I have had a number of difficulties with the online
documentation that comes with iNW.

The good news was that the stand-alone DOC CD-ROM was
a treat to install and use.

The bad news was that:

 (1) I have yet to see any online docs on the NIAS
     portion of iNW -- IPXGW (IPX-to-IP), MPR, NIAS
     (the Web server) or WANEx.

 (2) There is no control of where the NWUXPS CD-ROM's
     NFS online docs are installed and they require a
     different setup to run properly than the standalone
     DOC CD-ROM files (for the NWUXPS docs you just need
     to launch the EXE, rather than also passing a
     "-ini \\SERVER\VOLUME\DOCVIEW\DTAPPWIN\DYNATEXT.INI"
     parameter -- I had cloned the first install icon
     that contained this parameter and then spent a
     "considerable" amount of time reinstalling and ini
     modifying, etc to no avail).

 (3) I have thus not had too much luck in trying to merge
     these online docs into one set of directories, on
     one server so that the whole Computer dept. can
     point to one place for all docs.

Anyone had similar experiences, or solved any of the above?

---------

Date: Tue, 17 Dec 1996 13:59:00 EST
From: Angie Veach <aveach@IQUEST.NET>
Subject: NIAS Online Documentation

>I have had a number of difficulties with the online
>documentation that comes with iNW.
>
>The good news was that the stand-alone DOC CD-ROM was
>a treat to install and use...

1) The online documentation that ships with NIAS is pretty basic to the
Netware 4.1x base product.  I spoke with Edward at 800-336-3892 and I could
buy the complete NIAS manual set for $300 which is due to come out any time,
if it hasn't already.  I specifically asked him if the Web Server, etc.
documentation were included in this manual set.  He indicated yes.  I don't
know if or when there will be an updated CD-ROM version of the online docs.

2)  I have two volumes, SYS: and VOL1:.  The install program wants to put
everything on SYS: and I don't have enough room available to keep it there.
So, I moved it to VOL1: and then nothing worked.  I have found a way to
incorporate all online docs to come up in one session of Dynatext, under
each specific product header.

3)  On VOL1:(G:\), I have two directories:  DOC and DOCVIEW.  The DOC
directory contains, as you know, the document or book files.  The DOCVIEW
directory contains the viewer (Dynatext) files.  Whenever I receive new
Novell products that include online documentation, I merge their directory
structure to fit to my current one.  What I have found that works is the
following:

G:\
...DOC\
.......ENGLISH\
...............NW411
...............LWP50
...............WEB20
...............NW411C2, ETC.

I just move/copy their directory structure from their install to the one I
have on G:\.  All book directories go under the directory of ENGLISH.  When
I load Dynatext, all nine of my document collections come up on one screen
for me to choose what product I want to view.  I then have to modify the
Dynatext.ini file as follows.

4)  In the Dynatext.ini file, there is a line called connection=.  The
following is my connection line as it appears in my dynatext.ini file.  THIS
IS ALL ONE LINE WITH NO WRAP AROUND.  The following wraps around so you can
read it in this message only.  The syntax is important.

COLLECTION=G:\DOC\ENGLISH\NW41=Netware 4.1 Manuals;G:\DOC\ENGLISH\LWP50=Lan
WorkPlace 5.0 Manuals;G:\DOC\ENGLISH\WEB20=Netware Web
Server;G:\DOC\ENGLISH\NW411C2=Netware 4.11C2;G:\DOC\ENGLISH\NW411CLI=Netware
4.11CLI;G:\DOC\ENGLISH\NW411COM=Netware
4.11COM;G:\DOC\ENGLISH\NW411GTS=Netware
4.11GTS;G:\DOC\ENGLISH\NW411REF=Netware
4.11REF;G:\DOC\ENGLISH\NW411SYS=Netware 4.11SYS

This is the only line that I changed in order to view all my collections in
one Dynatext session.

------------------------------

Date: Tue, 17 Dec 1996 20:19:29 +0100
From: Borsodi Gabor <thulya@BME-EIK.EIK.BME.HU>
Subject: Re: NIAS Online Documentation

>COLLECTION=G:\DOC\ENGLISH\NW41=Netware 4.1 Manuals;G:\DOC\ENGLISH\LWP50=Lan
>WorkPlace 5.0 Manuals;G:\DOC\ENGLISH\WEB20=Netware Web
>Server;G:\DOC\ENGLISH\NW411C2=Netware 4.11C2;G:\DOC\ENGLISH\NW411CLI=Netware
>4.11CLI;G:\DOC\ENGLISH\NW411COM=Netware
>4.11COM;G:\DOC\ENGLISH\NW411GTS=Netware
>4.11GTS;G:\DOC\ENGLISH\NW411REF=Netware
>4.11REF;G:\DOC\ENGLISH\NW411SYS=Netware 4.11SYS
>
>This is the only line that I changed in order to view all my collections in
>one Dynatext session.

The solution above is good in the case if you always map that volume to
the same drive letter for every user who is permitted to read the docs.

If you cannot have such permanent mapping use UNC instead:

	collection=\\servername\volname\doc\$nwlanguage\collectiondir=...etc.

------------------------------

Date: Fri, 20 Dec 1996 13:56:54 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: annonyance with intranetware

>I have 2 Intanetware boxes with the IPX/IP gateway activated on them.
>I set it all up with inetcfg and the dumb things load TCP/IP first, and
>the IPX/IP gateway is loaded with the TCP/IP protocol.
>
>This causes a problem, because the IPX/IP gateway loads NetDB which stops
>loading for a couple of minutes 'till the clocks synchronize.  No problem,
>except the servers can't sychronize over TCP/IP, and IPX isn't loaded at
>this point.
>
>How can I make IPX load first from INETCFG?  The 2 minute delay on boot
>is a real pain on my test server.
---------
	A) Remember the part where you are asked to review startup.ncf and
autoexec.ncf? Never mind, just edit it after installation.
	B) Please press the Enter key before reaching 80 characters per
line.
	Joe D.

------------------------------

Date: Tue, 31 Dec 1996 14:31:26 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: 4.11 Upgrade

>We are still in the stone age at 3.12, how difficult is the upgrade to
>4.11? Does it require a complete reinstall or can a migration be preformed.
>
>Thanks, in advance
----------
	I'm sure you will want to read the NW 4.11 documentation in detail
before changing anything. In it you will find the several strategies for
changing the server, and that subject is too big for an email message.
	Bottom lines dept:
	If you have namespaces loaded then do a fresh installation.
	If you want (as you should) 64KB disk allocation units then do
	a fresh installation. Omit disk compression.
	A fresh installation loses passwords and file trustee rights etc
	but they will probably change anyway as you move into NDS and
	abandon user level bindery access.
	If your sys: disk drive has less than 25MB of C: space then do a
	fresh installation with that or more as C:.

	Obviously a full and tested-good backup (or three) is needed before
touching things. You can build a test server for experiments and answer
questions. Treat the situation as a practice disaster recovery exercise.
	Joe D.

------------------------------

Date: Sun, 5 Jan 1997 19:42:25 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: 4.1 - 4.11 NLM compatibility

>Does anyone know what the backwards compatibility of the NLM's, EXE's etc that
>came with 4.11 is with 4.1?  E.G. the 4.11 version of Monitor runs fine on 4.1,
>does anyone know what doesn't?

	Not outside of Novell. But some common sense helps a bunch here. That
translates into don't move NLMs from one server version to another unless the
vendor say it's ok. Certainly don't move standard Novell system NLMs around
this way. That's the server internals half of the problem.
	Client software, executed by DOS or its Windows cousins, is generally
backward compatible. That means newer client software runs against older
servers, but the reverse is only partly true (on a case by case basis).

>I know that DS.NLM is different (5.73 vs 5.01), the license files are
>incompatible, you have Long.nam on 4.11 and OS2.nam on 4.1.  Most updates just
>specify 4.x, so most things should work, are there any others that don't?  I'm
>staying with the ODI 3.20 spec drivers for the moment.

	The way to find out is to try it, ugh. Many third party programs work
just fine from the 4.10 to 4.11 levels, but hardly all. Sitemeter does not,
Discport (CD-ROM stuff) does not. Brad Clement's popular RDATE.NLM does not
(unless one goes back to TCPIP.NLM v5.00 from Jan 96).
	Server ODI drivers generally do work, but...  There is a whole new
set of specs for server drivers (lan, disk, whatnot) and one should try to
stay in that boundry so that patches and updates are applicable and effective.
The last thing needed is some wierd bug that traces back to an amalgam of
drivers and supporting NLMs. And, be sure to apply the compendium update to
NW 4.11 because it has an impact on some items being runnable or not.
	The "most updates specify 4.x" is pretty generic and can often mean
only 4.10. You'll have to test or call the vendor to find the real rules.
As to Novell patches/updates themselves I do not apply them to another version
of NW. Just stay with what's in updates\nwos\your-version-of-NW in the ftp
archives.

>I'd like to keep a consistent set of NLM, DSK, LAN drivers on all servers where
>possible, is it possible to update most of the support nlms and exe's on my 4.1
>boxes from a 4.11 server.  Login.exe for instance, has been updated in 4.11

	I think that "one size fits all" approach is unwise in this case.
I run NW 3.12, 4.10, 4.11 servers and I do not mix components between them.
To run NW 3 components in my path, say SYSCON, I do remove all the religious
.BAT files from sys:public of NW 4.x. Just apply updates/patches particular
to each version on each version and that's that. The simple way of remembering
this is to be able to recreate a server quickly from Novell supplied components
for that version of NW. Too much tinkering becomes too much to remember.
	Joe D.

------------------------------

Date: Wed, 8 Jan 1997 15:08:19 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Re-Installing a 4.1 server

>There is an easier way.  You can change the NDS Partitions so that server
>2 contains the master copy of the partition.  You can then follow the
>proper procedure for removing server 1 from the tree.  Then you can
>reformat the server and reinstall Netware.  Just insert the server back
>into the tree where ever you want it.  That would probably be easier and
>safer than playing with DSMAINT.  Just make sure that you follow the
>proper procedures for removing the server from the tree.

	Some good points above, and let me pick up on one. When a sys:
disk drive is replaced it loses its NDS magic number. Putting it back into
the tree without it is problematic. That is one reason to use DSMAINT.
	How does this occur? The NDS volume name also has an NDS object
ident number which the rest of the tree knows. Recreating an NDS object
also creates new, fresh, numbers (unless one uses NW 4.11 SMS compliant
tape restores). That means the old number is the "real" one and the new
number is an "imposter" as far as the tree is concerned.
	The way around this I have used, if the drive has failed without
notice, is to rebuild the server into a dummy tree, use Load Install to
remove NDS, then while there Add NDS and specify the old server ident.
To be successful one normally needs to remove the old volume object first
with a management workstation so old id is gone and a new number is accepted.
It's easy to shoot one's tree in the foot here.
	The dummy tree is needed to complete the fresh installation and
then load up tape restore programs and whatnot.
	In any case, never zap a server holding a Master copy of a database.
Move mastership to another server (DSREPAIR), remove the server from the
replica ring (so that NDS updates can proceed without it), and then tinker.
	Finally, before tinkering please bring all NW 4 servers up to the
very latest level of DS.NLM (5.01 for NW 4.10 servers, 5.73 for NW 4.11).
Less is not good, mixtures of less is probably worse.
	Joe D.

------------------------------

Date: Fri, 10 Jan 1997 13:59:50 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Novell 4.1 and Novell Webserver 2.0

>I'm running Novell 4.1 with Novell Web Server. I can "see" the webserver
>internally, via IP address or host name. When I try to connect from the
>"outside", via compuserve or america online, etc., I get a Timed out
>message...like it can't find the server. What's happening?? We currently
>run a Windows NT WebServer, a MAC Webserver, and a Front Page
>Webserver without any problems...but the Novell WebServer, it just
>doesn't want to be seen by the outside world.
--------------
	Which version of Novell's Web Server?
	My quick guess: you lost the IP "default route." Some late versions
of Novell's TCPIP.NLM clobber that item and I have had to insert the default
route by hand (via Load TCPCON) after each boot.
	Joe D.

------------------------------

Date: Mon, 13 Jan 1997 17:32:06 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Migrate

>I am trying to copy  data from one volume on a 3.12 server to another 3.12
>while maintaining file ownership and rights. Ncopy and copy can physically
>move the data however all the data is credited to my account. <snip>
----------
	Ownership and trustee rights are held in the file system, and they
are stored as numerical idents. The bindery has conversion from numerical
to text idents. Ncopy/xcopy/copy/etc do not move this extra information.
Tape backup programs can. But when the information ends up on the other
side the other side's name-number tables are completely different than on
the source machine. Uh oh. The numbers are server-specific. Numbers are
used because they are compact and readily compared; text strings would
consume huge amounts of file system space and be slow to compare.
	This name versus number being strictly local to the server is true
for NDS as well, and is one of the reasons why tape restores of NDS material
is a problem on NetWare before 4.11. NW 4.11 has the good sense to record both
and use what's appropriate.
	So, use a copy program if you wish, and follow it up with a FILER
session to reassign ownership and rights by name on the destination system.
There are utilities from John Baird and Wolfgang Schreiber which can read
ownership and trustee rights to text files, suitable for replaying to reassign
them. Please look in directory apps on netlab2.usu.edu.
	Joe D.

------------------------------

Date: Wed, 15 Jan 1997 19:59:52 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: 4.11 No Brainer!

>Just wanted to say to all wondering about Netware 4.11 1- Get the
>activation key!  otherwise you're in deep poop!  2- The install is a no
>brainer.  Novell has done an amazing job of writing a wonderful Install
>program!  Took me 30 minutes to upgarde my 4.1 server to 4.11, and 1 hour
>for a 3.12 server!  Rock and Roll!
---------
	Speaking of the 4.11 Install program. Last weekend I revised the
disk farm on a 4.11 server. Near the end of the tape restore something
happened and some NDS files became corrupt. Uh oh. This resulted in no
logins available (no NDS, see), dsrepair would not function, Load Install
would not remove nor add NDS because it encountered read errors when accessing
the NDS files. That meant no across the net tape restores, no fancy tape
restores directly on the server which require a login (ain't none, almost
all tape restore programs now require a preliminary login, even Sbackup).
All in all, an interesting situation.
	I fixed it quickly and cleanly by doing a rollover installation
of 4.11 again. It got to the point of being NDS aware, asked if I wanted to
use existing settings, to which I agreed, and then it replaced the bad stuff
with fresh files and got the scoop from replicas across the wire. The end
result was a happy and intact server. User files previously restored were
intact, owned properly, had the right rights, passwords ok, all that jazz.
	Thus when the sky has truely fallen and there isn't a way into the
server except the console keyboard and directly attached peripherals, and
NDS files are damaged, consider a rollover installation to clean up NDS.
This rescue technique is not in the Novell manuals. Use at own peril.
	Joe D.

---------

Date: Thu, 16 Jan 1997 09:36:46 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: 4.11 No Brainer

>Symantics question here.  When you say rollover installation, do you
>mean install NW4.11 on top of an existiing installation?
-------
	Yes, exactly. The question asked by Install.bat is upgrade an
existing NW 3.1x or 4.1x server, and we answer yes. That leaves existing
user files and whatnot intact.
	Afterward I reapplied the two NW 4.11 patches and removed the
unwanted NLS and driver files as general cleanup (optional).
	Joe D.

------------------------------

Date: Wed, 15 Jan 1997 15:39:26 -0300
From: Marcus Senna Barros - CI <ci@tvbahia.com.br>
To: netw4-l@bgu.edu
Subject: Re: NWADMIN95 and User Template

>We are running NWADMIN95 on our 4.10 server with the latest (2.11)
>Netware Client 32 and it seems to work fine.. However we cannot create
>a user using the USER_TEMPLATE when we try to create with this it grays
>out the create button.

I had the same problem. The new NWadmin 4.11 ONLY works with TEMPLATE
objects (a new class), and doesnït use the USER_TEMPLATE. Unfortunately,
the NWADMIN 4.11 doesnït update the NDS schema to allow us (netware 4.10
users) to manage template objects and create new users using some kind
of template.

I have no solution yet.

------------------------------

Date: Thu, 16 Jan 1997 09:09:01 -0600
To: Floyd Maxwell <floyd@direct.ca>
From: "Robert S. Sfeir" <robert@buyside.com>
Subject: Re: 4.11 licensing

>>Just wanted to say to all wondering about Netware 4.11 1- Get the
>>activation key!  otherwise you're in deep dodo
>
>Can you elaborate?

Novell 4.11 establishes a new way of unlocking the diskettes you are buying
to upgrade the system.  I got caught without a keycode to unlock my user
license.  What Novell is doing is having you fax in a form that has the
serial number of your upgrade.  On that form you have to enter name and
such, plus the serial number of the previous floppy that contained the
previous version's user license.  If this license number does not match the
one you purchased, it will not unlock it.  To get the activation key is a
maximum of a 1 hour process.  The activation key center is open 24hrs a day,
so you don't have to worry about waiting.

------------------------------

Date: Tue, 21 Jan 1997 16:54:12 +0100
From: "David W. Hanson" <hansond@AFRC.GARMISCH.ARMY.MIL>
Subject: Re: Mercury NLM on 4.11

>I am running like may colleges Pegasus mail and the Mercury POP3
>gateway.  After upgrading from 4.1 to 4.11, the POP3 host seems to
>stop working from time to time and start up on it's own again. We can
>force it to restart by unloading and reloading the NLM but we watched
>it start up one time on it's own.  Is anyone aware of an update or
>what may cause this problem.

Yes, I have heard that changes in CLIB.NLM have affected Mercury.
If you contact support for Mercury, they can give you specifics.

------------------------------

Date: Wed, 5 Feb 1997 14:19:29 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Upgrading from 4.1 to 4.11 (Where's the Instructions?)

>I seem to have not gotten the regular upgrade package for my two servers
>that were eligible for the free upgrade from 4.1 to 4.11.  As I go about doing
>the first one, I see references for specific instructions to accomplish the
>upgrade, but can not seem to find the instructions.
>
>The wonderful 4.11 reference book I purchased refers me to a file called
>4x241.exe on the web site, which is not there.  The readme's that I have
>found (so far) on the CD have a lot to say about the dangers of 4.0x to
>4.11 and NDS, but I am already at 4.1.
----------
	It's simplicity itself. Just do what I term a "rollover" upgrade,
which means D:install.bat, choose "upgrade NW 3 or 4 server?"
	Please use common sense though. Thoroughly backup, move the master
partition elsewhere, ensure the NW 4.10 servers are at NDS 5.01 before
you touch anything. Namespaces other than DOS may readily lead to trouble;
if you use them then be prepared to rebuild from scratch if necessary.
	NW 4.10 licenses don't work with NW 4.11, as you probably know.
	For more documentation please contact your Novell dealer or local
office. They are responsible for delivery of the goods.
	Joe D.

------------------------------

Date: Fri, 7 Feb 1997 10:25:40 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: IntraNetware and FTP server (Early Access Edition)

>I just received my copy of IntraNetaware Early Access Edition and found
>out that it does not have the FTP Server product CD with it.  Does
>anyone know if this is available for download somewhere (ftp.novell.com
>or mirror sites) or will i have to purchase the for sale version.  I am
>evaluating this over NT.... (no technology) and would like to get this
>feature working as it is a very important part of the needs for my
>Intranet / Internet server.
-------------
	Ftpserv.nlm is undergoing improvements at this time. Not
distributing the current design is a good thing for us, believe me (the
guy making most private noise about ftpserv which led to the changes now
in progress). I need it too, but I am waiting for the improved design. To
obtain a copy of the current material I recommend you discuss the matter
with your Novell local office.
	Joe D.

------------------------------

Date: Fri, 7 Feb 1997 14:03:16 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: OS/2 Name Space

>I did do an upgrade (Migrate from 3.11 to 4.1 and then upgraded to 4.11).
>How can I tell which files should be there and which should not in the
>SYS:SYSTEM and SYS:PUBLIC directories?
--------
	A person told me their extremely clever answer to that one. Before
the upgrade change ownership of files to a newly created username. Then
after the upgrade see which remain under that ownership.
	You should also do an NDIR /S > filename to have a listing of
files, datestamps, etc from the original 3.11 system.
	Now having said these words there is another aspect to consider.
That is disk allocation units. These days disks are large and it is
best to go to 64KB allocation units. You can do that with NW 3.1x and
tape restore files before unpacking the NW 4.11 CD-ROM. Naturally you
will have really good backups (plural) before commencing, and you will
know a restoration can be done via NW 4.11 (because you tested it on a
play machine).
	Joe D.

------------------------------

Date: Fri, 14 Feb 1997 13:06:25 +1300
From: "Baird, John" <BAIRD2@WHIO.LINCOLN.AC.NZ>
Subject: Strange console problem

>I have a 4.1 server with 128 MB ram and 4 GB hard disk and running
>Mercury/Pegasus.
>
>It had been running since Dec 1996 and now I am having a strange
>proble on the console:
>
>Server-4.10-237
> Insufficient directory space (or memory) to preserve SYS:TEMPFILE.000
> during file erase

You have run out of directory entries. Either you have reached 13% of
volume space used for directory entries, or you have hit the max of
2,000,000 under pre 4.11 versions of Netware. If the former, you can use
the console command "set maximum percent of volume used by directory=x".
If the latter, you should do purge/all but be aware that this should but
wont necessarily relieve the problem. NW 4.11 supports 8 million directory
entries with multiple name spaces, or 16 million for DOS only, so upgrading
is another solution assuming you are currently using 4.10.

Windows apps tend to leave behind huge amounts of litter in the form of
deleted temporary files, many 0 bytes in length. Ensure TEMP directories
are flagged purge immediate. Another possible source of problems is
student programs running amok - we have run out of directory entries
several times here when programs have gone into an endless loop creating
zero length temporary files which consume directory entries but not space.

------------------------------

Date: Mon, 24 Feb 1997 23:00:40 -0600
From: Darwin Collins <dcollins@fastlane.net>
To: netw4-l@ecnet.net
Subject: Re: Why go Intranetware

Arthur B. wrote:
>Seems to be 3 choices:
> 1. stay with Netware 4.1, maybe do some hardware upgrades.
> 2. migrate to Netware 4.11
> 3. migrate to Windows NT

Good points.   IMHO...

IntraNetware/4.11 adds:
. DHCP  - but we already downloaded it (free) and use it on 4.10.
. DNS   - ditto.
. newer NWAdmin - ditto.
. WebServer - but, already using the 'for pay' one.
. newer clients - ditto.
. better TSA support of bindery objects - not sure if we have this one.
. abend recovery - but, we haven't had any 4.10 production servers crash
. netscape licenses - but, then, we could use Internet Explorer.
. SMP out of the box. supports PentiumPro - but, file/print is bandwidth
  intensive.

The only items that IntraNetware/4.11 adds, which we could 'value' was:
. more directory entries.  (we hit the max on one server)
. more updates on WebServer.
. 'current' rev of 'code'.
. SMP.  - potential future.

So, we are spending $12k, to upgrade  7  250user copies &  3  100user
copies of 
Netware 4.10 to IntraNetware 4.11.

------------------------------

Date: Wed, 26 Feb 1997 14:27:10 -0600
From: "Mike Avery" <mavery@mail.otherwhen.com>
To: netw4-l@ecnet.net
Subject: Re: Netware DNS

>Does anyone know where I can get hold of the Netware DNS
>implementation?  I've had a look round support.novell.com but can't
>find it.  What should I be looking for?  I've got the DHCP server -
>works like a dream!  I'd like to put DNS on as well so I can scrap a
>Unix box (well, re-deploy!)

It's in the NWIP package.  It requires NetWare 4.10 or later.

And.... it's not as stable as you might hope.  We found that changing
information in the tables could cause the server to abend.  This
problem decreased when we got up to date on the patches, but never
QUITE went away.  (Two notes - it's been about 6 months since
I played with that, so things could have improved in the interim.
Also, the employer I was with at the time moved the primary DNS to
a HP Unix box and runs the DNS on the NetWare servers as a
secondary DNS.)

My suggestion is to put dhcp and dns on a 2 user license machine
along with your backup product (especially if you use arcserve to
backup a number of servers).

Also, have a secondary DNS that gets its information from the first -
that way if the first one abends, your users can keep running until
the primary dns is back on line.  The secondary can be any 4.X
server as running DNS didn't seem to cause problems.

------------------------------

Date: Thu, 27 Feb 1997 15:23:23 -0600
From: Darwin Collins <dcollins@fastlane.net>
To: netw4-l@ecnet.net
Subject: Re: 4.11 upgrade

>Everyone else on our tree (admin included) is at 4.1 or lower.  Does
>anyone know of ANY problems that may arise if we upgrade to 4.11 before
>everyone else?

Basically:
. all servers must be running at least 4.89 DS rev.
  Recommend:  to run the current DS rev (5.x)
. the server to be updated will extend the schema. (for the tree)
  It will create/add:  class  User Template
  This means:
  old NWAdmin will still use object name 'USER_TEMPLATE'.
  new NWAdmin will ignore the old USER_TEMPLATEs.
    It expects a 'User Template' class object.
  I believe new UIMPORT will still use the object name 'USER_TEMPLATE'.

  The only problem that we found, is that we need to upgrade Microtest
  DiscServe and Intel LanDesk (runs on that server) in order for them
  to support 4.11.

Oh, you can not mix licenses of 4.11 / 4.10 on a single server.  I mean,
that if you find that you run out of licenses on your 4.11 server, that
you can't just 'add' a 250user 4.10 license to it.  (even temporarily)

------------------------------

Date: Fri, 7 Mar 1997 15:01:10 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: NTP (Network Time Protocol) client available for NW servers

>>Joe,
>>
>>So what does it offer above RDATE?
>>
><cut Joe D.'s post about the NTP client>
>
>I asked that same question at the download site and here is the
>response I got:
>
>>Basically the SNTP uses a much more sophisticated system to provide
>>network time, than RDATE can. But this brings only advantages when
>>you run a SNTP server as well, since they have a synchronisation
>>sheme, who has about the same features as the NW 4.x timeservers have
>>between each others.
------------
	No, not really. NTP is a fancy network time protocol, for sure,
and one of the RFCs is in the package. But you do NOT have to run an NTP
server. In fact, have only three local standards machines, each slaved to
different national standards, and read time from the locals. If you lack
the locals then go to the nationals or whatever directly.
	The whole idea is to use the Internet as a source of time servers,
	^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
and to do so accurately. The Internet in this case can be local machines,
if you wish, or far away, or both. Be considerate of bandwidth and machine
loading.
	Before hanging on to someone else's machine please get their
permission. I strongly recommend reading NEWS group comp.protocols.ntp
to get an idea what is going on and where standards sites are located.
NTP is the de facto precision time keeping mechanism for "real machines",
including the better Unix boxes. PC motherboard clocks have always been a
joke as time keepers.
	RDATE is used to get the clock to roughly the right time (say within
seconds); use it as a one-shot at server startup and ensure it is unloaded
before starting SNTPCLNT. Recall that NetWare 4 no longer bothers keeping
DOS time current (sigh, I do wish they would stop that).
	Some of us have been pressuring Novell to have NTP built into NW 4,
for all the obvious reasons (see "joke" above). Amongst other tiny worries,
NDS comes alive and talking before the TCP/IP stack loads, which can disrupt
a network with false time. Rumors say they might look into it.
	Joe D.

	Folks, I do recommend doing the background reading on the subject
because it is useful professionally. The main docs are RFCs, such as 2030
and 1769, available from many places including netlab1.usu.edu and
netlab2.usu.edu.

------------------------------

Date: Wed, 12 Mar 1997 18:58:36 UT
From: DAVID SIMS <DavidSims@MSN.COM>
Subject: Dynamic Block resizer

RESIZE.NLM from Novell consulting dynamically adjusts the block size
in 4.1x.

------------------------------

Date: Tue, 25 Mar 1997 11:55:48 -0800
From: "Philip J. Koenig" <pjk@CRL.COM>
Subject: Re: New 4.11 defaults

>>I notice that NW 4.11 now has the following defaults:
>>
>>- Loads Mac namespace
>>- Turns off read-after-write verify
>>I am interested in opinions re: whether there is any way to not
>>load the Mac namespace if you never-ever are going to need it,
>>and whether reliability is compromised not having r-a-w verify
>>active.
>>I don't recall 4.1 doing the latter, but I may have missed it.
>>I thought it was a traditional NW feature to do that checking.
>--------------
>	Again, don't let machines win all the battles. Look at the
>installation process and discover that you can change settings as
>you install things. It's that simple. Don't cave in to defaults.
>	Joe D.

I never claimed I couldn't change things, I was simply attempting
to query people as to whether they thought these new defaults were
prudent or not.

As a matter of fact, I did change read-after-write verify back on,
and originally did remove "Load MAC.NAM", but changed it back after
it occurred to me that once the volume had been created with the Mac
namespace in the first place, it really didn't accomplish much to not
load it in the autoexec, since the filesystem structures were already
in place anyway.

(BTW, I did not see an option to not initially add the Mac namespace
when the SYS etc. volumes were first created.  It's possible I am
missing something because the copy of 4.11 I have was received with
a Novell book [2 user] and not a shrinkwrapped retail version with
the install manuals.)

---------

Date: Tue, 25 Mar 1997 13:47:55 -0700
From: Shawn <opeth@FUTUREONE.COM>
Subject: Re: New 4.11 defaults

>As a matter of fact, I did change read-after-write verify back on,
>and originally did remove "Load MAC.NAM", but changed it back after
>it occurred to me that once the volume had been created with the Mac
>namespace in the first place,

From what I've noticed (as I posted earlier), it does not add the name
space to the volume. It only adds the load mac.nam to ncf file. Check the
volumes to see if it has Mac namespace support loaded (I don't have a 4.11
server in front of me or I'd do it too).

>(BTW, I did not see an option to not initially add the Mac namespace
>when the SYS etc. volumes were first created.

I haven't seen this option either. However, you do have the option of
deleting the load mac.nam line before finalizing your initial ncf
configuration.

------------------------------

Date: Wed, 26 Mar 1997 11:48:05 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Upgrade 4.1 to IntranetWare

>Can anybody point me to an exact procedure for upgrading a 4.1 server
>to IntranetWare? (4.11).  I see references in places that state you
>must use DSMAINT, but no exact procedures.
---------
	Easier. Insert CD-ROM in drive A: (er, the CD-ROM equiv), run its
install .bat file, choose upgrade existing server.
	As always, make really good backups before starting, never tinker
with the server which holds the master NDS partition (make another server
the master while you work).
	Joe D.

------------------------------

Date: Thu, 27 Mar 1997 15:52:39 EST
From: seanstanton@juno.com (Sean M Stanton)
To: netw4-l@ecnet.net
Subject: Re: Intranetware Gateway & TCP/IP

>We have the following problem:
>
>We are using PC/TCP product over win 3.11, and we want to use the
>IP/IPX gateway facilities of Nw 411 to connect our corp network to
>Internet.
>
>To do this, we MUST install the Novell Client32. But this client is
>not ODI, so we are not be able to run PC/TCP over it.
>
>We are thinking to migrate to W95. But the problem is:
>
>1) What happen with the TCP suite from microsoft when we install the
>IP/IPX Gateway???

The Client32 installation has a choice to install the IP/IPX gateway
client piece. This choice also installs a "WINSOCK Switcher" program. It
leaves your prior winsock intact and also installs it's own WINSOCK.DLL
that talks TCP over IPX to the gateway., which converts to IP. You can
then switch between the two WINSOCK.DLL's on the fly. The TCP suite
applications should work as before, as they just talk to Winsock. The
only caveat is that when you are using the gateway, you are limited to
TCP packet types, no UDP allowed. This means certain types of
applications won't work, but this also helps secure your network from the
outside as well.

>2) Can I telnet from my WS to a unix host in my network??? Must I
>configure TCP/IP in both Gateway NICs??

Yes, first you must shut down all applications using the gateway and
switch to your old WINSOCK.DLL, as Windows can only use one WINSOCK.DLL
at a a time. And, no, only configure TCP/IP on the NIC that connects to
your ISP. Leave the NIC on your internal LAN bound to IPX only, this also
adds to you security from hacker intrusions, as the only TCP/IP node
visible to the outside world is the gateway.

>3) Is there any way to run ODI comaptible layer over Client32???

The Client32 can use NDIS or ODI drivers, the drivers supplied with
Client32 are ODI, and the drivers that come with WIN95 are NDIS, but all
WIN95 protocols, whether from M$ or Novell or any other company, will run
over NDIS or ODI drivers.

------------------------------

Date: Fri, 28 Mar 1997 10:40:14 -0800
From: "Robert S. Sfeir" <robert@BUYSIDE.COM>
Subject: NEW MAILING LIST

I've created a discussion list for all who are using or have an interest
in using the IntraNetware Web server.  If you're interested do the
following to subscribe:

Email to:  Listserver@buyside.com
Subject:   Blank
Text body: subscribe netwareweb <firstname> <lastname>

This list has a moderated join, so it may take a little while before
you're subscription is accepted. (usually once a day)

------------------------------

Date: Fri, 18 Apr 1997 19:00:45 +1200
From: David Harris <David.Harris@PMAIL.GEN.NZ>
Subject: Re: Need more 3.12 licenses - good reason install 4.11?

>(My own wish is to upgrade to 4, but busines prudence requires a full
>evaluation of all NOS alternatives, blah blah blah.) Hence, we have no
>NDS tree design in place, nor any immediate plans to design one. What is
>the impact of running 4.11 in bindery mode for a large production
>server? How much work will it be to implement? What would be the user
>impact? If we eventually do decide to migrate to 4, how difficult will
>it be to switch from bindery emulation to NDS? What would you do?

If it were me, I'd keep well clear of it. With NetWare 4.11, NDS is
almost usable now, but bindery emulation is a disaster - pure and simple.
Some reasons:

1: (the biggy)  Any time you have to rebuild your NDS database, your
bindery will get rebuilt and all your users' bindery IDs will change.
This can be a real hassle, since you have to migrate login scripts and
(if you use Pegasus Mail, which you probably don't) migrate mailboxes to
the new SYS:MAIL directories. It also plays havoc with trustee rights,
since these are still inherently bindery based (even in NDS mode).

2: It's incomplete - for instance, users directories in SYS:MAIL are only
created when the user actually logs in. This can make it a real bear to
pre-load a login script for a user.

3: It's slow - very slow. Our tests during the development of Pegasus
Mail show a bindery emulation server to handle bindery-based queries
anything up to 10 times slower than a NetWare 3.x server (mind you, NDS
isn't exactly greased lightning, either).

As far as migrating to NDS mode, well, that depends on what applications
you use and how much you are actually using the features of the NOS; if
you are not using NetWare-aware backup or mail utilities, then it's
probably not too much effort, other than having to re-establish
everyone's login scripts in NDS.

This is just my opinion of course - YMMV. I will admit that many of the
issues I raise are influenced by the effect they have on my program, and
that many sites may be unaffected by them.

------------------------------

Date: Fri, 18 Apr 1997 03:25:48 GMT
From: James Jang <jjang@PERTECH.COM>
Subject: IntranetWare & HP T4000s SCSI Tape Drive

I am posting this message as a warning for network administrators / vendors
who are installing or looking at new tape drives.

We finally found out today that the HP T4000s SCSI Tape drive is
INCOMPATIBLE with IntranetWare.  HP doesn't know where the problem lies,
but understands there is a problem.  They have no idea when the problem
will be fixed.

If anybody has any info on this please e-mail me at jjang@pertech.com

---------

Date: Fri, 18 Apr 1997 09:07:09 -0600
From: James Hooper <HOOPER@WPOGATE.SLU.EDU>
Subject: HP T4000s

In the last mailing, someone had mentioned that a T4000s was
incompatible with Intranetware.  On a different note, we had a problem
with the T4000s in that it wouldn't read tapes made by an older T4000s.
A computer (with the internal tape drive) was stolen.  When we replaced
the machine with a new T4000s, it wouldn't even recognize the format of
the tape.

Aside from obvious conclusions that the first drive had been "doing its
own thing," HP recommended that I "downgrade" the firmware from 1.07
to 1.05.  I did this and it STILL did not recognize the tapes.

Even though I explained that the tapes contained valuable financial data,
HP refused to help further.  The "customer service" representative told
me that it was a "media issue" and that HP was not a media company,
and that I was ON MY OWN.

Boos and Hisses on HP.

------------------------------

Date: Mon, 28 Apr 1997 08:44:28 GMT
From: Teo Kirkinen <kirkinen@CC.HELSINKI.FI>
Subject: Re: FTP and NDS mode

>In my last posting I inquired about FTP.NLM and thank everyone for the
>replies.  I got FTPD.NLM working rather painlessly, but discovered that
>it does not recognize NDS authentification.

Novell's FTPSERV in Unix Printing System (separate add-on to NW 4.1, free
with INW) uses NDS authentication, we use it everyday ;-)

The NDS authentication is not very reliable, if there isn't a replica
of the needed NDS partition on the server running FTPSERV.NLM. It works
most of the time but it seems to eat IPX sockets until they are all
gone.

------------------------------

Date: Thu, 12 Jun 1997 00:44:49 -0700
From: William Lynch Higgins <william.higgins@postoffice.worldnet.att.net>
To: floyd@direct.ca
Subject: Installing IntranetWare 4.11 on an IDE server

Q. How do I get IW4.11 to complete installation on a server with an all
IDE environment? When I get to the part of the installation where the
volume(s) mount, the installation program loses its path to the CD-ROM
drive (also an IDE drive). The error returned is #266, "path to
NETMAIN.ILS is invalid". No amount of fiddling with loading the CD as a
NetWare volume or as a DOS volume makes any difference.

A. First, within an IDE environment you really should only be loading
IntranetWare as a test server or a non-production server. Otherwise some
sort of SCSI setup is mandated. Assuming that, here's what works.

Preliminary step: set up each drive in the Master configuration. This
means a separate ribbon cable for both the hard drive and the CD-ROM
drive. If adding a paddle board (IDE controller card) for the second
drive is necessary, then you'll have to do it. Modern EIDE motherboards
have dual IDE ports on the board, however.

Note: You will not be able to mount the CD-ROM as a NetWare volume when
offered the choice in the installation program, as this is impossible
with IDE.

Installation: Run as normal. During driver auto-discovery, IntranetWare
loads the IDEATA driver twice. This is determined in the regular "Add
disk ... driver screen". You will see "IDEATA IDEATA". Delete both
driver instances, then add ONE new IDEATA driver by hand, i.e. go to the
driver screen list and scroll to IDEATA.HAM. Select it and load it. This
driver will now work for both the CD-ROM and the disk drive. Novell's
default double-loading definitely does not work, and it returns error
#266. This is true with either a PCI or an ISA motherboard.

------------------------------

Date: Sat, 5 Jul 1997 07:03:58 GMT
From: Teo Kirkinen <kirkinen@CC.HELSINKI.FI>
Subject: Re: 2nd processor / SMP - crash course

>I have a 2nd processor newly installed in one of my servers.  It
>shows up when booting.  Do I have to enable SMP to have netware
>4.11 recognize it?

Yes, you have to use INSTALL.NLM to install SMP.

>The documentation says that to take advantage of the 2nd processor
>a program must be SMP-enabled. So any program that is not written
>SMP-enabled will not use the 2nd processor?  I presume Netware's Web
>Server ver. 3.0 is?  (someone please say yes...)

Quoted from http://www.novell.com/intranetware/

>The Netware Web Server benefits greatly from IntranetWare's
>high-performance file and directory services. It can also employ
>Novell's Symmetric Multiprocessing (SMP), for superior performance of
>resource-intensive applications, such as databases, in extremely high
>demand environments.

A couple of weeks ago PC Magazine (number 10) tested web servers
and how they well the performance scales when a second cpu is added.
We have two servers with two cpus but haven't used Novell's web
server on them.

Very few of the ordinary NLM's we use can be run on the second cpu.
Dr Solomon's virus scanner is one but it is not problem free: the
two latest versions don't work on our dual-P133 AST Manhattan while
they run file on our dual-PPro200 DEC Prioris. The schedules virus
scans just don't start.

Intranetware uses the second processor to run the network drivers:
most of the time the utilization of our second processor is 0-2%
but it process over 90% of the interrupts.

You should also know that auto restart after abend doesn't work
when you have SMP enabled. If the server abends, it will go to
the SMP debugger.

>On a side note, the 1st processor is 133mhz and the 2nd one is 166.
>Does it make a difference that the faster processor is not the 1st
>one?

All the SMP motherboards I have seen run the processors at the same
speed. So if your server is jumpered for 133 MHz cpus, the second
cpu is underclocked to 133 MHz. It doesn't matter that it is
vertified to work at 166 MHz.

------------------------------

Date: Thu, 17 Jul 1997 13:13:39 +0200
From: Camaszotisz Gyorgy <webmaster@KERORG.HU>
Subject: Re: Novell DNS - multiple domains/zones?

>Does anybody know how (if possible) can I make DNS server running on
>IntraNetWare service multiple domains/zones as primary nameserver?

Here is the answer I was getting from Novell Support to the same
question:

   Currently you can only configure a NetWare server as a primary
   for one domain. Support for multiple domains is planned and
   should be available in the major release of DNS which is
   currently planned for release with MOAB (approx. at the end
   of this year).

   It two domains are needed then currently the only Novell solution
   is to have two DNS servers, each being the master of one domain.

------------------------------

Date: Mon, 11 Aug 1997 17:12:45 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Webserver slow response

>I have an Intranetware 4.11 web server and when I first try to connect to
>the home page, It takes like 30 seconds for the server to respond.
>I have DNS running on the same machine, the entries are present for the
>server and all seems to work ok, except for the lag time.  There is NO
>traffic between the time the client requests the page and the server
>responds with the page.  I don't have lanalyzer to look at the packets, but
>it seems to do it at the FIRST attempt of the client request after having
>launched the browser.  Subsequent requests seem to have immediate response.
-----------
	I see shorter lags. But I believe they are involved with reverse
IP lookups to find who you are by IP name rather than just IP number. Thus
if your client's IP info were also on the server in the DNS material it
ought to find the scoop rather quickly indeed. There can be, with some
web servers, an identd probe sent to discover who lies behind an IP number,
and obviously regular DOS/Windows machines don't know about that and don't
respond (meaning, time goes by). LZFW should show that, as well as any
remote DNS lookup by the server (assuming LZFW and server are on the same
wire).
	Once identified information is cached so that subsequent requests
go along quickly.
	What I see beyond what you have reported is lots of fragmented
pages. The pictures are often missing. I interpret this as the NW web
server pushing out information faster than the web client is prepared
to accept and packets are dropped. In my case client and server are on
the same wire.
	Joe D.

---------

Date: Tue, 12 Aug 1997 09:21:41 -0600
From: Jason Green <srpbfs01.jgreen@STATE.UT.US>
Subject: Webserver slow response -Reply

FWIW, I had the exact same symptom running the Novell Webserver 3.0 and 3.1.  It
would take approximately 30 seconds to make the initial connection from a
browser (in my case I was even on the same sub net).  Once the connection was
made, everything worked just fine.  I was running it on a low power server so I
just figured it was because of that, but then I moved it to a real server (HP
Netserver LC with 140 MB RAM) and had the same problem.   I was to the point of
shelving NWS for a different web server.

After doing some testing and not loading everything, I was able to fix the
problem by not loading Novell's ftp server.  I went back to the other server and
unloading the ftp server fixed the speed problem on it also.   I don't know why
it slowed down, but it is running just fine now.  I moved ftp services to a unix
machine which is where they should have been anyway.

------------------------------

Date: Wed, 13 Aug 1997 08:35:59 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: How to migrate existing 4.11 server to new 4.11 server?

>Should not be too hard.  First copy all of the data over, then back
>up NDS on the existing server.  Move the backup file from the first
>server to the new one and restore it.  Look for papers on changing
>server hardware on Novell's web page.  They have some good articles
>on the topic.  If you need more details, let me know.
>
>Mobeen Azhar

	That's correct. The situation is the same as replacing
the disk drive containing volume SYS:. There are a couple of points
worth emphasizing. One is file ownership information is held in the
file system, not in NDS, and that information does *not* move with
COPY/XCOPY/NCOPY operations; use a NW tape backup program for that
task. Another is use either a NW tape backup program rated for full
NDS compliance or Novell's DSMAINT to extract and then restore NDS
information. As with NW 3, restore the database info (NDS for NW 4,
bindery for NW 3) before restoring files.
	Joe D.

---------

Date: Wed, 13 Aug 1997 13:17:48 -0400
From: Erik Cummings <Erik.Cummings@SANTAFE.CC.FL.US>
Subject: Re[2]: How to migrate existing 4.11 server to new 4.11 server

I must disagree with you here Joe on the DSMAINT suggestion.  The only
reason DSMAINT would even be there is if you did an inplace upgrade from
NW4.10 or something similiar.  NW4.11 uses INSTALL.  Having done SEVERAL
of these in the past two months:  Ensure your server is fully patched
Backup all your files to tape.  Use Install/Directory Options/Directory
Backup and Restore Operations/Save Local DS Information Prior to hardware
upgrade.  Make sure you write down your internal IPX net number and
server name.

This will save your NDS to sys:system/backup.nds.  It will then ask
to save it to another place (A: or Remote Workstation if you are
RCONSOLE'd in).  The remote workstation works fine (your NDS may be
bigger than floppy!)  Now remove this server from the network.  If you
bring it up DO NOT ALLOW MONITOR to load with password!!!  You will not
be able to unlock it!!!!

NOTE:  The new server should already be built.  It should have some
name (TEST00 works for me) and in it's _OWN_ tree (again, TEST works
great).  Also ENSURE that this server is fully patched!

Then login to TEST00 from your workstation, copy the backup.nds from
your workstation to it's sys:system.  Change the IPX internal net
number and name to what the old server was.  Also make sure that your
TIME settings are the same as the old server was (HINT:  secondary,
EST5EDT, etc). Reboot AT THIS TIME.  Wait until you get a good timesync
with net.  I have never had it sync up the first boot, I had to down
and restart a second time (well, I never wait more than about 6 minutes
either!).  After the timesync occurs, load install/Directory Options,
Remove DS from this server, say yes/no to all the double check questions.
Then go to directory backup restore operations/Restore DS after hardware
upgrade.  When it asks for the files (A:) change the dir to sys:system/
IF YOU HAVE ANY PROBLEMS, DO NOT PANIC!  Try different slashes/syntax
(ie. sys:\system\ or sys:/system/...I keep forgetting but several of
these syntaxes do not work).  Also, make CERTAIN you have synced time
to network.  It will error out if you do not.  (No harm done error...).

If you did that, you are now ready to restore your files from tape.

The nice thing is that AT ANY POINT (If you have not had to scavenge
pieces from the OLD SERVER) you can back out in less than 5 minutes!
Just shutdown the new server, plug the old one back in, turn it on, and
Load install/directory/backup and restore/restore after hardware upgrade
and VOILA, you are back in business!  (Oh, same syntax and timesync rules
apply here!).  I have backed out at the beginning, middle (several spaces
and even gone back and forth a couple times), even up to having restored
most of the data to the new server and decided to go back!  Avoid the
gotchas above, DO NOT USE DSMAINT if it is there, and good luck.

---------

Date: Wed, 13 Aug 1997 12:22:28 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Re[2]: How to migrate existing 4.11 server to new 4.11 server

>I must disagree with you here Joe on the DSMAINT suggestion.  The only
>reason DSMAINT would even be there is if you did an inplace upgrade
>from NW4.10 or something similiar.  NW4.11 uses INSTALL.

	No need to disagree, because we actually do agree, that is unless
we choose to disagree, and in that case we agree to disagree so we do
agree. Something from Alice in Wonderland, almost.
	Load Install for NW 4.11 uses the same underlying tools that
DSMAINT does to preserve the NDS material externally. I did put an "or"
between this and tape backups.
	Joe D.

------------------------------

Date: Thu, 14 Aug 1997 15:47:56 +1200
From: "Baird, John" <BAIRD2@WHIO.LINCOLN.AC.NZ>
Subject: Crashes causing loss of a volume

Twice in the past 6 weeks we have had a NW 4.11 server crash with the
message "ReturnFATChain was passed a FAT entry that was already free".
On both occasions, vrepair was run automatically when errors were
detected while mounting one particular volume upon reboot. Vrepair
'fixed' the problems, but upon remount 95% of data was lost, so we
have deleted, recreated the volume and restored from backup.
Unfortunately, the crashes occured during mid afternoon and early
evening so it was approaching 24 hours since the previous backup.

We are concerned this will happen again, but are short on ideas for a
course of action. Some details are:

1. The server is a Compaq 4500, 160 MB memory, 16 GB disk in a RAID array,
   2 netflex cards. The entire hardware is Compaq including the UPS.
2. On both occasions the crash has occurred within 2 hours of a reboot,
   on the first, the user load would have been heavy after restart, on the
   second it would have been very light being between 6 and 7 pm.
3. At the time of the first crash, the server was fully patched up to SP2.
   At the time of the 2nd it was fully patched to SP3a, in fact loading SP3a
   was the reason for the reboot just prior to the crash.
4. Compaq's Insight Manager has not reported any disk or memory problems.
5. There were no hardware changes during the 3 months prior to the first
   crash, but the RAID array was extended between the first and second.
6. There had been some 3rd party NLM upgrades in the 3 months prior to
   the first crash.
7. The affected volume had suballocation enabled, no compression, only
   the DOS name space, and is 1 GB in size.

Suggestions anyone? In the absense of better ideas, I'll change the mount
order of the volumes, to mount an existing scratch disk at the point
where the affected volume was mounted, the idea being that this should shift
the volume's fat table in memory, and if a wayward NLM is overwriting part
of the fat tables, next time it will overwrite those for the scratch disk.

------------------------------

Date: Sat, 16 Aug 1997 16:52:25 +1000
From: Scott Marshall <esmarshall@USA.NET>
Subject: Re: nw4.11 and compression

> I have decided, only too late, that I do not want compression
> active on the 4.11 server I'm maintaining. I know I can't make a
> change to volume without rebuilding. I do know that I can change
> the attribute within filer. I could do more research and probably find
> the answer but I hoping someone would be willing to save me a little
> time. I'm under the gun to make a few other mods.
> The question is: Is there a way to set compression OFF recursively
> thoughout a directory structure.

[To turn off compression]

FLAG vol:*.* +dc /s /c

Where "vol:" is the name of the volume that you want to change.

eg "FLAG SYS:*.* +dc /s /c

This will flag all files and directories as "Don't Compress"

Alternatively, you can add "/DO" for Directories Only or
"/FO" for Files Only to the above command.

---------

Date: Sat, 16 Aug 1997 22:46:48 +1200
From: "Baird, John" <BAIRD2@WHIO.LINCOLN.AC.NZ>
Subject: Re: nw4.11 and compression

The solution I'd use is to set the following parameter in startup.ncf

set enable file compression = off

This prevents any more files being compressed on compression-enabled
volumes. Existing compressed files will remain compressed until they
are decompressed via the usual rules. In addition, if you have any
files flagged IC, I'd remove that setting.

------------------------------

Date: Wed, 1 Oct 1997 22:49:27 +0200
From: Camaszotisz Gyorgy <cama@KERORG.HU>
Subject: Re: Intranetware and DNS

>Is it possible to make an IntraNetware server nameserver for two
>different domains?  I mean, two different SOA records.

No, and yes.

No, because current version does not support it. Novell said that the
new version will come with Moab, early next year.

Yes, if you use a less convenient method for setup and management.
Someone at Hungarian Novell list said that NAMED.NLM, the DNS server
supports multiple primary domains, but UNICON can handle only one at
a time. He used the following method:

- Set up DNS server with the first domain name and data.
- Stop the DNS server and rename SYS:ETC/*/HOSTS.DB file to something.
  (I don't remember the correct directory name.)
- Set up DNS server with the second domain name and data.
- Stop the DNS server and rename SYS:ETC/*/HOSTS.DB file to something
  else.
- Edit SYS:ETC/*/NAMED.CFG file. It must contain a line for every domain
  like this:
  primary domain.com sys:etc/*/domain.db
- Restart the DNS server.

------------------------------

Date: Mon, 13 Oct 1997 12:44:55 +0100
From: Hegyvari Krisztian <hegyvari@NFS.JOZSEF.KANDO.HU>
Subject: Netbasic IDE

>I have been looking at the HTML guide to the Netbasic IDE that came
>with NWS 3.1    I am interested in installing the IDE, where would
>the program be?

	www.hitecsoft.com

($ 995 USD)

------------------------------

Date: Wed, 29 Oct 1997 13:01:26 -0400
From: Mike Prosise <mprosise@SED.STEL.COM>
Subject: Re: IP / IPX SnapIn

>>Could someone please point me or tell me how to add the IP / IPX
>>Gateway Snapin to NWADMIN???

Edit the NWADMN3X.INI file located in C:\WINDOWS,
Under the [Snapin Object DLLs WIN3X] section add:
IPXGW3X.DLL=IPXGW3X.DLL
Save and exit

Note that you cannot use the 95/NT version of NWAdmin to view these
objects (yet).  Also, if you haven't run the 3x version of NWAdmin
you'll need to do this first to cause the .INI file to be created.

------------------------------

Date: Tue, 11 Nov 1997 22:36:55 -0500
From: "Jeffrey A. Tinch" <jtinch@FUSE.NET>
Subject: Re: Intranetware conversion time budget

>>Do any of you intrepid souls who have already converted to Intranetware
>>have time budgets for the task?  We're getting ready to do the upgrade
>>from version 3.12 on five servers supporting about 200 users at three sites.
>>Before we do, we need to give management a realistic roll-out schedule and
>>an estimate of conversion costs.  Can any of you pioneers give me some
>>rules of thumb?
>---------
>	Much, most, depends on the skill and experience level of the people
>involved. The way to judge yours is to do a test server.
>	Joe D.

Almost everytime I do a 3.12 to a 4.1x Migration I start on Friday at
about 5:00pm and most of the time if there are no major problems I am
finished by 5:00am.  Some have gone to 11:00am when I have problems or
a really slow network. All have been across the wire migrations. No sense
keeping old hardware around if you don't have to. Plus its better if
there is a major problem, you do not have to reinstall & restore from
tape and start again.

In the 20 plus migration I have done I have never had any problems more
major than fixing print queue problems after the migration or corrupted
files on 3.12 server that if give more time before starting could have
been found and fixed . We usually keep the old server around for about
a week and then turn it into a W/S.

------------------------------

Date: Thu, 20 Nov 1997 11:16:24 -0800
From: Brandon Fouts <BrandonF@WSHA.ORG>
Subject: Install/Upgrade to NetWare 4.11

Install/Upgrade to NetWare 4.11

User wants to know how he can install NetWare 4.11 from the
Netware/Intranetware 4.11 CD-ROM.

There are several ways to go about this.  Please read on:

1. Upgrade existing server: (if cdrom exists on server)

A. Configure, install, and mount 4.11 CD-ROM as volume
B. From the server console type: LOAD cdvolume:products/nw411/_/411/boot/INSTALL -so
C. Select "Server Options"
D. Select "Upgrade 3.x or 4.x server to 4.11
E. Follow the prompts

2. Upgrade existing server: (if cdrom doesn't exist on server)

A. Configure, install, and mount 4.11 CD-ROM as volume on existing server on the LAN
B. From the server console type:
    LOAD servername\cdvolume:products/nw411/_/411/boot/INSTALL -so
C. Select "Server Options"
D. Select "Upgrade 3.x or 4.x server to 4.11
E. Follow the prompts -

    Whether an upgrade from existing server or installation of new server
3. Install directly from CD-ROM: (if cdrom exists on server)

A. Insert CD in drive
B. Choose Install.bat or RUN install.bat
C. Select desired language - proceed with installation

4. Install directly from CD-ROM: (if cdrom doesn't exist on server)

A. Configure, install, and mount 4.11 CD-ROM as volume on existing server on the LAN
B. From workstation to be server, map a drive to that volume
C. Choose Install.bat or RUN install.bat
D. Select desired language - proceed with installation

  Document Title:  Install/Upgrade to NetWare 4.11
  Document ID:  2930912
  Creation Date:  12OCT97
  Modified Date:  06NOV97
  Document Revision:  1

------------------------------

Date: Sun, 23 Nov 1997 02:52:24 -0500
From: "Todd M. Wilkinson" <tmwilkin@MAILBOX.SYR.EDU>
Subject: Re: iNW Server

>> I have been charged with writing up a proposal for an Intranet
>> server with WWW capabilities, user FTP (for publishing pages into the
>> server) and minimal licence requirements.

	Generally you don't have to pay per connection for HTTP connections
	but you do generally have to pay for FTP, telnet, and other
	sort of logins.

>> As I don't have access to NT or Intranetware, I am looking for
>> pointers to good resources that can either do a comparison of the two
>> or can provide some detail of the features and capabilities of each.
>>
>> I would also like personal opinions of the relative merits. And any
>> information from anyone who has gone through this process themself.
>
>This may be heresy on this list but have you considered using
>Linux/Apache?  It free -- so much for license requirement problems.
>Great listservs (like this one) for help.

I guess this all depends on what you are looking for in your Web
server.  If all you are doing is setting up static pages and
the usage is low, then go for the cheapest option which is probably
LINUX of some sort, or an existing machine that can handle a
bit of additional load.  But it comes down to what you want
to do,and were you have the most experience.

Novell - Good if you are already into a Novell environment
	 where drive mappings allow you easy access to do web
	 publishing.  Price is generally right if you are a
	 Novell shop.  The Netware web server does static
	 pages very well and has adequate hooks into perl
	 and Netbasic (proprietary) for server side execution
	 of scripts.  It does however lack 3rd party addon for functions
	 such as easy publishing of documents via a remote IP based
	 machine such as easy publishing via Frontpage (FTP is basically
	 your only option).

NT     - Proprietary but good if you buy into the whole NT based
	 genre.  A well rounded server, but its major flaw
	 is that you must use MS based WEB products to make full
	 use of the server.  Perl must be purchased as an add on
	 to the Web server.  If you want to use Active Server Pages
	 (ASP) you can and some of the development tools are good
	 and can quickly get you into dynamic publishing via databases
	 and ActiveX.  Problem is you loose portability in that if
	 you move to another platform you pages are not going to run.
	 Much of the advanced web page development needs access to
	 the server for error checking and such.  You will have to
	 by into the MS solution if you want to make full use of
	 the server.

(Solaris)UNIX - A good well rounded solution.  If you can code or script
	 in any language that will run on a UNIX box you can run
	 that script or program on a UNIX web server(generally).  You
	 get more complete remote control and access since you can
	 work via telnet from anywere.  Problem is the learning curve
	 for UNIX is higher then any other OS (IMHO).  However if
	 you can write it then it will run on a UNIX box.  Depending
	 on your maintenance needs the costs may or may not be higher
	 that the previous examples.  If you are wanting to hook
	 into Oracle databases for work then you may want the Oracle
	 web server running on your UNIX box.  This tends to be a good
	 pair for obvious reasons.  Portability is generally good
	 from one UNIX version to another and if you write
	 *correct perl* then your perl scripts should move over
	 to Netware perl with only minimum code changes.  You have
	 several OS's to choose from if you go with one of the
	 Linux versions.  RedHat, which is one of the easier
	 LINUX's to get into.  Caldera which is another packaged
	 LINUX is a bit more difficult, but also more robust and
	 flexible as far as support, vendor options for a commercial
	 type of setting.  I could discuss all day the pro's and
	 con's of different OS's but...

Bottom line is that each presents their own advantages and disadvantages.
Get a definite set of needs for the present and the future and base your
decision on what your needs are, not what the vendors or others (like me)
tell you.

------------------------------

Date: Fri, 28 Nov 1997 20:20:20 +0000
From: Randy Richardson <randy@INTER-CORPORATE.COM>
Subject: Re: DNS on IntraNetware

>Can IntraNetware 4.11 be a DNS server without installing Netware/IP?
>We're quite happy using IPX, and NW/IP seems like a lot of fuss at
>the server, just to have a DNS server.

If you install NetWare/IP and don't configure it, the DNS server
will still work.  Make sure TCP/IP (not to be confused with
NetWare/IP) is installed before you install the DNS server.

You can also add IPX/IP gateway to enable internet access for all
the clients without installing TCP/IP at all the workstations.

---------

Date: Sat, 29 Nov 1997 11:03:52 -0500
From: Bud Durland <ndurland@CAPITAL.NET>
Subject: Re: DNS on IntraNetware

>If you install NetWare/IP and don't configure it, the DNS server
>will still work.  Make sure TCP/IP (not to be confused with
>NetWare/IP) is installed before you install the DNS server.

Where do I configure the DNS to add host names and so forth?  Does
it just read all that from the HOSTS and/or RESOLV.CFG files?  What
if I want it to be a secondary DNS?  For that matter, what NLM do I
load to start the DNS?

>You can also add IPX/IP gateway to enable internet access for all
>the clients without installing TCP/IP at all the workstations.

We'll likely do that in a couple of months, but I'd like to get DNS
running now so that I can move mail and web services to a Novell
server, making us an all-novell shop.

---------

Date: Sat, 29 Nov 1997 18:01:59 +0100
From: Camaszotisz Gyorgy <cama@FREEMAIL.C3.HU>
Subject: Re: DNS on IntraNetware

>Where do I configure the DNS to add host names and so forth?  Does
>it just read all that from the HOSTS and/or RESOLV.CFG files?  What
>if I want it to be a secondary DNS?  For that matter, what NLM do I
>load to start the DNS?

To start your DNS service, execute UNISTART.NCF file. This will load
other unix-related components too.  There is a utility called
UNICON.NLM where you start/stop/manage services like DNS, FTP, NIS
and others. DNS uses it's own database via Btrieve.

---------

Date: Sun, 30 Nov 1997 08:36:42 +0100
From: Camaszotisz Gyorgy <cama@FREEMAIL.C3.HU>
Subject: Re: DNS on IntraNetware

>So the steps involved are:
>
> - Make sure TCP/IP is installed and working. (It is, the
>latest patch -- I have my web server here, and I can load
>PING.NLM and find stuff).
>
> - Install but do not configure Netware/IP
>
> - Run UNISTART.NCF at the console (I suspect some of the
>services in UNISTART will already be running)
>
> - LOAD UNICON.  Some where in here I can configure the DNS
>entries.

Yes, the previously described steps was correct. Now I have access to an
IntranetWare server console, so here are the steps you have to walk
through:

1. LOAD UNICON
2. Log in as Admin user.
3. Select Manage Services -> DNS -> Initialize DNS Master Database
4. When prompted, enter the domain name you want to service as master,
   and select whether you have subnets or not.
5. When finished, your DNS server will be up and running. No reboot
   needed.
6. Because the DNS database now contains everything from your hosts
   file, and maybe some mysterious settings, review them in Manage
   Services -> DNS -> Administer DNS -> Manage Master Database.
7. Download the latest root domain database (those for "." domain
   containing entries only for top level domains such as .com) from
   ftp://ftp.rs.internic.net/domain/named.root, and place it as
   sys:etc/dns/root.db on your server. The original one from the INW CD
   contained the military root name servers.
8. Restart DNS server by going in UNICON to Start/Stop Services, and
   deleting the entry for DNS Server, then re-inserting it again.

NOTE:

Novell products use NETDB.NLM as a DNS resolver. This is a stub
resolver, designed to work in conjunction with Novell`s DNS server,
or some other DNS server capable of handling recursive queryes.
Because this functionality is optional for DNS servers, be sure to
set up your RESOLV.CFG file accordingly, or queryes asking for outer
world's information may not be answered correctly.

> - Reboot the server ???

No need for it, just go through the step 8. above.

------------------------------

Date: Thu, 11 Dec 1997 14:37:16 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Virtual LAN Frame Type

>I am running INW 4.1. The NIC internal net number is 343c8913.
>The Node address is 00000012
>Frame Type "Virtual Lan"
>Lan Protocol IPX Network 343c8913.
>
>Can someone tell me the easy way to change the Node address of the
>Virtual Lan, with out doing a re-install.
--------
	Hmmm. Let me guess. When you installed the lan driver you saw a
box on node address and you filled it with 12. THAT IS FATAL. THE BOX
REALLY MEANS BOARD'S HARDWARE ADDRESS AND SHOULD NEVER BE TOUCHED. IF
THIS IS CORRECT THEN PLEASE REMOVE THE DRIVER COMPLETELY AND REINSTALL
IT. USE LOAD INETCFG TO ADD/REMOVE LAN DRIVERS.
	There are no "nic internal net numbers." You may be referring
to the server's IPX address, or the IPX address of a board. The server's
IPX address is most easily defined as the hexadecimal representation of
the IP address of the board closest to the site's backbone. This will
then agree with the IP network number on that wire, which will be the
IPX network number (but expressed in hex).
	Example: board in server closest to backbone is IP 129.123.1.44,
on IP network 129.123.1.0 (subnet mask of 255.255.255.0). The IPX network
is 817b0100 (81 is 129, 7b is 123). The server's internal IPX net (as
seen in autoexec.ncf) is 817b012c. Never change a lan adapter's "node
address" (means its hardware address).
	For more details on this simple and yet highly effective numbering
method please see doc Utahstd.txt in directory misc on netlab2.usu.edu
(or same in pub/mirror/misc on netlab1.usu.edu).
	Joe D.

------------------------------

