For best results: this site requires
that cookies be enabled for proper operation - see Legal Page for more info
Select Any of These
NOVELL NETWARE
LAST UPDATED:
08 March 2009 17:02:36 -0600
Changes to this page are IN PROGRESS
NOVELL'S SUPPORT LIFE CYCLE
To help you keep up with which Novell products are still supported
by Novell and which are no longer supported, Novell publishes the
Novell Support Life Cycle. This Life Cycle defines the duration and
levels of support customers can expect to receive as products move
through their life cycle, assisting you in the management of support
needs and future software upgrades. Novell classifies its product in
four categories--Shipping, Maintenance, Mature, and Discontinued.
You'll find this valuable information on the Novell Web site at
Novell has a wealth of information on its Web site to assist you in
troubleshooting and maintaining your Novell networks. However, you
don't always have access to the Internet to get the help you need.
Fortunately, Novell provides a great deal of that information on its
Support Connection CD. The Novell Support Connection CD, updated
monthly, provides the latest files, patches, drivers, and technical
information you need. For more information on the product and details
on how to subscribe, check out the following Novell site:
With the recent virus scare brought on by Melissa, you should
consider implementing a network-wide virus protection solution. One
possible choice is Command AntiVirus with F-PROT Professional 4.52 for
NetWare from Command Software Systems. This tool includes both an
on-access scanner and an on-demand scanner to search for polymorphic
viruses. It also includes several alerts so that you will immediately
be aware of potential virus attacks, and you install and configure it
centrally. You can download a 30-day trial version of Command
AntiVirus with F-PROT Professional 4.52 for NetWare from
PING is your best friend when troubleshooting TCP/IP connections.
Unfortunately, on your Windows NT workstations, the usual method of
getting command line help doesn't work with PING. For example, when
you type
HELP PING
at a command prompt, Windows NT displays the following error
message:
"This command is not supported by the help utility. Try 'ping /?'."
Then, when you type
ping /?
Windows NT displays:
"Bad IP address /?."
However, you can get command line option help! Just type
ping or ping -?
at a command prompt to display the options.
LOGIN SCRIPTS AND NETWARE 4.1
With NetWare 4.1, you need specific rights to use the login
scripts. For example, you must be a trustee of the object and have at
least the Read right to the login script property to run the script.
This Read right is all you need to run the login scripts. You don't
need the Browse right since it only gives the object the right to be
seen by another object--you don't have to see the login script to run
it. NetWare 4.1 stores the login scripts in NDS, meaning you should
not attempt to make changes by any other means than through the 4.1
NETADMIN and NWADMIN utilities.
TROUBLESHOOTING LOGIN SCRIPTS--PART 1 OF 2
What's the number one cause of problems in login scripts? Most of
the problems NetWare administrators and users face with login scripts
are the result of syntax and spelling errors. Correcting spelling
errors and using variables in the right way (such as putting quotes
around a login name being tested in an IF..THEN condition) resolve
many problems. Double- and triple-check for spelling and syntax errors
before moving on to more complex troubleshooting techniques.
TROUBLESHOOTING LOGIN SCRIPTS--PART 2 OF 2
To help you track progress (or lack of progress) in your login
scripts, take advantage of the built-in troubleshooting commands
available in NetWare. For example, you can set MAP DISPLAY and MAP
ERRORS to ON in the login script. It's common for administrators to
set these parameters to OFF, hiding mapping errors that occur during
login script execution. With these settings on, you'll be able to see
the error, providing clues as to why a certain command did not execute
as expected. After seeing that the login script performs all map
commands without error, the MAP DISPLAY and MAP ERRORS parameters can
be returned to the OFF position.
COMMON LOGIN SCRIPT PROBLEMS--PART 1 OF 2
If you have a series of paths set in your AUTOEXEC.BAT file, your
login script may overwrite some of these paths. The reason for this is
that NetWare PATH statements are set up as search mappings when logged
onto the network starting with s1, s2, and so on. When you
specifically MAP (S1:=), then you overwrite the existing search
mapping. To avoid this problem, use a MAP INS on the search drives,
pushing the existing statements down the line without overwriting.
COMMON LOGIN SCRIPT PROBLEMS--PART 2 OF 2
Be extremely careful when you use the EXIT command in your login
scripts. Entering the command using the correct syntax is critical.
For example, you need to make sure the path and command you put in the
quotes are not more than 14 characters long. The early versions of
LOGIN.EXE in 3.1X and the LOGIN.EXE in 4.1 don't support more than 14
characters in the path. Also, remember that EXIT will exit you clear
out of the login script, not allowing any other login scripts to run.
If there is a user or profile login script that a user needs to
execute, you should not use EXIT to get out of the system/container
login script.
NDS UPDATE FOR NETWARE 4.11
Novell has identified a problem you may experience when installing
one or more NetWare 4.11 servers and NetWare 5 servers into the same
Directory Services tree. The problem could cause corruption in the
tree. To avoid the problem, Novell now provides an update that
contains the updated files DS.NLM v6.03 and DSREPAIR.NLM v4.63. This
DSRrepair addresses schema definitions that may not have been properly
time-stamped if your tree began life with a NetWare 4.0 or NetWare
4.01 server. For more information and to download this patch, visit
http://support.novell.com/misc/patlst.htm
QUICK NETWORK ADAPTER INFORMATION
Can you get everything you want to know about your network adapter
with one command? Well, maybe not everything, but certainly some
valuable information when you need it quick. On your Windows 95/98/NT
workstations, just type
IPCONFIG /all at a command prompt. IPCONFIG will display the card
description, physical address, IP address, subnet mask, and more.
INTERMITTENT FAILURE OF NETWARE LOGIN
If you're experiencing intermittent failures when logging in to
your NetWare servers, the problem may lie with licensing. When a
Windows NT client logs onto a NetWare NDS tree, a licensed connection
to the NetWare server is required. If your NetWare server is out of
licenses, NT can't establish a connection, causing the login script to
fail, and no access will be allowed.
Novell recently released a new set of patches the address several
known issues with its Z.E.N.Works 1.1 product. The fixes address the
following issues:
An attempt to update a file in use on a Windows NT workstation will
fail if the user is not a member of the Administrators group. With
apps marked Force Run, Run Once, and Prompt Distribution, if the
prompt is declined, the user is repeatedly prompted to rerun the
application. A GPF occurs when distributing a registry key with no
value. The GPF occurs on Windows 3.x only. For more information and to
download this patch, visit
To address several known problems in its BorderManager product,
Novell recently released a patch kit--Support Pack 1 for BorderManager
Enterprise Edition v3.0 for the product. This patch kit contains
general fixes to the BMEE 3.0 product, and Novell recommends it for
all BMEE 3.0 installations. For more information and to download this
patch, visit
http://support.novell.com/misc/patlst.htm
NETWARE 5 SUPPORT PACK 2
Novell has released its latest Support Pack for its NetWare 5 OS.
The new Support Pack 2 contains updates for all services contained in
the NetWare 5 box and provides a bundle of fixes that are tested
together. Novell recommends that you don't install individual files
from the Support Pack. For more information and to download this
patch, visit
http://support.novell.com/misc/patlst.htm
GROUPWISE 5 NT GATEWAY FOR EXCHANGE PATCH
Novell has identified a host of problems with its GroupWise 5 NT
Gateway for Exchange. The problems that you may experience include the
following:
· A GPF occurs while processing certain inbound messages.
· The gateway cannot obtain the configuration information during
initialization if a UNC path is used.
· A GPF occurs while processing an inbound message with OLE
attachments.
To address these and other issues, Novell recently released a patch
file for the product. For more information and to download this patch,
visit
http://support.novell.com/misc/patlst.htm
MANAGEWISE 2.6 FIXES
Novell has released an updated version of its Support Pack for
ManageWise that addresses several known bugs. The ManageWise 2.6
Support Pack 1 provides all ManageWise 2.6 patches since the
ManageWise 2.6 release. To download this patch and find more
information, go to
http://support.novell.com/misc/patlst.htm
TROUBLESHOOTING NETWORK ERRORS WITH WINDOW 95 SYSTEMS
If you're accessing NetWare 3.x and 4.0x servers from Windows 95
workstations, you may experience regular login problems. Packet burst
processing most likely causes these problems. To work around them, you
can comment out PBURST.NLM in your AUTOEXEC.NCF file. Unfortunately,
you'll notice a performance hit across your routers and WAN links.
The best solution is to patch the server(s) with PBWANFIX.NLM,
which is included in the PBURST.EXE patch file. Novell has addressed
and fixed this problem in NetWare v4.1x and above.
SLOW ACCESS FROM NOVELL'S CLIENT FOR WINDOWS NT
Are you noticing a slowdown when loading applications on a
workstation that isn't connected to the network? When you use the
Novell IntraNetWare Client for Windows NT, applications sometimes load
very slowly if the workstation isn't connected to the network. Using
the Microsoft Client for NetWare, the client's performance is fine.
The problem is that the application attempts to get printer
information from the printers installed on the workstation. As a
workaround, type
NET STOP SPOOLER
at a command prompt on your workstation. The client stops printing
from functioning, and the applications can no longer query the print
services.
This command is only temporary. After you restart the workstation,
you'll have to re-enter the command if you disconnect from the
network.
LPTX INVALID SELECTION ERROR
If you try to run NPrinter 95 (NPTWIN95.EXE) on your Windows 98
laptop with a printer attached to LPT1, you may receive an error
message (This Printer Is Configured To Use LPT1 And LPT1 Is An Invalid
Selection For Your PC) when selecting a printer to service. To avoid
this problem, perform a Windows registry search for all occurrences of
the string PORTNAME (all uppercase) and replace each with
PortName
MPREXE.EXE ERRORS FROM WINDOWS 98
You may experience a few lingering problems from your Windows 98
workstations. For example, if you have a Windows 98 computer logged
onto a Novell network and it is running a program that uses an older
GetOpenFileName() API, you may see this error:
MPREXE.EXE Caused An Invalid Page Fault In Module KERNEL32.DLL
Microsoft states that this is because of a problem with its Client
for NetWare Networks and Service for NetWare Directory Services
(MSNDS) network clients. A fix will be available in the next service
pack.
PACKET BURST AND WINDOWS 98 CLIENT FOR NETWARE
You still may experience a few lingering problems from your Windows
98 workstations. For example, if you run Windows 98 with the Microsoft
Client for NetWare on a NetWare 3.12 or 4.01 server and packet burst
is turned on, you may have some problems. According to Microsoft,
these problems also affected Windows 95. The company advises that you
get the patch file PBURST.EXE from Novell at
http://support.novell.com
NDPS PRINT JOBS SPOOL FILES
What happens to print jobs when you send them to your networked
printers? When you send an NDPS print job, NetWare spools it to a .PA
directory (on the SYS volume) that is associated with the Printer
Agent for the printer in question. If you want to know the name and
full path of the directory, at the server console, go to the NDPS
Manager Available Options menu, choose Printer Agent List, and then
choose the Printer Agent for the appropriate printer. Finally, choose
Information, and you'll see an entry for Job Spool Location toward the
bottom of the screen.
NETWARE 5 EVALUATION OR DEMO LICENSE INSTALL/UNINSTALL
A warning to those who have installed the NetWare 5 evaluation or
demo license on a server: Don't attempt to remove your NetWare 5
evaluation or demo license from the server/tree. If you do, you won't
be able to reinstall the license, because evaluation and demo licenses
can be installed into the same server only once. Even if you removed
the tree and created a new one, you still wouldn't be able to use the
same license--NetWare Licensing Services, not Directory Services,
tracks the installation of licenses.
CONTROLLING ACCESS TO NDS OBJECTS
If you need to assign additional NDS rights to users, start with
the default assignments. Defaults are in place to give users access to
the resources they need without giving them access to resources they
don't need.
Also, avoid assigning rights using the All Properties option. This
protects private information about users and other resources on the
network. Although assigning property rights using the All Properties
option may seem easier, this option grants many property rights that
users do not need.
Finally, use Selected Properties to assign property rights. This
allows you to assign more specific rights and helps you avoid security
problems.
CONTROLLING ACCESS TO NDS OBJECTS
If you need to assign additional NDS rights to users, remember that
granting the Supervisor object rights implies granting the Supervisor
rights to all properties. For some container administrators, you might
want to grant all object rights except the Supervisor right, and then
grant property rights using the Selected Properties option.
Also, use caution when filtering Supervisor rights with an IRF. If
the network administrator who has the Supervisor rights to the
container administrator's user object deletes the user object of the
container administrator, that branch of the NDS tree can no longer be
managed.
Z.E.N.WORKS CRITICAL FILES
For Z.E.N.Works to function properly on your Windows 95 or Windows
NT systems, several DLL files must be present on the client computer.
These files are transferred to the computer during the Z.E.N.Works
client software installation. Each DLL relates to a specific
Z.E.N.Works policy. The DLLs and their respective policies are as
follows:
WSREG.DLL--Workstation Registration
WM95CSP.DLL--Computer System Policies
WM95USP.DLL--95 User Policies
WM95ROAM.DLL--Roaming Profiles
WM95INV.DLL--Workstation Inventory Policies
WM95PM.DLL--Desktop Preferences Policies
SAFE WAY TO DOWN A FILE SERVER WHEN CONSOLE IS HUNG
If your NetWare 4.11 server is frozen, you can still safely down
the server even though you don't have the console prompt. This will
not work for hard hangs since the server will not accept input from
the keyboard. The console can get hung for a variety of reasons,
although the most common hang is caused by unloading an NLM and the
console doesn't come back.
You can still toggle screens and drop into the debugger by holding
down Ctrl-Alt-Shift-Esc or Ctrl-Alt-Esc. You'll then see the prompt
Down The File Server And Exit To DOS (Y/N). Selecting Y and pressing
Enter will close down the database and exit you to the DOS prompt.
DISPLAYING ADMIN RIGHTS IN NETWARE 4.x
If you're administering a NetWare network for the first time and
don't know who has Admin rights, you can quickly find out by using the
NLIST command. In the PUBLIC directory of your server, type
NLIST USER WHERE "Security Equal To" EQ "Admin"
You'll then see a list of all of the users in your NDS tree with
Admin rights. You can view other NLIST search commands by typing
NLIST /?
UNDERSTANDING THE LOGIN SCRIPT HIERARCHY
Login scripts can prove difficult to troubleshoot. You'll have much
more success if you know where the login script text files are located
and in which order the login scripts run. If you are running a 3.1x
network, you'll have three types of login scripts--the system, user,
and default login scripts. Here's the order in which NetWare executes
these scripts. First, if a system login script exists, it executes
first. Next, the user login script runs. If no user login script has
been defined, a default login script will run.
You'll find the system login script in the SYS:PUBLIC directory in
a file named NET$LOG.DAT. You can edit this file using any text
editor. You'll find the user login script in the user's mail directory
in a file named LOGIN.
PLANNING FOR INTRANETWARE SETUP
When you install IntranetWare, you'll have the option of setting up
multiple volumes. While you may be tempted to create one large SYS:
volume to hold everything, doing so is not recommended. One reason is
that you don't want to locate your print queues on your SYS: volume.
If your print queues fill up, NDS will become disabled. Follow the
planning guides available on your IntranetWare CD or on the Novell Web
site to plan your volumes well.
DEFAULT LOGIN SCRIPTS
NetWare embeds the default login script in the LOGIN.EXE command,
meaning that you can't modify the file or the script. This script will
execute without regard for previously run scripts. For example, if the
default login script runs after a system login script, it may
overwrite mappings the system login script just made. You can prevent
the execution of the default script by including the EXIT script
command. The EXIT command in the system login script will cause
LOGIN.EXE to exit immediately without executing any further
instructions in the current or subsequent scripts. Also, on 3.12
networks only, LOGIN.EXE supports the script command NO_DEFAULT.
Placing this command in the system login script prevents the default
script from running, even if no user script exists.
LOGIN SCRIPTS AND NETWARE 4.1
With NetWare 4.1, you need specific rights to use the login
scripts. For example, you must be a trustee of the object and have at
least the read right to the login script property to run the script.
This read right is all you need to run the login scripts. You don't
need the browse right, since it gives the object only the right to be
seen by another object--you don't have to see the login script to run
it. NetWare 4.1 stores the login scripts in NDS, meaning that you
should not attempt to make changes by any means other than through the
4.1 NETADMIN and NWADMIN utilities.
TROUBLESHOOTING LOGIN SCRIPTS--PART 1 OF 3
What's the number-one cause of problems in login scripts? Most of
the problems NetWare administrators and users face with login scripts
are the result of syntax and spelling errors. Correcting spelling
errors and using variables in the right way (for example, putting
quotes around a login name being tested in an If/Then condition)
resolve many problems. Double- and triple-check for spelling and
syntax errors before moving on to more complex troubleshooting
techniques.
TROUBLESHOOTING LOGIN SCRIPTS--PART 2 OF 3
To help you track progress (or lack of progress) in your login
scripts, take advantage of the built-in troubleshooting commands
available in NetWare. For example, you can set Map Display and Map
Errors to On in the login script. It's common for administrators to
set these parameters to Off, hiding mapping errors that occur during
login script execution. With these settings on, you'll be able to see
the error, providing clues as to why a certain command did not execute
as expected. After seeing that the login script performs all map
commands without error, the Map Display and Map Errors parameters can
be returned to the Off position.
TROUBLESHOOTING LOGIN SCRIPTS--PART 3 OF 3
Another built-in command that can prove helpful in troubleshooting
login scripts is the Pause command. Use the Pause command prior to the
script command that doesn't work as expected. Run the script, looking
for the errors. Keep moving the Pause command down through the script
until you isolate the problem in the script.
COMMON LOGIN SCRIPT PROBLEMS--PART 1 OF 2
If you have a series of paths set in your AUTOEXEC.BAT file, your
login script may overwrite some of these paths. The reason is that
NetWare PATH statements are set up as search mappings when logged onto
the network, starting with s1, s2, and so on. When you specifically
MAP (S1:=), then you overwrite the existing search mapping. To avoid
this problem, use a MAP INS on the search drives, pushing the existing
statements down the line without overwriting.
COMMON LOGIN SCRIPT PROBLEMS--PART 2 OF 2
Be extremely careful when you use the EXIT command in your login
scripts. Entering the command using the correct syntax is critical.
For example, make sure the path and command you put in the quotes are
not more than 14 characters long. The early versions of LOGIN.EXE in
3.1X and the LOGIN.EXE in 4.1 don't support more than 14 characters in
the path. Also, remember that EXIT will exit you clear out of the
login script, not allowing any other login scripts to run. If there is
a user or profile login script that a user needs to execute, you
should not use EXIT to get out of the system/container login script.
If you're installing IntranetWare, you have two choices for
installation--Simple or Custom. The Simple installation streamlines
the process, but it may cause you more work down the road. A good rule
of thumb is: If your network will consist of only one or two servers
and fewer than 1,000 users, you'll need only one NDS container; if IPX
is the only protocol you'll use, then you'll be fine using the Simple
install. However, if you'll have multiple servers with more than 1,000
users, you'll need multiple NDS containers; if you plan to use TCP/IP,
you should use the Custom install, which will give you much more
control over the process.
When you install NetWare on most high-end server systems that use
RAID 5 and advanced disk drive technologies, NetWare automatically
enables the Read After Write Verification setting. Since most of these
manufacturers provide this capability within the drive, you can turn
off this setting to increase performance. To do this, you'll alter the
SET command from your NetWare server console.
Novell recently released a patch that addresses several known
problems you may experience on NetWare versions 3.x and 4.x. The patch
contains a new STRTL7.EXE file that contains STREAMS, TLI, SPXS, and
IPXS NLM update files. It addresses a host of problems, including
several abend errors. You can download the patch file
Recovering deleted files on your NetWare volumes just got easier.
As you know, recovering deleted files, or even getting detailed
information about these files, can be tough. Fortunately, utilities
like Salvage 98 make it easier. Salvage 98 works with your NetWare 3,
NetWare 4, IntranetWare, and IntranetWare for Small Business server
providing a wealth of information about your deleted files. Using
Salvage, you can view info about each deleted file, including the file
size, who deleted the file, and the date the file was deleted. You do
all this using a Windows Explorer-like interface, making the task of
file recovery easy. For more information about Salvage 98 1.0, visit
http://wiredred.com
To download the utility, visit the Novell FTP site at
What's the limit on the number of objects you can put in a
container? You may not get a consistent answer to this question. For
example, the NDS Design class materials from Novell say the number is
100. However, the advanced 4.x administration materials say 500. Why
the confusion? The answer is that there is no limit within the base
NDS. Any problems you may have faced were with displaying the objects
within a container, not a physical limit. For example, NetWare 4.01
could effectively process about 1,200 objects, while the newer
versions can process 12,000 to 15,000 objects per container (a sign
that if you're running into problems, you might want to rethink your
structure).
Looking for useful shareware, freeware, utilities, and tools for
Novell NetWare? If so, make your first stop Dave's Novell Shareware
Web site. You'll find an extensive selection of utilities and tools
for every version of NetWare. It's a well-organized catalog of useful
shareware and freeware. If you have a utility or tool you'd like to
share, you can list it free on this site. Check out this NetWare
toolbox at
As you know, NetWare allows you to create aliases that represent
objects in your NDS. Why should you bother with aliases? These little
gems can make your tree structure easier for end users. For example,
you can create an alias for a mobile user, placing it at the top of
the tree, helping him or her during authentication. Since aliases
contain very little data, replication traffic is limited to the name
and the data for a pointer to the real object, speeding up the
process. Or, you can place aliases of your most-accessed printers,
print queues, servers, and server volumes in an easy-to-access
container. Now, instead of clicking around through the tree trying to
find an object, it's a click or two away.
NDS has four types of replicas--Master, Read/Write, Read Only, and
Subordinate--each designed for specific purposes. Here's a brief
description of each.
The Master replica is a writable replica that can also handle
partition operations--only one master replica per partition. Only one
partition operation is valid at any time for a partition, and the
master enforces that requirement.
The Read/Write replica is a writable replica that, like the master,
can be updated from the client. Both read/write and masters are valid
for login and authentication requests.
The Read Only replica cannot be changed from the client, getting
updated only with the changed data in the replica from another
read/write or master. This replica cannot be used for bindery
emulation because there must be a writable replica on the server for
bindery users.
The Subordinate replica is a replica of the partition root, which
includes the replica list (ring). As a child partition, it will reside
on every server that holds a copy of the parent partition, but not of
itself.
Several NetWare 3.x programs require the use of a supervisor
account in Bindery mode. However, providing this access on your 4.x
server could put a hole in your security. The best way to handle this
is to create a new container on the server, then create a supervisor
account in this container. Finally, create a replica of a partition
(containing this container) on the server. Creating this supervisor
account creates an object named supervisor in the directory; however,
this account won't be available as the server supervisor in the
bindery services mode on the server. This process creates two distinct
supervisor accounts--one for normal use and one for the program.
Netoria Directory Extensions (NDIRX) is an NWADMIN snap-in that
extends the NDS schema and provides administrators with an NWADMIN
page to manage three additional directory paths for each user, similar
to the user's home directory. You can map additional drives from
within any login script, using them for purposes such as mapping mail
directories, mapping group directories, and mapping organizational
directories. NDIRX fully supports NetWare 5, NetWare 4, and
IntranetWare, with both 32-bit and 16-bit versions. It also supports
all IntranetWare NWADMIN features such as multiple user selection and
user templates. Best of all, NDIRX is free. For more information,
visit the Netoria Web site at
Does it make sense to have a single server be responsible for all
replicas? In some cases, the answer is yes. For example, having a
central server makes backing up the NDS tree easier, allowing you to
back up the entire tree from one server. Also, tree walking on the
central server is faster both on external or subordinate references.
However, in other cases, a single replica server may not be the best
solution. For example, the single server will have to communicate to
all servers in the tree that hold any type of replica. It will be
updating replicas, sub ref time stamps, external reference backlinks,
etc., on every server. This server will have to receive all updates
made in the tree (such as object creations, deletions, modifications,
login time stamps, etc.), which means that every change in the network
will be replicated to this single server. Weigh the options carefully
as you plan your network.
Looking for specialized tools and utilities for Novell's
IntranetWare? If so, you'll be interested in JRButils from JRB
Software. JRButils v4.00 contains 73 bindery-based and 64 NDS-aware
utilities for managing IntranetWare. The utilities are command-line
based and cover almost all aspects of managing NW 2.x, 3.x, and 4.x,
providing far greater functionality and flexibility than the tools
shipped with IntranetWare. They are particularly suited for managing
large numbers of users, allowing operations to be performed on objects
selected by wild cards, container, membership of a group, or by a list
in a file. JRButils is suited to batch mode operations such as mass
usercode creation, customization, and deletion. For more information,
see
With NetWare 3, we were used to having a guest account that we
could quickly assign for limited access to our networks. With NetWare
4, you can create a guest equivalent as well, granting rights to users
for access to the tree. However, this requires a separate account for
guest privileges. Another option you might use is to grant the rights
that you would have granted to the guest user to public. This gives
guest rights to all connected users. The downside to this option is
that no authentication is required to access these resources, which
means that you're potentially compromising your NDS security. The most
recommended solution is to grant the rights to [root] rather than to
public, which gives guest rights to ALL authenticated users in the
tree. Thus, users can authenticate as themselves and access the
resources (servers, volumes, services, etc.) that are for guest use.
This allows for flexibility for granting rights to public services
without compromising security.
ROOT PARTITION REPLICATION CONSIDERATION--PART 1 OF 3
While it may sound like a good idea to place replicas of the root
partition on all or most of your servers to speed up the tree
walking/name resolution process, you should weigh the options
carefully. Remember, there are tradeoffs in placement of the root
partition. Multiple replicas may provide faster name resolution, but
you may sacrifice performance on the WAN because of synchronization
traffic. It can also cause administrative problems, since it requires
that all servers stay in communication. For example, partition
operations involving that partition would require that every server be
up and reachable. If one of those many servers were down or
unreachable, the administrator couldn't perform tasks such as creating
a new partition or merging a partition with its parent.
ROOT PARTITION REPLICATION CONSIDERATION--PART 2 OF 3
Weigh the options carefully before you place replicas of the root
partition on all or most of your servers to speed up the tree
walking/name resolution process. Synchronization poses another problem
with placing replicas of the root partition on most of your servers.
Each of these servers holds the same replica list, requiring it to
stay in constant communication with every other server. The time it
takes to synchronize will increase drastically as the number of
servers increases. To be safe, you should place replicas of the root
partition only in each campus environment, hubs of the company, or key
locations, but not on every server in those locations.
ROOT PARTITION REPLICATION CONSIDERATION--PART 3 OF 3
Before you place replicas of the root partition on all or most of
your servers to speed up the tree walking/name resolution process,
consider the options carefully. You may not want to place replicas of
the root partition on all or most of your servers because of the
effect on the NDS cleanup process, which executes when all
synchronization has been successful. If one or more of your servers is
down or unreachable, the cleanup processes won't run until all servers
have been reached and synchronized to that time in the database.
Again, instances of the root partition should be placed in each campus
environment, hubs of the company, or key locations--but not on every
server in those locations.
Novell has released an update to the support pack for NetWare
5--Support Pack 2. This support pack contains updates for all services
included in the NetWare 5 box. The support pack provides a bundle of
fixes that were all tested together. Installing individual files from
the support pack is not recommended.
These files have undergone component testing, core OS testing, and
integration testing with other Novell products. This download file was
rebuilt to correct an install problem in which the complete set of SMS
components was not copied to the server. In some cases, this may cause
backup products to become unstable. Look for the file nw5sp2a.exe on
the Novell Technical Support Web site at
To add support for SFT3, Novell recently released an update to the
NWPA (NetWare Peripheral Architecture) files, including the latest
HAMs, CDMs, and CDROM.NLM for v3.12, v3.2, and v4.x. The NWPA.NLM,
NWPAIO.NLM, NWPAMS.NLM, NBI.NLM, and CDROM.NLM files are the same
revisions as those found in Support Pack 6a for NetWare 4.11. The HAMs
and CDMs included in this download are the latest certified and
release versions available at this time. This download kit is provided
to allow 4.10 and 3.x customers to take advantage of the NWPA
architecture. This update fixes problems including changes made to the
frontend. The command line parser was also fixed to allow more than
256 characters in the command line string. You can download the update
file nwpaup1a.exe from the Novell Technical Support Web site at
Here's another Y2K patch from Novell. This file contains the latest
version of CLIB for NetWare 3.12 and 3.2. This new release of CLIB.NLM
contains two fixes for Year 2000 (Y2K) issues, including a problem in
which the wrong day of the week is returned by applications using the
CTIME API after Feb. 29, 2000, and a problem in which the wrong date
is returned by applications using the API STRFTIME with the %D
parameter. These problems are seen with NLMs developed using ANCII C
source code, with the Novell APIs STRFTIME and CTIME. Novell states
that these problems are seen only with NetWare versions 3.12 and 3.2
and have not been observed in NetWare version 4.x or 5.x. You can
download the update file named lib312c.exe from the Novell Technical
Support Web site at
Having trouble with the Novell Client v4.6 for Windows NT? If so,
you need to be aware of a new service pack for this client--Service
Pack 1. This service pack contains updates that address issues with
the Novell Client v4.6 for Windows NT, including:
Automatic install with unattended.txt file option; the process
hangs Cannot execute programs from Start/Run when using DNS names path
Cannot browse directories when opening a connection to server Client
drops mapping a drive in a DOS box using a DNS name Remote control
option not in the custom install of the 95 and NT clients Unattended
installation with NWIP-protocol gets error You'll find the service
pack in the file nt46sp1.exe on the Novell Technical Support Web site
at
Novell has released a patch kit for the Novell Client v4.5x for
Windows NT. This patch addresses several known problems you may
experience with the Client, such as:
NT AutoLogon is incompatible with NWIP The NetWare Client for NT
shows USERWHO in banner A simultaneous login hangs Terminal
Server/Metaframe The semaphore is not released when using the API
NWClosesemaphore NT Client and NAL loads slowly (remote replica) DOS
error 5 is encountered during network startup. Timeout and access are
denied to tsinst.ovr You can download the patch file named nt451p1.exe
from the Novell Technical Support Web site at
Novell continuously posts updates to its client files, providing
revisions and fixes for known issues. If you're using the Novell
Client v3.1 for Windows 95/98, you'll want to download the latest
service pack for this client--Service Pack 1 for the Novell Client
v3.1 for Windows 95/98. This service pack addresses all known issues
discovered since the release of the client, including these problems:
Disappearing printers CMD will not work on certain computers DNS
will not work if DHCP lease is expired Application cannot be launched
using STARTRUN Client tries only the first address from a list of IPs
Volumes cannot be accessed when opening from Start You can download
this service pack--9531sp1.exe--from the Novell Technical Support Web
site at
Are you running Novell's Client v3.0 and v3.01 for Windows 95/98 on
your workstations? If so, you'll be interested in the latest
patch/update file from Novell. This update, named 9530p1.exe, includes
fixes for several problems, including the following:
NetWare Client for NT shows USERWHO in banner Unable to
authenticate on Windows 98 using dialup networking after the first try
ZEN printer policy package duplicates printer FoxPro databases are
deleted; issuing a DEL .* deletes all files on a network drive. The
same command would fail on a local drive with the message File Not
Found. You'll find this patch file on the Novell Technical Support Web
site at
Novell has released a patch for its GroupWise 5.x Gateway for
cc:Mail product on the Microsoft Windows NT platform. This patch
addresses some known issues and provides the option of verifying
GroupWise account creation at the destination post office before
initiating mailbox migration. It also provides control over the
GroupWise domains and cc:Mail post offices that can participate in
directory operations.
You'll find the patch in the file ccmln1.exe, which is available
for download from the Novell Technical Support Web site at
Novell recently released an update to the CyberPatrol filtering
tool provided with BorderManager 3.0. This patch file, named
bm3cp2.exe, includes fixes for two known issues. First, it resolves a
problem that occurred if an access control rule to deny access to
categories on the CyberNot list was created. When requests came
through the Transparent Proxy, some requests to search agent sites
were blocked even though they were not part of the denied categories.
Second, it resolves a cosmetic problem with the registration screen
showing the registration date incorrectly. You'll find this file on
the Novell Technical Support Web site at
Are you running Novell's X.400 NLM Gateway? If so, you'll be
interested in downloading x400nlm1.exe, a new patch that addresses
several problems and provides a few updates, including:
Y2K fix: The gateway now converts two-digit years to four-digit
years. Fixed abend in the X.400 gateway. Free called with a memory
block that has an invalid resource tag. Fixed abend that occurred when
receiving certain types of messages. The running process was
ngwx400__P. The cause was a page fault processor exception. Corrected
a daylight-saving time problem with the gateway. If an appointment was
scheduled through the gateway within a daylight-saving time period,
the time was off one hour. The time is now correct. Outbound status
tracking now works correctly. You'll find this patch on the Novell
Technical Support Web site at
HOW TO LOGIN WITHOUT RUNNING THE SYSTEM/USER LOGIN SCRIPT
The DEFAULT login script built into LOGIN.EXE executes after the
SYSTEM login script (NET$LOG.DAT) when there are no USER login
scripts. The solution is either to use an Exit command at the end of
the SYSTEM login script or to create individual USER login scripts.
The latter approach requires more work, but creating USER login
scripts has a security benefit.
Time synchronization occurs at two times. The first is when the
shell or redirector makes a connection to a server (the NOT-LOGGED-IN
connection, which gives you access to SYS:LOGIN). To disable this
connection from setting your workstation's time, use SET STATION TIME
= OFF in your NET.CFG.
The second time is during the login process. In the absence of a
SET_TIME OFF command in any login script executed by the user, the
workstation's time will be set to that of the fileserver. This command
is supported in LOGIN.EXE, which ships with NetWare 3.12 and 4.x; you
can download it from the usual places for earlier versions.
Are you running Novell's X.400 NLM Gateway? If so, you'll be
interested in downloading a recently released patch, x400nlm1.exe,
from the Novell Web site. This patch addresses several known problems
and provides a few updates, including
* Y2K fix: The gateway now converts two-digit years to four-digit
years. * Fixed abend in the X.400 gateway. Free called with a memory
block that has an invalid resource tag. * Fixed abend that occurred
when receiving certain types of messages. The running process was
ngwx400__P. The cause was a Page Fault Processor Exception. *
Corrected a daylight savings time problem with the gateway. If an
appointment was scheduled through the gateway within a daylight
savings time period, the time was off by one hour. The time is now
correct. * Outbound Status Tracking now works properly.
You'll find this patch on the Novell Technical Support Web site at
Looking for a way to collect and report information about the users
on your NetWare network? If so, you should give UserInfo 2.0 from
Thompson Software a try. This shareware utility gathers and displays
user-related data from your IntranetWare or NetWare 4 networks. You
can view usernames, the date and time users last logged in to the
network, and login time restrictions. UserInfo provides several ways
to sort and view the data, including a handy way to sort the data
based on the Last Login Date/Time field. This sort allows you to
identify users with inactive connections, then use the utility to
delete those connections.
UserInfo 2.0 also gathers and displays server-related data such as
loaded NetWare Loadable Modules (NLMs) and the values of enabled SET
parameters. For more information about UserInfo 2.0, visit
Managing the NetWare printing process has always been a challenge.
Fortunately, some very useful third-party utilities work with NetWare
to make this task easier for both end users and administrators. One
such utility is NovPrint 3.0 from Thompson Software. NovPrint is a
complete printing utility that provides easy control of the printing
process on your IntranetWare or NetWare 4 networks. NovPrint provides
tools for both users and administrators. As an administrator, you can
use NovPrint to assign printers to particular network print queues,
change global printer attributes, access print queue monitors, change
the placement of print jobs in a network print queue, delete these
print jobs from the network print queue, and more. As an end user, you
can check the status of network print queues and local printers, hold
print jobs, and change printer options such as form feeds and banners.
For more information about NovPrint 3.0, visit
Most network users are familiar with Winpop--a simple Windows
pop-up messaging system. Now there's Winpop Plus 1.0, an enhanced
version of the popular utility. Winpop Plus adds functionality not
found in the standard version, including the ability to send broadcast
or personal messages over multiple protocols.
Winpop Plus also allows you to open files, run applications, and
initiate chat sessions from your NetWare workstations. Winpop Plus
provides support for Novell Directory Services (NDS) and the NetWare 3
bindery, allowing you to select the workstations you want to target on
your company's network or intranet. For more information about Winpop
Plus 1.0 and to download a trial copy, visit
ENABLING LONG FILENAME SUPPORT ON INTRANETWARE OR NETWARE 4.11
Need to enable long filename support on your IntranetWare or
NetWare 4.11 server? Here are the steps you'll need to take: First,
you need to ensure that you have the latest patch kit installed (check
the Novell Web site Technical Support area). Next, to load long
filename support, at the server console prompt, type
LOAD LONG.NAM Then, type
ADD NAME SPACE LONG TO VOLUME Finally, to prevent the need to
perform these steps each time you restart your server, add the load
commands for the LONG.NAM to your AUTOEXEC.NCF file.
Imagine the performance increase you would get if you could install
a second network card in your server and share the traffic load
between it and the existing card. You can do this by taking advantage
of a NetWare feature known as load balancing. Load balancing allows
you to bind two network cards to the same IPX network address (this
process works only for the IPX protocol).
To enable load balancing on your 4.x server, you'll use the INETCFG
utility. In INETCFG, enable NLSP routing and define the maximum number
of path splits. Then, turn on Load Balancing with a set command at the
server console prompt. Next, at the server console, type
LOAD IPXRTR (Be sure you are using the current version of IPXRTR.
As of mid-1998, this is the common version found in IPX65G.exe. Note:
The version of IPXRTR that ships with NetWare 4.10 does not support
load balancing.) Next, type
LOAD INETCFG and select Protocols, IPX, Advanced IPX (set to
Enabled), Routing Protocol (NLSP with Rip/Sap Compatibility), Expert
Configuration Options, Maximum Number of Path Splits (set to the
number of cards that will be used in load balancing). Then, exit
INETCFG and save the changes. You'll need to reinitialize the system
to make the changes take effect. Next, you need to set the Set Load
Balance Local LAN to On and add the command to your AUTOEXEC.NCF to
have it automatically load in the future.
Need a quick report that displays important server information?
There's a utility--CONFIG.NLM--that gathers NetWare server
configuration information, including a list of loaded modules, NCF
files, INET config file, speed rating, total RAM, set parameters, disk
information, volume information, name space information, LAN
information, and system files. When you run CONFIG.NLM, it creates a
text file (CONFIG.TXT) in the SYS:SYSTEM directory that contains this
information. You can download this useful utility from the Novell Web
site at
Novell recently released an update to its ODI
Specification--Version 3.31. This update affects several support
modules such as NBI, MSM, and TSM for Novell NetWare file servers.
This ODI update adds support for Hot Plug PCI and for removing a
single instance of a driver. You can get the full details and download
the update in a file named odi33g.exe on the Novell Support Web site
at
ENABLING LONG FILENAME SUPPORT ON NETWARE 4.1 AND 3.11
Need to enable long filename support on your NetWare 4.1 or 3.11
server? Here are the steps you'll need to take. First, you need to
ensure that you have the latest patch kit installed (check the Novell
Web site Technical Support area). Next, to load long filename support,
at the server console prompt, enter
LOAD OS2.NAM Then, type
ADD NAME SPACE OS2 TO VOLUME Finally, to prevent the need to
perform these steps each time you restart your server, add the load
commands for the OS2.NAM to your AUTOEXEC.NCF file.
GroupWise administrators will be glad to know that Novell recently
posted an update to the Support Pack for GroupWise 5.5--Support Pack
2. This update includes fixes and improvements to the GW
Administration, GW Agents (Internet, NLM, NT, and WebAccess), and GW
Client (Win 95/98/NT) components. You'll find the English version of
Support Pack 2 on the Novell Support Web site. Look for the file
g552en.exe at
If you're running Novell's GroupWise 4.x API Gateway, you'll be
interested in obtaining the latest patch from Novell. This patch fixes
several known problems you may have experienced, including:
Abends that occurred while the gateway was processing a directory
list. Abends caused by memory allocation/free error. The gateway would
not free memory when it was stopped. If the gateway was not stopped
for a long period of time, an abend would eventually occur. You'll
find the patch in the file GW41API.exe on the Novell Support Web site
at
Novell recently released an update to its ODI
specification--version 3.31. This update affects several support
modules such as NBI, MSM, and TSM for Novell NetWare file servers.
This ODI update adds support for Hot Plug PCI, and for removing a
single instance of a driver. You can get the full details and download
the update in a file named odi33g.exe on the Novell Support Web site
at the following URL:
If you're running Novell's GroupWise 4.x API Gateway, you'll be
interested in obtaining the latest patch from Novell. This patch fixes
several known problems you may experience, including:
* Abends that occurred while the gateway was processing a directory
list. * Abends caused by memory allocation/free error. The gateway
would not free memory when it was stopped. If the gateway was not
stopped for a long period of time, an abend would eventually occur.
You'll find the patch in the file gw41api.exe on the Novell Support
Web site at the following URL:
Attention NetWare 4.2 administrators! Novell has posted an
additional year 2000 patch for your version of NetWare. This patch
fixes a problem with the UIMPORT.EXE tool, which fails to create
expiration dates properly for both passwords and accounts when the
dates are greater than 1999. Novell states that none of the year 2000
issues addressed by this update pose any threat to the network or to
data integrity. You can find additional information about Novell's Y2K
fixes at
http://www.novell.com/year2000
For the patch described above, look for the file 42y2kp1.exe on the
Novell Support Web site at
Looking for additional training on the NetWare 4.11 to NetWare 5
Update? If so, you should check out the self-study program available
from Novell. It is an excellent tool for Certified Novell Engineers
(CNEs) because it is based on Novell's instructor-led Course 529 and
prepares CNEs for the corresponding certification exam that will
update their certification to NetWare 5. If you support and maintain
NetWare networks, you will find this kit is extremely helpful in
preparing you to migrate to NetWare 5. It is also a great on-the-job
reference. For details, visit the Novell Education Web site at
Are you experiencing Page Fault errors on your NetWare 4.1/4.11
server? If so, here are a few tips for resolving these errors. First,
add the following in the server AUTOEXEC.NCF:
SET Read Fault Notification = On SET Read Fault Emulation = On SET
Write Fault Notification = On SET Write Fault Emulation = On
Make sure that you have the latest LAN driver versions and the
latest disk driver versions. Finally, if you continue to see Page
Fault errors (without Abend), contact the manufacturer of your NIC and
disk controller to obtain the latest available driver versions.
Need to change the name of a server on your 4.1x network? Here are
the quick and easy steps:
1. Make sure that NDS is synchronized correctly (SET DSTRACE=ON).
2. Change the file server name in AUTOEXEC.NCF of the server. 3. Down
the server. 4. On another server, do a RESET ROUTER. 5. Wait five
minutes, then reboot the server that has been renamed. 6. Check
DSTRACE again to make sure NDS is synchronized. 7. Go into
NETADMIN/NWAdmin to rename volume objects associated with the server.
Are you upgrading to Fiber and not sure what frame type to use? The
only defined and necessary NetWare frame types for IPX on FDDI are
FDDI_802.2 and FDDI_SNAP.
If you're running ETHERNET_802.2 IPX clients, use FDDI_802.2 for
IPX on your servers. If you're running ETHERNET_II IPX clients, use
FDDI_SNAP for IPX on your servers.
If you're running ETHERNET_II TCP/IP clients, you MUST use
FDDI_SNAP for TCP/IP on your servers. If you're running ETHERNET_SNAP
AppleTalk clients, you MUST use FDDI_SNAP for AppleTalk on your
servers. Finally, don't use ETHERNET_802.3, ETHERNET_SNAP, or
"FDDI_RAW" for IPX, and you'll be fine.
Are you experiencing drive mappings that are created twice or to
the root directory? If so, the cause is most likely because the
default login script is running along with your system login script.
To avoid this double duty, put the line
Do you need to limit the amount of disk space a given user can
access on a volume? No problem. In NWADMIN, click on the volume
object. From the menu, choose Object, Details, See User Space Limits,
or click on the directory under the volume. Then choose Object,
Details, Facts, and Restrict Size to make the change.
NetWare 5 brings with it the realization of clustering. Novell's
clustering solution for NetWare, code named Orion, will be released in
three phases. The NetWare 5 file system, along with integrated
directory services, provides the foundation for a solid clustering
solution. You'll be able to cluster up to 16 nodes, depending on your
configuration. To find out more about Novell's clustering solution,
visit the Orion section of the Novell Web site at
Novell's new NetWare 5 makes management easier with the integration
of the Domain Name Servers (DNS) and Dynamic Host Configuration
Protocol (DHCP) into the Novell Directory Services (NDS). NetWare 5
provides the benefits of NDS (centralized management, replication,
fault tolerance) to industry-standard DNS/DHCP utilities. This should
reduce the amount of time you spend administering IP names and
addresses.
DNS/DHCP Services also supports Dynamic DNS, allowing for dynamic
updates of host names based on changing IP addresses. It includes a
Java-based management application that allows you to monitor,
configure, and manage the DNS and DHCP services in NDS. It also easily
imports existing DNS and DHCP data into NDS.
Z.E.N.works, Novell's desktop management tool suite, is designed to
help reduce the overall cost of ownership for your workstations by
reducing the time you spend managing the systems and making them more
efficient for the end-users. NetWare 5 includes a Z.E.N.works Starter
Pack, providing you the chance to try it out on your network.
Z.E.N.works helps you automate time-consuming tasks such as
application and operating system updates or upgrades. You can take
over someone's system across the network, saving you the time normally
spent running around the office from workstation to workstation. It's
a suite of tools worth checking out.
For more information on Z.E.N.works, visit the Z.E.N.works area of
the Novell Web site at
NetWare 5 includes a new and improved backup utility. This new
utility is protocol-independent, adds multiple and repetitive
scheduling, and supports the Windows 95-based GUI utility and
autoloader. It also takes advantage of NDS by allowing central
management to back up jobs across the network.
NT domains using NDS? Is it possible? Yes, with Novell's NDS for NT
(available for NetWare 5 as a separate product). NDS for NT lets you
manage NT domains and Microsoft BackOffice through NDS, providing a
single login, single point of administration, and full NT application
support for mixed NetWare and NT networks. NDS for NT should save you
time and money when managing and administering a mixed NetWare/NT
Server network and simplify the deployment of NT Server applications.
Attention NetWare 4.2 administrators! Novell recently posted an
additional year 2000 patch for your version of NetWare. This patch
fixes a problem with the uimport.exe tool in which it fails to create
expiration dates properly for both passwords and accounts when the
dates are greater than 1999. Novell states that none of the year 2000
issues this update addresses pose any threat to the network or to data
integrity. You can find additional information about Novell's Y2K
fixes at:
http://www.novell.com/year2000
For the patch described above, look for the file 42y2kp1.exe on the
Novell Support Web site at the following URL:
One of the most significant new features of NetWare 5 is its
support for Internet Protocol (IP) as a core protocol. In NetWare 5,
all NetWare Core Protocols can use the TCP/IP transport protocol,
giving customers the ability to run in a "Pure IP" environment--pure
in the sense that it doesn't retain an IPX-based encapsulation (or, in
the case of NT Server, a NetBIOS encapsulation). This allows you to
select the protocol that best suits your needs. If you require IP,
NetWare 5 will simplify your life by eliminating multiple protocols
and freeing up valuable network bandwidth.
Network security is more critical than ever as our networks grow
from internal to global. Network administrators spend a lot of time
tightening and fine-tuning NetWare's many security features. However,
one step that many neglect to take when considering network security
is physical access to the servers. You can set up the tightest
security possible, but if an employee or hacker can walk up to your
server and down it or gain access, you're doomed.
Your servers should be accessible only to those who need physical
access. Put your servers in a locked room. If your servers reside in a
data center with other systems, you may even consider a lockable rack
or cabinet. Some server boxes have locking covers, preventing access
to the system drives. You may feel a little paranoid, but you can't be
too safe. Lock it up!
As network administrator, one of the most challenging tasks you may
face is rebuilding your network after a crash or devastating hacker
attack. That's why it's important that you keep copies of some of the
more important files archived, ready for use if needed. For example,
you should have copies of your STARTUP.NCF and AUTOEXEC.NCF files. You
should back up your bindery or NDS, as well as System Login Scripts
and Container Scripts. Keep these copies offsite or in a secure place.
Then, hope that you never need them!
NetWare includes a powerful tool for monitoring activity on your
network--the Security utility. You'll find the utility in the System
subdirectory. Security provides a wealth of information about who is
accessing the network, who has supervisor rights, what trustee
assignments they have, and more. You should run the report often,
comparing results and looking for dramatic changes in activity or to
rights. This should help you identify potential security holes or
hackers.
NetWare includes a useful utility--CONLOG.NLM--that tracks all
activity at your server console. Once you load the NLM, NetWare
creates a logfile, called console.log, in your SYS:ETC directory. In
this logfile, NetWare stores all console information, including error
messages. This can prove handy, since an active server can quickly
fill up the screen, scrolling off important messages before you have
the chance to view them. You can view this logfile at any time,
tracking errors and looking for unauthorized activity.
Confused about all the versions of NWADMIN.EXE and which one you
should use? Follow these guides:
NWADMN3X.EXE is the NW 4.11 version for Windows 3.x.<P NWADMN95.EXE
is the NW 4.11 version for Windows 95. NWADMNNT.EXE is the NW 4.11
version for Windows NT.
The NetWare 4.11 version will also work with earlier NetWare 4
versions, but they don't support MHS or the "old style" of user
templates. In a mixed NetWare 4.10/4.11 environment, user templates
can be used without a problem.
If you're running Novell's NetWare 4, you'll be interested in
downloading and applying the latest fixes and updates, which are
available in Support Pack 7. Support Pack 7 contains updates for all
services contained in Novell's NetWare 4.11 and NetWare 4.2 products.
Novell released this support pack to provide a group of fixes that
were all tested together; the company emphasizes that you should not
install individual files from the support pack. You can order the
Support Pack 7 CD from the Novell support Web site at
Novell recently released a service pack to address a few issues
with its Novell Client v3.1 for Windows 95/98. The service pack fixes
the following problems you may experience when using the client:
· Disappearing printers
· CMD will not work on certain computers
· DNS will not work if DHCP lease is expired
· Application cannot be launched using STARTRUN
· Client tries only the first address from a list of IPs
· Volumes cannot be accessed when opening from Start
Novell notes on its support site that your NetWare 4.11/4.2 servers
will require an update before you can install this client service
pack. The server update is located in the NetWare 4 Support Pack 7.
You'll find the Client Support Pack in the file 9531sp1.exe at
If you're running Novell's NetWare 3.12, you should download and
apply the Y2K patches for your version of NetWare. You can download
these fixes in the file 312y2kp2.exe, available from the Novell
support site. If you're running NetWare 3.2, you don't need this
patch, since this release includes the updates found in this patch. To
obtain the 3.12 Y2K patch, visit
KEEPING UP WITH THE LATEST REQUIRED NOVELL CLIENTS
It's tough to keep up with the changes to Novell's client software.
Fortunately, Novell posts a text file on its support Web site that
lists all of the clients and their latest versions. You can view this
file at
Looking for an easy way to view server configuration information?
If so, check out the Server Configuration Information program,
available for download from Novell support. This tool displays volume
size in megabytes, loader version on NW v4.x, serial number, ABEND.LOG
on NW v4.11, part of IO$LOG.ERR and MSSTATUS.DMP, TIMESYNC.CFG and
ATPS.CFG, and whether compression, suballocation, and migration are
enabled on each volume. This tool runs as CONFIG.NLM on your server,
and it works on all versions of NetWare. You can download the tool in
the file confg8a.exe from
Novell has identified a problem that you may experience on your
NetWare 4.11 servers. The problem occurs when an application running
on Windows 95/98 workstations opens the same file multiple times on
the same connection and then closes it. Novell says that with the
Novell client on Windows 95/98, the file is not being closed out
correctly when it closes on multiple opens. Ultimately, if this is
allowed to continue, the server will run out of resources and hang. To
resolve this issue, Novell has released a patch for NetWare 4.11 and
4.2. You can download the patch in the file revfhrft.exe, found on the
Novell support Web site at
Novell has identified additional issues related to the Y2K problem
and its NetWare 4.10 product. These issues affect the LOADER.EXE and
RCONSOLE.EXE features. For example, one issue could result in the file
server abending at the year 2000 rollover to 1/1/2000. Using the SET
TIME command, the BIOS clock would also be reset to the year 1980. To
address these issues, Novell provides the file 410y2kp2.exe, which you
can download from
Are your NetWare 4.11 servers ready for the new year? To be sure,
you should download and apply the latest version of Novell's Y2K
patches for 4.11. You'll find them in the file 411y2kp2.exe at
Having trouble with your Windows NT workstations running Novell's
Client for NT? If so, you should check out the latest update to the
Client--version 4.6. The patched client addresses a host of issues,
including:
· Automatic install with "unattended.txt" file option; the process
hangs
· Cannot execute programs from Start/Run when using DNS names path
· Cannot browse directories when opening a connection to server
· Client drops mapping a drive in a DOS box using a DNS name
· Remote control option is not in the custom install of the 95 and
NT clients
· Unattended installation with NWIP-protocol gets error
· Selected server or tree could not be found (error message)
· Database locked error with Business Works and NT client
· IE4 Dr. Watson error with Zen-installed printers
· Login screen pops up on Terminal Server You'll find the new
client in the file nt46sp1.exe at
Looking for extra tools to help you through the day as
administrator of your NetWare 4.x and 5 servers? If so, try out the
utilities found in TOOLBOX.NLM version 2.01. You can execute this
group of utility functions on the server console or via NCF files
without involving any clients. You'll find TOOLBOX.NLM in the file
etbox2.exe, available from
Do you need extra tools to act as administrator of your NetWare
3.12 and 4.0x servers? Try out the utilities found in TOOLBOX.NLM
version 1.09. You can execute this group of utility functions on the
server console or via NCF files without involving any clients. You'll
find TOOLBOX.NLM in the file tbox7.exe, available from
Clients connecting to NT Server 4.0 using Novell's IPX protocol may
experience difficulty if you've just installed NT Service Pack 3. To
repair this problem, run Regedt32 from the Start, Run command line. To
resolve the problem, open the following key and add the values below:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\
Services\LanManServer\Parameters Value Name: MinClient-BufferSize Data
Type: Reg_Dword Data: 500 Radix: Decimal
Looking for a tool to make server management a little easier? If
so, check out AdRem Server Manager, which helps you monitor and manage
NetWare servers and is designed to make even the most complicated
tasks easy for knowledgeable server administrators and beginners. With
this tool, you can monitor all connections between stations and the
server--for instance, files opened on the server--and manage files and
directories. The client/server version also allows multiple server
managing: software distribution and simultaneous configuration
comparisons and console command executions. AdRem Server Manager is
available in English, German, and Polish. For more information, visit
http://www.adremsoft.com/products.htm
FIXING NETWARE 4 WITH THE SUPPORT PACK
If you're running Novell's NetWare 4, you'll be interested in
downloading and applying the latest fixes and updates, available in
Support Pack 7. This contains updates for all services in Novell's
NetWare 4.11 and NetWare 4.2 products. Novell tested the fixes in this
Support Pack as a group, and emphasizes that you should not install
individual files from it. You can order the CD from the Novell Support
Web site at
Novell recently identified some additional issues related to the
Y2K problem and its NetWare 4.10 product. These issues affect the
loader.exe and rconsole.exe features. For example, one issue could
result in the file server abending at the year 2000 rollover to
1/1/2000. Using the Set Time command would also reset the BIOS clock
to the year 1980. To address these issues, Novell provides the file
410y2kp2.exe containing updates to these files, which you can download
at the following URL:
Having trouble with your Windows NT workstations running Novell's
Client for NT? If so, you should check out the latest update to the
Client--version 4.6. The patch addresses a host of issues, including
the following:
* Automatic install with unattended.txt file option problem in
which the process hangs. * Client cannot execute programs from
Start/Run when using DNS names path. * Client cannot browse
directories when opening a connection to a server. * Client drops
mapping a drive in a DOS box using a DNS name. * Remote control option
not in the custom install of 95 and NT clients. * Unattended
installation with NWIP protocol gets error. * "Selected server or tree
could not be found" error message. * "Database locked" error with
Business Works and NT client. * Internet Explorer 4 Dr. Watson error
with Zen-installed printers. * Log-in screen pops up on Terminal
Server.
You'll find the new Client in the file nt46sp1.exe at the following
URL:
If you're running Novell's NetWare 3.12, you should download and
apply the Y2K patches for your version of NetWare. You can download
the NetWare 3.12 year 2000 fixes in the file 312y2kp2.exe, available
from the Novell support site. If you're running NetWare 3.2, you don't
need this patch, since this release already includes those updates. To
obtain the 3.12 Y2K patch, visit the following URL:
Are your NetWare 4.11 servers ready for the New Year? To be sure,
you should download and apply the latest version of Novell's Y2K
patches for 4.11. You'll find them in the file 411y2kp2.exe at the
following URL:
Novell recently released a Service Pack to address a few known
issues with its Novell Client 3.1 for Windows 95/98. The Service Pack
fixes the following known problems you may experience when using the
Client:
* Disappearing printers. * CMD will not work on certain computers.
* DNS will not work if DHCP lease is expired. * Application cannot be
launched using Start/Run. * Client only tries the first address from a
list of IPs. * Volumes cannot be accessed when opening from Start.
(Novell notes on its support site that your NetWare 4.11 and 4.2
servers will require an update prior to the installation of this
Client Service Pack. The server update is located in the NetWare 4
Support Pack 7.)
You'll find the Support Pack in the file 9531sp1.exe at the
following URL:
Novell recently identified a problem you may experience on your
NetWare 4.11 servers. The problem occurs when an application running
on Windows 95/98 workstations opens the same file multiple times on
the same connection and then closes it. Novell says that with the
Novell Client on Windows 95/98, file closes on multiple opens are not
closed out correctly. Ultimately, if you allow this to continue, the
server will run out of resources and hang. To resolve this issue,
Novell has released a patch for NetWare 4.11 and 4.2. You can download
the patch in the file revfhrft.exe, found on the Novell support site
at the following URL:
How secure is your NetWare server console? With access, users can
do almost anything--access user data, trace LAN/mainframe data, change
configurations, and destroy volumes. Natively, the console is
unaudited, often accessed through shared passwords, giving anyone who
uses the console full access.
SecureConsole for NetWare is a fileserver console security
application that controls the level of access individuals or NetWare
groups have to your console, including what console commands they can
use, what console applications they can see, and whether their actions
are audited. SecureConsole has system console autolocking and screen
saver features to protect your system from unauthorized users.
SecureConsole is an NDS-aware product. For more information, visit
In traditional NetWare environments, messages occurring on servers
are not always reported to systems administrators. ConsoleAlert allows
an administrator to generate SNMP alerts when messages appear on the
NetWare server console or third-party application screens. In addition
to alerting the administrator, ConsoleAlert can automatically take
corrective console actions as defined by the administrator. For more
information, visit
In some NDS environments, errors that occur on remote servers may
not be reported automatically to systems administrators. In these
cases, holdups can go undetected until user backlash bombards the help
desk or support staff. DSAlert is a diagnostic and network support
tool that enables Novell's Network Directory Services error conditions
to be monitored and reported. For more information, visit
If you're working with a mix of NT and NetWare, you probably are
aware of the performance problems that can occur between these
systems. Fortunately, you can improve the Microsoft network device
transport protocol configuration to minimize the time necessary to
discover new NetWare and Microsoft network devices (workstations,
servers, and so on).
Windows NT uses Remote Procedure Call/Server Message Block
(RPC/SMB) as the method of communicating between Microsoft networking
devices (NT servers and workstations, Windows 95/98/3.1x, and DOS).
RPC/SMB was written to use NetBIOS as a packet structure, and
Microsoft networking devices can encapsulate these NetBIOS commands
into one of three transport protocols: TCP/IP, IPX, or NetBEUI.
NetBEUI is the default transport protocol; even if all three
transport protocols are present, a Microsoft networked device will
default to NetBEUI first when attempting to locate a new network
device. Once this request has timed out, it will then try the next
transport protocol (the order is controlled in a registry key for
Windows NT/95/98). This continues until it has located the network
device or has tried all available transport protocols. Since NetBEUI
is not routable, any attempt to find a network device that is across a
router will fail. In the tips to follow, we'll share some solutions
from Novell.
You can improve the Microsoft network device transport protocol
configuration to minimize the time necessary to discover new NetWare
and Microsoft network devices, such as workstations and servers. To do
so, try this trick from Novell.
Disable or remove NetBEUI as a transport protocol. NetBEUI cannot
be routed (although it can be bridged), and any attempt by a Microsoft
network device to locate a target that is across a router will
fail--but not before a two- to four-second timeout period.
To do this, go to Control Panel/Network/Protocols, highlight
NetBEUI Protocol, and click on Remove. Click Yes to the message "This
action will permanently remove the component from the system. If you
wish to reinstall it, you will have to restart the system before doing
so."
To reconfigure the Microsoft network device transport protocol to
reduce the time it takes to discover new NetWare and Microsoft network
devices, such as workstations and servers, try this trick from Novell.
Configure TCP/IP as the primary transport protocol for NetBIOS
interface, server, and workstation. To do this, go to Control
Panel/Network/Bindings, display the bindings for NetBIOS Interface by
clicking on the + next to it, then highlight WINS Client (TCP/IP) and
click on the Move Up button so that this option is first. Make sure
that NWLink NetBIOS (this is IPX) is listed second.
Next, display the bindings for Server by clicking on the + next to
it. Highlight WINS Client (TCP/IP) and click on the Move Up button so
that this option is first. Make sure that NWLink NetBIOS is listed
second and that NWLink IPX/SPX Compatible Transport is listed third.
Now, display the bindings for Workstation by clicking on the + next
to it, then highlight WINS Client (TCP/IP) and click on the Move Up
button so that this option is first. Make sure that NWLink NetBIOS
(this is IPX) is listed second.
You can reconfigure the Microsoft network device transport protocol
to reduce the time necessary to discover new NetWare and Microsoft
network devices, such as workstations and servers. To do so, try this
idea from Novell.
If you're using an IP Novell environment (NetWare 5 server
environment or a mixed NetWare 4.11/5 environment with NetWare 5
compatibility mode enabled), configure TCP/IP as the primary transport
protocol for Novell's client. Otherwise, configure IPX as the primary
transport protocol for Novell's client.
To do this in an IP Novell environment, go to Control
Panel/Network/Bindings and display the bindings for Novell Client For
Windows NT by clicking on the + next to it. Highlight TCP/IP Protocol
and click on the Move Up button so that this option is first. Make
sure that NWLink IPX/SPX Compatible Transport is listed second.
In an IPX Novell environment, go to Control Panel/Network/Bindings
and display the bindings for Novell Client For Windows NT by clicking
on the + next to it. Highlight NWLink IPX/SPX Compatible Transport and
click on the Move Up button so that this option is first. Make sure
that TCP/IP Protocol is listed second.
Novell has released a patch for BorderManager 2.1 and FastCache
2.1b Proxy Cache which requires that IntraNetware Support Pack 6a
(IWSP6A.EXE) and the BorderManager Admin Snap-in Patch (BMADM2C.EXE)
be installed. The new patch contains Y2K fixes and addresses other
problems, including:
· Proxy cannot create log files when the date changes to 1 January
2000. It returns an Error 135 Creating Log File error.
· An abend occurs in Proxy FastFree.
· An abend occurs because ServerCbReinit called FastFree with an
invalid memory area.
· The proxy hangs (stops servicing HTTP requests).
· A memory leak in proxy eats up memory.
You'll find the new patch on the Novell support site at
Network administrators perform a lot of tasks to keep the network
up and running. Having the right tools is essential. One tool that
might help is NodeVision Wizard, which assists network administrators
in identifying problems by performing tasks, including:
Managing resources and metering software usage on NetWare and
Windows NT networks Scanning the details of node-level hardware and
software Identifying critical changes and displaying side-by-side
comparisons of before and after the changes Notifying the
administrator of changes on scanned nodes with a unique color code
that allows for instant identification of the problem areas For more
information, visit
ADDING FUNCTIONALITY TO THE DISPLAY SERVERS COMMAND
Novell's DISPLAY SERVERS command doesn't provide all of the
available information about your network. The Service Advertising
Protocol (SAP) makes a lot more information available, but you'll need
a tool to get to it. The tool for the job is SAPSQL v. 1.45 from
Midnight Technologies. SAPSQL NLM is a module that extracts additional
information out of SAP advertisements about servers and devices
connected to your network, including IPX addresses, SAP type, service
description, the company that registered the SAP type, and the
company's phone number. The product works on your NetWare 3.x/4.x
servers at a cost of $39.95 per server. For more information, visit
You've probably used PKZip to compress files on your PC's hard
drive, but did you know about a tool for compressing files on your
NetWare networks? ZipWiz-NLM is a PKZip-compatible compression and
decompression NLM that allows you to compress and decompress on your
server. End users can still decompress their own files at their
workstations with any zip-compatible tool, while you can save time by
compressing and decompressing with the power of your server rather
than needing to move those files to a workstation. ZipWiz-NLM handles
long names, preserves file attributes, and recurses subdirectories.
For more information, visit
Novell recently released a patch that fixes bugs discovered in the
Novell Internet Messaging System (Novell IMS) after the release of
Novell IMS version 2.00. All fixes in this patch will be released
officially with the first support pack for IMS. Novell notes that the
patch is designed for the shipping version (as of June 30, 1999) of
IMS. It includes all other patches. Look for the file nims200d.exe on
the Novell Support Web site at the following URL:
http://support.novell.com/misc/patlst.htm
----------------------------------------------
UPDATES FROM NETWARE 5 SUPPORT PACK 3 TO 3A
Novell recently released an update to its Support Pack 3 for
NetWare 5. This update contains the changed files from NetWare 5
Support Pack 3 to 3a. You should only install this update if you have
Support Pack 3 currently installed. You'll find the file, named
sp3to3a.exe, on the Novell Support Web site at the following URL:
http://support.novell.com/misc/patlst.htm
----------------------------------------------
NOVELL INTERNET MESSAGING SYSTEM UPDATE
Novell has released a patch that fixes bugs discovered in the
Novell Internet Messaging System (Novell IMS); these bugs were
discovered after the release of Novell IMS version 2.00. All fixes in
this patch will be released officially with the first support pack for
IMS. Novell notes that this patch is designed to be applied to the
shipping version (6/30/99) of IMS. It includes all other patches. Look
for the file nims200d.exe on the Novell support Web site at
Need help managing the use of space on your NetWare servers? If so,
you should check out FileWizard 3 from Knozall. This LAN-based file
management system for Novell servers and workstations allows network
administrators to automatically:
Generate comprehensive reports based on any criteria Move, copy,
delete, and migrate files found that match your criteria Automate a
complete HSM storage solution Use true NetWare migration to move aged
files to a storage volume (or Jukebox), which can then be accessed by
the end user on the fly Generate graphics that reflect server space by
volume, user, directory, and file extension Track how server space is
used Predict when additional space will be required For more
information, visit
If you've ever lost valuable data in compressed files and had no
way to restore it, you'll be interested in a utility called FixCFile
v. 1.21. This utility can help recover your valuable data that is
locked away in corrupted compressed files. FixCFile is a NetWare
Loadable Module for NetWare 4.1. It'll cost you $795.95 per site, but
only a few uses of the software could easily pay for it. For more
information, visit
If you've ever lost valuable data in compressed files and had no
way to restore it, you'll be interested in a utility called FixCFile
v. 1.21. This utility can help recover your valuable data that is
locked away in corrupted compressed files. FixCFile is a NetWare
Loadable Module for NetWare 4.1. It'll cost you $795.95 per site, but
only a few uses of the software could easily pay for it. For more
information, visit
Tracking file access and activity is essential to ensuring the
security of your network and the important files it handles. Using a
tool like Knozall's FileAuditor, you can audit all file activity. With
FileAuditor, you can record who opened, closed, deleted, and modified
files; notify individuals when specified file activities occur; and
deny access to specified files. You can also define which departments
and users should be denied access to specified files and write
customized scripts that can be executed based on predetermined file
activity or corporate policies. Finally, you can generate customized
reports, detailing file and directory activity. For more information,
visit
Novell can fill your server console and error log files with a lot
of unwanted network alerts. While critical alerts are important to
see, many alerts on a NetWare console fill the screen and error logs
with information that is not so useful. A utility called NoAlert helps
you manage these alerts. NoAlert v. 1.17 works on your NetWare 3.x and
4.x servers. For more information, visit
Novell has released the latest Engine and Signature version 4.24.8
for ManageWise. InocuLAN v4.0 has been updated to incorporate new
virus scanning signatures (v4.24.8) and performance improvements. This
release of the signature will detect new variants of known macro
viruses. This update provides changes to avupdate, service pack for
Windows 95 build 464, and service pack 2 for NetWare. Look for the
file mwinoc1a.exe on the Novell support Web site.
For the latest virus signature update and service pack for InocuLAN
v4.0 for Windows NT for the Intel platform only, look for the update
file mxinoc2a.exe. These files update your system to version 4.24.8
and also update to the NT service pack 2A build 375. You can use this
patch for either ManageWise 2.5 or 2.6. Look for both of these files
on the Novell support Web site at
File compression and archival is an important part of managing your
NetWare networks. Because of the nature of file compression and the
realities of disk storage, archived files may on occasion become
corrupted. To help you keep tabs on these compressed files, you can
use a utility such as CompMon, which runs as an NLM and examines
compressed files, reporting the extent of damage to them, if any.
CompMon v. 2.00 runs on your NetWare 4.1 servers. For more
information, visit
Looking for a utility to help you manage the backup and restore
process for NDS? If so, you should check out DeTroubler NDS
Backup/Restore from Future-Gate. DeTroubler is the only
object-oriented backup and restore product written specifically for
Novell Directory Services. Using DeTroubler, you can restore the
entire tree unattended or recover single objects or portions of the
tree with a single mouse click. This product works on your NetWare
4.10, Intranetware 4.11, and NetWare 5 servers. For more information,
visit
Wouldn't it be nice to perform a test run on NDS changes before you
put them in place on your live network? Now you can do just that. DS
Designer provides a familiar environment for NDSTree Design in which
all NDS operations are perfectly simulated, including partition
creations, merges, and moves; replica creations and deletions; server
insertions and deletions; and tree merges. Using this tool, you can
get a view of the results that will be realized on your live NDS Tree,
analyze the results, and decide if they are satisfactory before
executing them. For more information on DS Designer, visit
Novell has released an update to its update for NetWare 5. This
update contains the changed files from NetWare 5 Support Pack 3 to 3a.
You should install this update only if you have the NetWare Support
Pack 3 installed. You'll find the file sp3to3a.exe on the Novell
support Web site at
STORAGE ANALYSIS AND MANAGEMENT FOR NETWARE SERVERS
Collecting data about the network is one of the critical functions
of network management. FileWizard 5 from Knozall provides enterprise
storage management capabilities for Windows NT servers and
workstations, Novell NetWare networks, and UNIX servers running NFS.
You can view and report to determine what kind of files are on the
network, who owns them, when they were last used, how big they are,
and when servers will run out of space. FileWizard 5 gives you the
power to manage growing storage requirements without throwing hardware
at the problem. For more information, visit
Novell recently released the latest version of Clib for NetWare
3.12 and 3.2. The only changes since lib312c.exe are the inclusion of
updated after311.nlm and a3112.nlm files to address a possible memory
corruption issue. You can download this update in the file lib312d.exe
from the Novell Support Web site at the following URL:
http://support.novell.com/misc/patlst.htm
----------------------------------------------
DOCUMENTING YOUR NDS INFORMATION
Documenting network setup is a critical responsibility of network
administrators, and documenting NDS information is a critical
component of network documentation. DS Designer helps you create
complete documentation of your NDS Tree. By importing report files
into DS Designer, you can obtain:
Partition documentation, including parent/child partition
relationships Replica documentation, including how and where replicas
are distributed among servers Server documentation, including
IPX/TCPIP addresses and DS versions Schema synchronization
documentation, including information on how servers synch NDS schema
Object documentation, including all objects in your entire tree
organized by partitions, containers, and servers NDS warnings and
suggestions Schema documentation. Compare NDS schema between servers.
Choose servers randomly or report a certain server's distribution
list. For more information, visit
Network administrators are responsible for managing the use of
applications to avoid overuse of the software licenses. To help you in
this task, Knozall created Meter Wizard, which monitors application
use so you can forecast the need for additional licenses or upgrades.
You access the primary metering and management functions from the
Metering Console. From the console. you can install or remove metering
on all network applications and software suites, record details of
access for future reference, view user lists for specified
applications and graphic displays of license usage of metered
applications, and print usage reports. For more information, visit
Novell has released the latest version of CLIB for NetWare 3.12 and
3.2. The only changes since LIB312C.EXE are the inclusion of updated
AFTER311.NLM and A3112.NLM, which address a possible memory corruption
issue. You can download this update in the file lib312d.exe from
Novell support at
Automation can take on the load of costly, time-consuming,
repetitive jobs like data collection, analysis, monitoring, fault
management, and correction, and leave the IT department free to do
other tasks. One tool that helps with the automation of these tasks is
AutomationWizard from Knozall, which monitors server parameters and
conditions, detects when they are abnormal, and responds to alerts
from other analysis or warning systems. AutomationWizard can then
decide how to fix the problem and carry out those actions without
administrator interaction. The tool's scheduling options can run jobs
based on time, date, day of week, conditions, or events.
AutomationWizard can distribute and collect information from remote
sites. For information, visit
Navigating on your NetWare console isn't easy by default. Important
pieces of information can scroll off your NetWare screen, making them
unavailable and leaving you in the dark. PageUp alleviates this
problem. Simply load the NLM, then you can use the Page Up, Page Down,
up arrow, and down arrow keys. PageUp v. 1.10 works on your NetWare
3.x and 4.x servers. For more information, visit
Looking for a collection of useful DOS-based utilities? Wizard's
Tool Belt contains the following utilities that perform important
tasks on your Novell network:
FWGETACC--Gets and saves the last access dates for files on all
volumes and servers to which you are attached. FWRESACC--Restores the
last access date to the files in all volumes and servers to which you
are attached. For anyone running backups or virus scans, these
operations change the access date on every file they touch. That means
you lose valuable information about which files have been used
recently on your network. FWCHGUSR--Allows the supervisor to change
the user or "owner" of the files in a directory. During server
maintenance, the ownership of files is often changed to the
administrator or supervisor. This simple utility allows the system
administrator to change the user name for all files or specified files
in a directory to a specific user. Keeping file ownership up to date
and having the ability to modify it is useful when you have
chargebacks to users for storage space. FWACC2UP--Changes the date of
the last access to the date of the last update. If access dates have
been changed by a virus scan or backup, you can change them to the
last update so that you can track which files are used.
FWFIND--Searches all attached volumes and servers to find files that
match a given file spec, such as orphan files. The default search
looks through every server and volume that can be seen.
*Administrators can search the entire network with one command rather
than searching volume by volume or server by server. As part of the
file search, the administrator can prompt for a delete when the file
is found, specify servers or volumes to search on, or limit the search
to files belonging to an invalid user. FWCPYVOL--Copies all files
between volumes on the same server and maintains owners and
attributes. If you need to do maintenance on one volume, you can
create a backup of that volume instead of going through a backup or
mirroring routine. FWFILER--Provides a tree view with information
about files and directories that you can't get from NetWare. For more
information, visit
Need a tool that enables you to schedule and control tasks on a
server, as well as on multiple DOS or OS/2 clients? If so, check out
NLMAuto from Knozall, which enables you to execute commands on a
server and its clients without any administrator intervention. You can
schedule commands to run based on specific events, or you can schedule
them to run at a specified time. You can also monitor third-party
alert packages to respond to critical server alerts. For more details,
visit
Novell has released the new NetWare 4 Support Pack 7. You'll find
this update in the file nw4sp7a.exe on the Novell Support site. This
file contains updates for all services included in the NetWare 4.11
and NetWare 4.2 products. The support pack provides a bundle of fixes
that are all tested together, and installing individual files from the
support pack is not recommended. These files have undergone component
testing, core OS testing, and integration testing with other Novell
products. You can order the support pack CD at
http://support.novell.com/csp/
or visit the Novell Support Web site and look for the file at
Novell has released a patch file for GroupWise 5 NT Gateway for
Exchange--Patch 2. This patch file provides the following fixes to
some known problems:
Filtering switches /blockdom and /allowdom now work with directory
synchronization as well as with directory exchange. The gateway can
now initialize a migration in certain non-English environments.
GroupWise users will no longer be deleted if the location of the
gateway is changed to another domain. Mail from Exchange to GroupWise
now works with a userid on both GroupWise and Exchange. Mail sent from
a user on an external GroupWise domain to MS Exchange now does not
drop any recipients. The problem with replies to mail sent from the
Internet to MS Exchange through GroupWise 5.2 GWIA has now been fixed.
Replies will still not work if GroupWise 5.5 GWIA is used with
Internet addressing. You can find the patch in the file exchnt2.exe,
available for download from the Novell Support Web site at
Novell has released the latest virus signature update and service
pack for InocuLAN v4.0 for Windows NT for the Intel platform only.
These files update your system to version 5.02 and also update to the
NT service pack 2A Build 375. This patch can be used for either
ManageWise 2.5 or 2.6. You'll find the update file--mxinoc2d.exe--on
the Novell Support Web site at
Novell has released the latest Engine and Signature version 5.02
for ManageWise. InocuLAN v4.0 has been updated to incorporate new
virus scanning signatures (v5.02) and performance improvements. This
release of the signature detects new variants of known macro viruses
and provides changes to avupdate, service pack for Windows 95 Build
464, and service pack 2 for NetWare. Look for the file mwinoc1d.exe on
the Novell Support Web site at
NetWare's NDIR is a great tool, but it's not the easiest to use.
wNDIR is a Windows utility that provides most of the features of
Novell's NDIR, but in an easy-to-use format. Using wNDIR, you can
export data to a text file in several ways, and you can create
command/batch files to operate on the files found. You can use wNDIR
for any purpose--from archiving old data to listing the files owned by
a user. For more details, check out
Network management is a time-consuming, never-ending job. One tool
that might help ease the workload is WebConsole. This tool has
Web-based and directory-enabled features that allow IT departments to
set and monitor security levels, manage users, generate system status
reports, and solve problems on any enterprise server from any single
location using the Internet. For more details, visit
Need quick access to volume information on your NetWare servers?
VGadget can give you a status summary of any or all of the volumes on
your NetWare servers. VGadget can display free space, total space, and
the percentage of occupied space, and you can sort the data on any
column. You can copy the data to the clipboard for use in other
programs, and you can scan all the servers you are connected to, or
scan all the servers in a standard list. VGadget will connect to the
server if required. For more details, check out
Every network has them--disk hogs that take up tons of precious
space on the server. UserSpace is a tool that scans users' home
directories and reports on the amount of space used in each one. The
administrator can select any part of the NDS tree, and UserSpace will
report all the users from that point down. Get more details at
To address a host of known problems, Novell recently released a
patch file for GroupWise 5 NT Gateway for Exchange--Patch 2. This
patch file provides the following fixes:
* Filtering switches /blockdom and /allowdom now work with
directory synchronization as well as directory exchange * Corrects a
problem where the gateway couldn't initialize a migration in certain
non-English environments * Corrects a problem where GroupWise users
could be deleted if the location of the gateway changed to another
domain * Mail from Exchange to GroupWise now works with a userid on
both GroupWise and Exchange * Mail sent from a user on an external
GroupWise domain to MS Exchange now does not drop any recipients *
Fixes the problem with replies to mail sent from the Internet to MS
Exchange through GroupWise 5.2 GWIA (replies still don't work if
GroupWise 5.5 GWIA is used with Internet addressing)
You'll find the patch in the file exchnt2.exe, available for
download from the Novell Support Web site at
As network administrator, you need to know when servers aren't up
and running. ServAlert 2.0, a utility written for all Novell networks,
continuously monitors servers at preset intervals defined by the
system administrator. If a server goes offline for any reason,
ServAlert 2.0 will detect and identify the downed server, then dial
and page those personnel specified in the program. Should the server
come back online, the program will dial those personnel and notify
them that it is back online. The program also keeps an activity log,
which you can print, edit, or delete. For more information, visit
You need to cut off viruses before they spread across your network.
One tool that you might use to help in the battle against viruses is
Protector Plus, an antivirus software designed for NetWare servers. It
has an online NLM program to detect and remove all types of viruses
from the server. The files are scanned as soon as they are created or
accessed on the server. The software uses minimal server resources,
generates activity log files, and is easy to install and use. You can
download free monthly upgrades from the developer's Web site. This
software is compatible with NetWare 3.11 to 5.0. Site licenses are
also available. For more information, visit
Wouldn't it be great if you could schedule tasks at your server
console and have them run at specific times? Proschedule for NetWare
is an NDS-based server console scheduling utility that allows
administrators to schedule console jobs from NWADMIN on individual or
multiple servers simultaneously. This utility integrates with
ManageWise through SNMP to provide feedback on the status of jobs. For
more details, visit
If you've planned your network design carefully, you should rarely
need to change volume names on the server. However, there may come a
time when you must. Note: If you use INSTALL.NLM to rename volumes,
NWADMIN will continue to display the old volume names because
INSTALL.NLM does not update the NDS. However, NWADMIN obtains
information on volume objects from the NDS.
You can solve this problem by using DSRepair. After loading
DSRepair, choose Advanced Options, then select Check Volume Objects
and Trustees. DSRepair will report the number of volumes that have
been renamed and update the NDS. NWADMIN will now display the new
volume names.
As a network administrator, you may want to move newer NetWare
utilities to older servers, or you may want to copy these utilities to
a local drive on a workstation. LOGIN.EXE and NDIR.EXE are two such
popular utilities.
However, before you move these utilities, you should know which
unicode files should be moved as well. For most utilities, you can get
this information simply by running the utility itself using the /VER
parameter (for example, PCONSOLE /VER). Most utilities will generate
the needed support files in this way. If a .MSG file for the utility
exists, you should copy that file as well.
Novell has released an update to Novell Directory Services for your
NetWare 4.11 and 4.2 servers; this update addresses two problems.
First, DS could monopolize too many sockets under heavy load.
Modifications were made so that DS does not take too many sockets.
Second, there was a memory leak problem in which IP, IPX, and AFP were
bound on the server. Both problems are fixed with this update. Also,
enhancements were made to DSRepair to recognize schema changes made to
NDS. You'll find the update file named ds411s.exe on the Novell
Support Web site at
What do you do if your NT server crashes, you're using NDS for NT,
and you want to relink your NT domain with the NDS tree and Domain
object without manually re-creating the domain users and remigrating
them?
If you have a Backup Domain Controller in the domain that has NDS
for NT installed on it, you're in luck. All you have to do is promote
the BDC to a PDC, rebuild the original PDC, and demote the second PDC
when the original comes back online. If you don't have a BDC in your
domain, things get rougher. First, you'll have to reinstall NT on the
server using an emergency recovery disk for that specific server.
(This is important because the SID identifier for the server has to be
the same as it was originally.) Next, install NDS for NT and place the
new domain object in a temporary Organizational Unit. Make sure you
use the same name for the new domain and server that you used
originally. Delete the domain object and SAMMIG.EXE dated 4/17/98 or
later. (If yours is older, contact Novell Technical Support.)
SAMMIG will detect that the migrated domain no longer exists and
allow you to browse the tree for the original domain. It will then
update the NT registry to point to the original domain and regrant
user access to the domain. Reboot the NT server, and everything should
be fine.
If you use NDS for NT on your network to integrate your NetWare and
Windows NT servers, you may have encountered the following error when
trying to create a new user in User Manager for Domains on a domain
that you've migrated:
"You specified a Username which is already in use by another user.
Choose a Username which is not already in use by another user or
group."
This error can occur if there's an NDS object in the "Default User
Creation Context" of the NDS Domain Object with the same name as the
NT user you are trying to create. This object can be any NDS object,
not just a user or group. To avoid the error, make sure the new NT
name for the user or group is unique for both the NT Domain and the
NDS context.
If you've lost the license diskette for your server, don't call
NetWare's Technical Support Center. There's nothing the support center
can do about it. Instead, call Novell's Customer Response Center at
888-321-4272.
One of the nice things about the Novell Application Launcher is
that you can replace your user's regular Windows 95 or Windows 3.x
desktop with a NAL window. From the NAL window, you can control what
applications your users can and can't use. You don't have to worry
about them running programs they shouldn't or snooping around the
network.
The NAL window isn't escape-proof, however. If your user invokes
the Task Manager, either by minimizing the NAL window and
double-clicking the desktop or by pressing Ctrl-Esc, he or she can
click File and Run from Task Manager and run programs either locally
or on the network--or even invoke a copy of DOS.
To prevent this, either delete or rename TASKMAN.EXE on your users'
workstations. Then they won't be able to use this back door and sneak
out of the NAL window.
Novell has released a patch kit for Z.E.N.works 1.1. This kit
contains fixes for the following issues, among others:
Attempt to update a file in use on Windows NT workstation fails if
user is not a member of Administrators group. For applications marked
Force run, Run once, and Prompt distribution, the user is repeatedly
prompted to rerun the application if the prompt is declined. Search
drive in drive/ports fails. Remote control and Ctrl-Alt-Del are not
possible with Unisys Aquanta DX. "Run Only Allowed Windows
Application" fails if icon is delivered to the desktop. Windows NT
Start Menu shows Common applications when registry is set not to show
them. You can download the patch kit in the file zw110p3.exe, which
you'll find on the Novell Support Web site at
When you use Novell's Client32 for Windows 95 and log into your
server, have you noticed that your workstations will sometimes get the
right drive mappings, while at other times they won't? Most users have
encountered this inconsistency.
The problem is with your permanent drive mappings in Windows 95.
These mappings can conflict with drive mappings coming from your login
scripts. Don't attach to server drives and map them permanently from
inside Windows 95. Instead, use drive mappings from inside of login
scripts.
Novell recently released a Service Pack that contains updates for
the English version of Novell Client 3.1 for Windows 98 and Windows
95. Service Pack 2 addresses a lengthy list of problems, including the
following:
* Files close incorrectly on server * Program can't send e-mail via
IPX/IP GW in Nwclient 3 * Password synchronization between NetWare and
MS networking fails * Disappearing printers * CMD will not work on
certain computers * DNS will not work if DHCP lease is expired *
Application can't launch using STARTRUN * Server runs out of memory
due to multiple file opens
The list goes on. You can download the Service Pack in the file
9531sp2.exe from the Novell Support Web site at
Do you have a large NDS tree? Have you noticed problems running
NETADMIN? With large NDS trees, NETADMIN sometimes reports that it has
run out of memory. This is due to a limitation in DOS. If the NDS
container has more than 1,250 objects, reduce it. Novell recommends
never going over 1,250 objects per NDS container and per NDS
partition. With large numbers of objects, the DOS buffers become
overrun and the program can't handle it. You have two ways to fix the
problem:
1. Don't use the DOS NETADMIN to manage your NDS tree; use the
Windows versions instead. Windows 95 and NT handle program buffers
much better than DOS.
2. Reduce the number of objects in the NDS container in which the
problem occurs.
Novell has released a patch kit for the Novell Internet Messaging
System, version 2.01 rev a. You'll find the patches in the file
NIMS201A.EXE, which provides fixes and enhancements for the Novell
Internet Messaging System version 2.00. A note from Novell on this
patch: To upgrade to NIMS 2.01, you must have a released copy of NIMS
2.0. You cannot upgrade beta versions of NIMS 2.0 to 2.01. If your
installation of NIMS 2.01 failed, you do not have a recognized
released copy of NIMS 2.0. If you already have NIMS 2.01 and just want
to update to NIMS 2.01a, you should use NIMD201A.EXE instead of this
patch. Look for the file NIMS201A.EXE on the Novell Support Web site
at
Depending on your network configuration, you may be running more
than one IPX frame type. Microsoft NT Workstation 4.0 allows you to
specify only a single IPX frame type. Normally, if you want to use
multiple types, you can use the Autodetect option. If you use
Autodetect, NT searches for multiple frame types in the following
order:
Ethernet 802.2 Ethernet 802.3 Ethernet II Ethernet SNAP
This may not be the best order for your network. You can specify
more than one frame type to be bound when the network services are
initialized by making changes in the Registry. The key you'll need to
change is:
PktType is a multiple string value (REGEDIT32), which means that
you can make more than one entry as long as the values are on separate
lines. The following values are possible:
ff - Autodetect (cannot be used in conjunction with other values) 0
- Ethernet II 1 - Ethernet 802.3 2 - Ethernet 802.2 3 - Ethernet SNAP
4 - ARCnet
You can determine what frame types are bound by using the IPXROUTE
CONFIG command at a Command Prompt. Unlike NT Workstation, NT Server
doesn't restrict you to a single frame type.
It used to be that when you created volumes for large hard drives
on your NetWare servers, you'd use only a couple of hundred megabytes
for the SYS: volume and then dedicate the rest to a data volume. As
applications and utilities have grown, a small SYS: volume can cause
you lots of headaches. If the SYS: volume fills up, your server may
crash. As more and more products rely on NDS, they'll require more
space on your SYS: volume as well. Novell suggests that you make a DOS
partition big enough to store a coredump and some useful utilities,
approximately 512MB. Make the rest of the space the SYS: volume. Add
secondary hard drives for data, and mirror the SYS: volume for better
protection.
Welcome to The New NetWare newsletter. We will dive from the
5,000-foot overview level down to specific NetWare features and back
again as the situation demands. Think of this as alternating between
trends and a focus on details, not a demented yo-yo ride.
Critics doom Novell to lingering death every few months, usually
based on some new Microsoft initiative. It's true that Microsoft
Windows NT ran like a buzzsaw through Novell's installed customer
base. Novell officials no longer delude themselves they can "beat"
Microsoft, showing increasing maturity and realism.
On February 8th., Novell unveiled their new "iChain" initiative,
making e-commerce easier via NDS. This positive trend bodes well for
NetWare, for several reasons.
First, Novell actually puts something of value on top of their
superior infrastructure tools. NetWare contributed to Microsoft's
ascension by providing a reliable network platform that Microsoft
couldn't manage themselves.
Second, Novell now focuses on the applications rather than the
plumbing. Where does the directory service for policies, security, and
manageability stop and e-business applications start? Who cares?
NetWare finally defines the solution rather than just the
architecture.
Make no mistake: Microsoft executives would gleefully dance on
Novell's grave, but they have taken dance lessons for years with no
chance to perform on Novell's plot. Those of us who prefer NetWare
must continue to fight the good fight against the new Windows 2000
army.
Good news abounds for this continuing battle. For the first time,
Novell fans have a full arsenal, matching and beating every Windows
feature with one from NetWare. Novell marketing, revamped by CEO Eric
Schmidt, may actually be able to make a public case for continued
NetWare patronage, and even grab a few new friends. This newsletter
will give you the tools to maintain or even increase your company's
reliance on NetWare rather than taking the short term route and caving
in to Windows 2000.
Remember that short-term decisions often compromise long-term
success. Follow Novell's red brick road a little longer, and see for
yourself how the scenery has changed in NetWare's favor.
Almost as surprised by the Internet as much as Microsoft, Novell
scrambled to add Web server technology to NetWare. Hamstrung by the
convoluted NLM (NetWare Loadable Module) programming environment,
Novell settled for a third-party, weak Web server to package with
NetWare 4.
Quickly aligning itself with Netscape, Novell added the FastTrack
server to NetWare. Good, but not good enough. Windows NT boasted IIS
(Internet Information Server), along with a variety of third-party
products, all more powerful than the FastTrack server. Microsoft's
command of the developer market paid off as well. Anti-Microsoft
developers built Apache Web servers on top of Linux boxes, forsaking
NetWare.
Novell boosted its Netscape commitment, making Netscape's
Enterprise Server the standard Web programming platform for NetWare 5
-- big improvement. People may prefer other Web servers to Netscape's,
but they can't snub NetWare because its Web-server option lacks for
power or flexibility. If directory service matters, Enterprise Server
plugs directly into NDS.
How will this help your situation? Managers believe intranets
serving browser clients are the wave of the information-age future.
Following the hype, these managers drool over Linux, NT, or Solaris
systems crammed with critical documents.
Raise your hand and volunteer to host the intranet software on an
existing NetWare server. How will you counterbalance the hype
inundating the managers? Remind them you already have NetWare servers,
reducing their capital budget hit. They love that. Remind them a new
platform means new training for existing personnel or new personnel.
They hate that. Run an intranet pilot using NetWare without increasing
headcount or the training budget. They love that.
Once this pilot succeeds, expand it. Need another Web server for
customers? Why not NetWare? You already have proven hardware and
software in place. If the managers balk and still want Sun, Linux, or
NT, tell them how brave they are for boldly striking out in a new
corporate direction and hosting mission-critical information on
untested platforms with no in-house support. Such a brilliant
high-stakes gamble! They hate that.
Is NetWare 5.1 with Netscape Enterprise Server the ultimate,
never-to-be-beaten Web engine? No, but it's pretty high up on the
horsepower ratings today. Add NetWare's support for multiprocessor
servers, the renowned performance of NetWare file services, and tight
coupling of the Netscape server with NetWare core services -- and the
package stacks up well.
How well? Well enough that millions of Web hits per hour hit
NetWare servers every day with nary a glitch, problem, or "server
busy" message.
Did you know NetWare 5.1 includes free groupware with every
license? Nope, not GroupWise, but something easier, less-complex to
configure, and already familiar to most users.
"Collaborative computing" now claims official buzzword status,
especially when tied to the previous new buzzwords, "Web-enabled" or
"thin client." It all boils down to sharing information within a
closed group, capturing the give-and-take common with email exchanges
while structuring and archiving the information into a useful package.
Enough of a tease: NetWare 5.1 includes an NNTP-server software
module. Network News Transfer Protocol sounds complex, but it powers
the lowest common denominator of Internet interaction: news groups.
About 50,000 news groups (or more, and growing every day) are
available through your ISP, ranging from discussions in high-level
organic chemistry to ways to kill Barney, the purple dinosaur.
NNTP servers start easily and run with little administrative
overhead. If you can handle NetWare, you can handle a news server in
your sleep. Yet a small time investment in news-server setup can pay
big dividends for your company.
Jon Udell was editor of Byte Magazine and authored "Practical
Internet Groupware" for O'Reilly & Associates publishing. I spoke with
him recently when doing research for a groupware article.
"The information that's the lifeblood of a company is not in a data
warehouse, but in all the message traffic between people," says Udell.
"People live in email." Documents have value, says Udell, not just
because of the information inside, but because of the context wrapped
around the documents and their contained information.
Yes, email lists and CC: lists can help, but the information
scatters to hard disks here and yon. News servers collect and retain
all the messages in a central site. Any index server offers a quick
way to archive the material into a useful storehouse of corporate
information.
Company discussion lists open the doors for everybody to
participate and share their knowledge with the group. If your company
is like most, real knowledge is hard to find and should be preserved
whenever possible. Your NetWare 5.1 NNTP server will help, and it's
free.
The NetWare Management Portal appeared with NetWare 5.1, and this
utility alone may be worth the price of an upgrade. Any current
browser on your network can, with proper password authentication,
display more server information than NetWare has ever shown before.
There's no reason NetWare Administrator couldn't be upgraded to
have these same features, except that ConsoleOne has usurped the job
of primary management interface. Yet, the NetWare Management Portal
may be the winner in this race. It's slick, it's easy, it's complete,
and speedwise it's a Ferrari against ConsoleOne's minivan.
Yes, the browser makes a secure connection to the NetWare 5.1
server
over https://server-ip-address:specified-port. The front screen
puts the NetWare Management Portal banner across the top, with the
server name in the upper left corner just under the banner. Beside the
server name is a traffic signal light, showing green (good), yellow
(check something), or red (attention needed). Red doesn't
automatically mean a dead server, just that one of the 17 critical
displays has gone into red. In my lab, the LAN Traffic sometimes drops
to zero and the server gets worried the network board may be taking a
cigarette break. Then the next update catches some traffic, and all
goes green.
Page refresh rates are adjustable at 2, 5, 10, 30, and 60 seconds
and 5 minutes. Server health pages show the item being monitored (like
Available Memory or CPU Utilization), the status, the current setting,
the peak setting, and the maximum.
The home screen offers seven sub-pages: Volume, Server,
Application, NDS, or Hardware management, Remote Server Access, and
Health Monitors. Everything an administrator can handle with the
MONITOR utility and more can be handled inside the Server Management
pages.
In fact, more can be seen here than anywhere else with a Novell
utility. Want to see the date, version, and allocated memory of every
NLM running on your server? Go to Application Management, Address
Spaces / Memory Protection, and click the OS address space name. Want
to sort the 100 or so active NLMs on a server? Click the heading for
Code size, Data size, Allocated Memory, NLM Total (bytes) or NLM Total
(rounded). This information can be rooted out with MONITOR in NetWare
5.0, but only at great pain.
Display a dozen server health monitors on one browser screen,
updated every few seconds, and you'll never go back to MONITOR.
If you have not installed NetWare version 5 or 5.1, be prepared for
the new installation process. All the familiar tasks, such as
specifying server name, setting up volumes, and deciding protocols are
still there, of course, but they're wrapped in a graphical user
interface (GUI) rather than the long-familiar C-Worthy DOS interface.
Technical or political reasons for a GUI installation? I say
political all the way. Any computer company you can think of that's
been touting a GUI network server installation for years, blasting
NetWare for the DOS screens?
Novell just can't quite get it right in choosing which screens to
convert to GUI and which to leave in C-Worthy. I have criticized
recent versions of NetWare in various reviews because the C-Worthy
interface remains awkward for management, requiring deep menu
structures and no easy ways to move around. But initial server
installation screens as a GUI? No thanks. I don't want pretty, I want
a quick and easy setup.
Be warned: If you start to install a NetWare 5 or 5.1 server
without a mouse attached, restart. Novell uses the number-pad keys to
mimic mouse movements, but the mind-numbingly slow response makes root
canal work preferable. If you forget to add the mouse, or, like I do
half the time, miss the screen where you tell NetWare the mouse is
either a PS/2 or a serial model, give up and restart the process. I
guarantee you it will be quicker than using the number-pad keys for
mouse movements.
If Novell engineers had asked me, I would have told them to leave
an option for C-Worthy installation screens, but to use a GUI for all
later management.
The DOS C-Worthy screens work very well when zooming through
sequential installation screens. Installation goes much faster that
way than using the GUI for either NetWare or Microsoft Windows NT. But
management screens are a different story. NWCONFIG still in C-Worthy?
What a pain.
My wish: DOS installation screens, GUI management screens.
Unfortunately, Novell still has it backwards with NetWare 5.1.
Changes to this page are IN PROGRESS 