- NWADMIN Displays Old Volume Names
- Moving Newer
NetWare Utilities to Older Servers
-
What do I do when my PDC dies
using NDS for NT?
- Avoiding username errors
with NDS for Windows NT.
- Help! I've lost my server's
license diskette.
- Making your NAL Window escape-proof.
- Problems
with using Citrix WinFrame with Novell's intraNetWare Client for Windows NT.
- Why have my drive mappings gone nuts?
- How big should my SYS volume be?
- Binding
multiple frame types in NT Workstation 4.0 and Novell Client 32.
- Having problems with NETADMIN?
- Why is the Intranetware client
for NT so slow?
- Viruses and Client32 for Windows 95.
- Help!
I lost my tree.
- Where
do NDPS print jobs spool?
- ZENWorks
Workstation Manager DLLs
- Deleting
index files with CD PURGE
NWADMIN Displays Old Volume Names
If you have planned your network design carefully, you should rarely need to change volume
names on the server. However, we do not live in an ideal world and you should know the
implications of changing volume names if the need arises. As it turns out, if you use
INSTALL.NLM to rename volumes, NWADMIN continues to display the old volume names. This
happens 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.
NOTE: This procedure does not work for print queues on renamed volumes. You must delete
and recreate the print queues.
Moving Newer NetWare Utilities to Older Servers
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 by simply running the
utility itself using the /VER parameter, e.g. 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.
What do I do when my PDC dies using NDS for NT?
Sometimes something goes wrong and your servers crash. There's no controlling it. But what
do you do if your NT server crashes and you're using NDS for NT and want to relink your NT
domain with the NDS tree and Domain object without manually re-creating the domain users
and re-migrating 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 has to do is promote the BDC to a PDC, rebuild the
original PDC, and demote the second PDC when the orginal 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
orginally) 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 orginally. Delete the domain object and SAMMIG.EXE dated 4/17/98 or later. (If
yours is older contact Novell Technical Support.)
SAMMIG detects that the migrated domain no longer exists and allows you to browse the tree
for the original domain. It will then update the NT registry to point to the original
domain and re-grant user access to the domain. Reboot the NT server, and everything should
be fine!
Avoiding username errors with NDS for Windows NT
If you use NDS for NT on your network to integrate your Netware and Windows NT servers,
you may have enountered 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.
Help! I've lost my server's license diskette
If you've lost the license diskette for your server, don't call Netware's Technical
Support Center. There's nothing they can do about it. Instead, call Novell's Customer
Response Center at 888-321-4272.
Making your NAL Window escape-proof
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 desktops 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 completely escape-proof however. If your user invokes the Task
Manager, either by minimizing the NAL Window and double-clicking
the desktop or pressing [Ctrl][Esc], they can click File and Run from Task Manager and run
programs either locally or on the network. They can even
invoke a copy of DOS.
To prevent this, either delete or rename TASKMAN.EXE on your users' workstation. Then they
won't be able to use this backdoor and sneak out of
the NAL Window.
Problems with using Citrix WinFrame with Novell's intraNetWare
Client for Windows NT
If you use WinFrame on some of the Window NT workstations on your network along with
Novell's Intranetware Client for Windows NT, you're probably
having problems. You're not alone.
When Citrix developed WinFrame they were given access to the source code of the Microsoft
Graphical Identification and Authentication (GINA). They
updated it to include it as part of the WinFrame solution. The installation program of the
Novell intraNetWare Client v4.10 for Windows NT replaces the
Microsoft GINA with Novell's GINA named NWGINA. Because a component of the WinFrame
solution is hard-coded in the Microsoft GINA, when customers install the intraNetWare
Client v4.10 for Windows NT, the WinFrame solution no longer functions correctly.
Novell's release of the intraNetWare Client v4.11 for Windows NT in August 1997 attempted
to work around this problem. When you install this verion of
client, it detects if the Citrix WinFrame product has been installed. If it has, the
installation program won't replace the default Microsoft GINA.
This will allows you to use both the WinFrame product and the Novell intraNetWare Client
for Windows NT. However, doing so makes the Client not
fully functional.
Novell is working with Citrix to get the code that is currently only in the Microsoft GINA
moved from the Microsoft GINA to WinLogon so that the
WinFrame solution will not be limited to functioning only when Microsoft's GINA is loaded.
This modification has to be performed and delivered by
Citrix. Novell also plans to modify the manner in which NWGINA stores configuration
information for the WinFrame solution to be complete when
used in conjunction with the intraNetWare Client for Windows NT. So hang in there!
Why have my drive mappings gone nuts?
Have you noticed that when you use Novell's Client32 for Windows 95 and log into your
server that sometimes your workstations were get the right drive
mappings while sometimes they don't? Sometimes this problem inconsistently happens to all
many different users at many different times.
The problem is with your permanent drive mappings in Windows 95. These mappings can
conflict wit hdrive 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.
How big should my SYS volume be?
Used to be that when you created volumes for large hard drives on your Netware servers,
you'd only use a couple of hundred megabytes for the SYS:
volume and then dedicate the rest to a data volume.
As applications and utilties 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 are becoming reliant on NDS, they'll require more space on your
SYS: volume as well.
Novell suggests the following:
With the current market situation, the smallest drive available is 2G in size. Having such
a drive, 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.
Binding multiple frame types in NT Workstation 4.0 and Novell
Client 32
Depending on your network configuration, you may be running more than one type of IPX
frame type. Microsoft NT Workstation 4.0 only allows you to
specify 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
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NWlnkIpx\NetConfig\<NIC/Adapter
Driver> : PktType
PktType is a multiple string value (REGEDIT32), which means 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.
NT Server doesn't restrict you to a single frame type like NT Workstation.
Having problems with NETADMIN?
Do you have a large NDS tree? And 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 over 1250 objects, reduce it. Novell recommends never going
over1250 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 choices to fix the problem:
1) Don't use the DOS NETADMIN to manage your NDS tree, use the Windows versions instead.
WIndows 95 and Windows NT handle program buffers much better than DOS.
2) Reduce the number of objects in the NDS container where the problem occurs.
Why is the Intranetware client for NT so slow?
Have you noticed that opening files from a Novell file server using the Novell
IntraNetWare client takes a long time? It's not your imagination. It does.
Slow file access doesn't happen if you use Microsoft's client for Novell instead of Novell
IntraNetWare client. Here's why.
Microsoft added the MultinetGetConnectionPerformance API to Windows 95 and Windows NT
version 4.0 to speed file access on a network. Microsoft's
Novell Client supports the API call, Novell's doesn't. Without this call, things slow down
appreciably. Until Novell fixes the Intranetware Client for NT, if you want performance,
go with Microsoft's client if possible.
Viruses and Client32 for Windows 95
If you're worried about viruses on your network and use Network Associates's VirusScan95
with Novell's Client 32 for Windows 95, you have a right to be. You may not be getting the
virus protection you think you are.
VirusScan95 can scan and find viruses on both local and network drives when explicitly
told to do so. But if you use VShield to automatically scan
files when you start programs, you may have a problem.
VirusScan95 can detect viruses on startup when the files load from a local drive. But if
you start a program from a network drive, Vshield won't notice the launch and lets the
program start without being scanned.
This problem may also occur when you copy files from one network drive to another. If you
copy a file from the network drive either to or from a network drive, you're ok.
For now, Network Associates is working to make the program work with Novell's Client32.
You should make sure you do periodic scans on your network drives rather than depending on
VShield. You also may want to install NetScan on your server.
Help!
I lost my tree.
If you're using a Win9x workstation and the tree and context are missing from
the default location profile, it's probably because you're logging into an NT
domain first. Designating the Novell NetWare client as the Primary Network Logon
will prevent this from happening.
Where
do NDPS print jobs spool?
When you send an NDPS print job, it is spooled 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, choose the Printer Agent for the printer you're interested in, choose
Information and you'll see an entry for Job Spool Location toward the bottom of
the screen.
ZENWorks
Workstation Manager DLLs
For ZENWorks to function properly on a Window 95 or Windows NT computer, several
DLL files must be present on the client computer. These files are transferred to
the computer during the ZENWorks client software installation. Each DLL relates
to a specific ZENWorks 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.
[return to Top]
Deleting
index files with CD PURGE
If you frequently mount different CDs as volumes on your NetWare server, you
need to be aware that for each CD you mount, NetWare creates an index file. The
index files are stored in a hidden
directory on the SYS: volume called Cdrom$$.rom. When you dismount the CD,
NetWare doesn't automatically delete the index files, and they can soon
accumulate taking up valuable space. An easy way of deleting these files is to
run the CD PURGE command at the server console. However, make sure that there
are no mounted CD volumes when you do this, or the command won't run.
Legal Disclaimer
THE INFORMATION IN THIS PUBLICATION IS
PROVIDED "AS IS". WE EXPRESSLY DISCLAIMS ALL REPRESENTATIONS AND WARRANTIES OF
ANY KIND REGARDING THE CONTENTS OR USE OF THE INFORMATION INCLUDING, BUT NOT LIMITED TO,
EXPRESS AND IMPLIED WARRANTIES OF ACCURACY, COMPLETENESS, MERCHANTABILITY, FITNESS FOR A
PARTICULAR USE, OR NON-INFRINGEMENT. IN NO EVENT SHALL WE BE LIABLE FOR ANY DIRECT,
INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, LOST
BUSINESS OR LOST DATA, RESULTING FROM THE USE OR RELIANCE UPON THE INFORMATION, EVEN IF WE
HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME JURISDICTIONS DO NOT ALLOW THE
EXCLUSION OF IMPLIED WARRANTIES, SO THE ABOVE EXCLUSION MAY NOT APPLY TO YOU.