 |
» |
|
|
|
This section lists common problems that may occur without
producing an error number. For information on numbered errors, see
"Error Messages," later in this chapter. Problems Starting NetWare Connectivity | |
"Invalid drive specification" appears when I try
to start NetWare Connectivity. Be sure the lastdrive
entry in the CONFIG.SYS file is not set to z.
The lastdrive entry should be set to a letter
near the middle of the alphabet, such as p. If you change the lastdrive entry,
reboot the workstation so the change can take effect. If lastdrive is not z,
and if you are using the nwload command to
start NetWare Connectivity, edit NWLOAD.BAT. Halfway down NWLOAD.BAT
you'll find a line that logs the user in to the NetWare
server; for example: where q is the drive letter used for the login. This drive
letter must be the letter following the drive letter specified as
the lastdrive entry in the CONFIG.SYS file. For example, if lastdrive is p,
use q in the login
line of NWLOAD.BAT; if lastdrive is f,
use g in the login
line, and so forth.
"Bad command or file name" appears when I run NWLOAD.BAT
or NETX.COM, NETxCOM, or NETX.EXE. Check your LANMAN.DOS\NETPROG
directory (if your workstation is running LAN Manager Enhanced)
or your LANMAN.DOS\BASIC directory (if your workstation
is running LAN Manager Basic) to be sure that it contains
either the NETX.COM or NETX.EXE files or one of the NET3.COM, NET4.COM,
or NET5.COM files, whichever is appropriate for your version of
MS-DOS. If you don't find this file, copy it from your
NetWare distribution disks. If you use the nwload command
to start NetWare and the workstation uses the NETX.COM or NETX.EXE
files instead of the NET3.COM, NET4.COM, or NET5.COM files, be sure
you have modified NWLOAD.BAT to use NETX.COM or NETX.EXE. This modification
involves removing rem from the following two lines, making these
lines commands instead of comments: If this is the problem, you should also check the NWUNLOAD.BAT
file. You must remove rem from the following two lines in NWUNLOAD.BAT: rem netx /u
rem goto IPXREL |
When I try to start NetWare, a message appears
saying that ROUTE or ROUTE.COM cannot be loaded. The file ROUTE.COM, required for NetWare
source routing on token-ring networks, did not get installed on
the workstation. Copy this file to the LANMAN.DOS\NETPROG
directory if the workstation is running LAN Manager Enhanced,
or the LANMAN.DOS\BASIC directory if the workstation is
running LAN Manager Basic. You can get this file from Novell. If your network is not token-ring, then the PROTOCOL.INI
file is incorrectly trying to load ROUTE.COM. To correct this, modify
the PROTOCOL.INI file so that it does not load ROUTE.COM. You should
also modify the PROTOCOL.INI file in the LANMAN.DOS\DRIVERS\PROTOCOL\IPX
directory in the same way so that the problem does not recur when
you change configurations. If this problem happens on many workstations and your network
is not token-ring, check the disk you use for installation. It may
have the PROTOCOL.INI file meant for token-ring networks. For more
information, see Chapter 2, "Installing and Configuring
NetWare Connectivity."
"A File Server could not be found" appears when
I try to start NetWare Connectivity. Check the computer's physical
connection to the network. Check that the network cable is correctly
attached to the workstation. Check that a NetWare file server is running.
Problems Using NetWare Connectivity | |
While in the Microsoft Windows File Manager, "Can't
connect to net drive" appears when I try to connect to a Windows
NT or LAN Manager directory. You are trying to connect a drive
letter that comes after the drive specified as the lastdrive
to a Windows NT or LAN Manager directory. With
NetWare Connectivity, you can assign only drive letters up to and
including lastdrive to Windows NT
or LAN Manager directories. Use a drive letter that occurs
earlier in the alphabet. The lastdrive is set in the CONFIG.SYS
file.
The workstation has a local drive letter assigned
to a Windows NT or LAN Manager directory, but when I use that drive
letter it refers to a NetWare directory instead. The drive letter has been assigned
to a Windows NT or LAN Manager directory and a
NetWare directory simultaneously. End one of those connections,
and then reconnect using a drive letter that is not being used. To prevent problems, do not assign the same drive letter both
to a Windows NT or LAN Manager directory and to
a NetWare directory. When connecting to Windows NT or LAN Manager
directories, use only drive letters up to and including the letter
specified in the lastdrive entry in the CONFIG.SYS
file (the default is p). For connecting to
NetWare directories, use letters that come after the lastdrive
letter.
The workstation is connected to a Windows NT or
LAN Manager directory, but I can't find any files or subdirectories
in that directory. Check the local drive letter assigned
to that directory to see if it is also assigned to a NetWare directory.
To check, type: If the drive letter has been assigned twice, end the connection
to one of the directories, and then reconnect to that directory
using a different drive letter. To prevent problems, do not assign the same drive letter both
to a Windows NT or LAN Manager directory and a
NetWare directory. When connecting to Windows NT or LAN Manager
directories, use only drive letters up to and including the letter
specified in the lastdrive entry in the CONFIG.SYS
file (the default is p) for LAN Manager
directories, When connecting to NetWare directories, use letters
that come after the lastdrive letter. This problem can also occur if the server in question
is running user-level security and the user does not have R permission
to the directory. (This problem is not related to NetWare Connectivity.) For more information about user-level security and directory
permissions, see the LAN Manager administrative documentation.
Cannot Find LAN Manager DLL Error Message If you see the following message when starting the Microsoft Windows
operating system, your workstation has a search path problem: Cannot find LAN Manager DLL:
NETAPI.DLL (Enhanced) or MSNET.DRV (Basic).
Check the PATH to ensure that it is correct. |
The problem is that NetWare changed your search path when
you logged on to a NetWare server, and your LANMAN\NETPROG
directory was deleted from the search path. To correct the problem do one of the following: If you use nwload
to start NetWare, check NWLOAD.BAT to ensure that the command to
start the fixpath utility is near the bottom
of the file and that the command to start this utility specifies
the correct location of FIXPATH.EXE. If you don't use nwload
to start NetWare, you can run fixpath yourself
after you start NetWare. To run fixpath,
type its full path. For example, you might type: c:\lanman\netprog\fixpath |
For more information about using fixpath,
see "Using the Fixpath Utility," earlier in this
document.
After installing NetWare Connectivity on a workstation
with the Microsoft Windows operating system, the workstation may
hang or crash when you start an MS-DOS box from within the Windows
operating system. (This problem also occurs on NetWare-only workstations.) You
can solve the problem in one of two ways. Edit the [netware] section of the
SYSTEM.INI file in your WINDOWS directory. In this file, set nwsharehandles
to true. The NetWare Connectivity Setup program
sets nwsharehandles to true
by default, so unless you change your SYSTEM.INI file you should
never have the problem of MS-DOS boxes that hang or crash. If you want nwsharehandles
to be false, you can solve the hanging problem
by creating a .PIF file for your MS-DOS boxes, so that the MS-DOS
boxes start in background mode.
To create a .PIF file for your MS-DOS boxes Start the Windows operating system. In the Accessories program group, choose PIF Editor. Complete the PIF Editor dialog box: In the Program Filename box, type
the path to the COMMAND.COM file, such as: - Or - In the Window Title box, type: u In the Start-up Directory box, type: Near the bottom of the dialog box, select the Background
box.
From the File menu of the PIF Editor dialog box,
choose Save. In the Filename box in the Save As dialog box, type
msdosbox.pif
and then choose the OK button. From the File menu, choose Exit to close the PIF
Editor dialog box. Go to the program group from which you currently
launch MS-DOS boxes, and select the MS-DOS box program item. From the Program Manager File menu, choose Properties. Complete the Program Item Properties dialog box: In the Description box, type: In the Command Line box, type:
Choose the OK button. The MS-DOS box program item will now launch MS-DOS boxes in
background mode.
The Net Stop Workstation command does not work. You cannot stop the Workstation service while NetWare is loaded
with the nwload command. When you stop the Workstation service using the net
stop workstation command, LAN Manager performs
the following actions, in this order: Logs you off from the network. Unloads each currently loaded protocol. The protocols
are unloaded in the re verse order of their loading (the last one
loaded is the first one unloaded). Stops the Workstation service. If the unloading of any protocol in step 2 is not successful,
the process stops at that point. In this case, any remaining protocols
are left loaded, and the Workstation service does not stop. With NetWare Connectivity, one of the protocols is IPX. IPX
cannot be unloaded if the NetWare shell (NETx.COM) is running, so
if you type net stop workstation
with the NetWare shell running, the command will fail. For example, if you use the following series of commands,
the net stop workstation command fails because
it cannot unload IPX (because the NetWare shell is running): net start workstation
load netbeui
nwload
net stop workstation |
The following series of commands will work, however: net start workstation
load netbeui
nwload
nwunload
net stop workstation |
If you don't want net stop workstation
to automatically unload IPX and stop NetWare, you can bypass the
load ipx command (which is in the NWLOAD.BAT
file), and load IPX by using the following commands (instead of
load ipx): Then, when you want to unload IPX, use the following command
(instead of unload ipx): If you use these commands, net stop workstation
will not try to unload IPX, because IPX was not loaded with the
load ipx command.
The workstation has a printer devicename assigned
to a printer on a NetWare server, but the print jobs I send do not
print on that printer. Check the printer devicename to see
if it is also assigned to a printer on a LAN Manager server.
To check, type: If you also need to check your connections to NetWare printers,
type: If you find that the devicename is assigned to both a NetWare
printer and a LAN Manager printer, end one of those connections,
and then reconnect to that printer using a different devicename.
"DOS Error 15 has occurred. SYS0015: The system
cannot find the drive specified." appears when I try to connect
to a LAN Manager directory. You are trying to assign a drive letter
above the letter set as lastdrive to the directory. When connecting
to LAN Manager directories, you can assign only drive letters
up to and including the lastdrive letter.
|
Printable version
