![[Intel Navigation Header]](/CONTENT/PIX/HEADER.GIF)
LANDesk(R) Manager: Troubleshooting Notes from Tech Support
Contents:
LANDESK(R) MANAGER V1.5X OVERVIEW
LANDesk(R) Manager has over a dozen separate tools. Most customers focus
on:
* Inventory Manager
Desktop Access (which also accesses Chat and File Transfer)
Traffic Monitor
Application Monitor
Server Monitor (on NetWare* v3.11 and NetWare v3.12 file servers)
Network Printer Manager
Desktop Remote
GENERAL NETWARE* ENVIRONMENT
LANDesk(R) Manager is Novell-certified for NetWare* v3.11 and NetWare
v3.12. LANDesk Manager v1.51 officially supports NetWare v4.01 (bindery
emulation) with the exception of Server Monitor--its 2 NLMs only
function with NetWare v3.11 and NetWare v3.12 file servers. All 5 NLMs
take less than 200 KB file server memory.
Note: USER.NLM loads with 3 outdated APIs but functions perfectly
with NetWare v4.x. SFTIII NetWare is not officially supported, but many
customers successfully use everything except CONTROL, MONIT386, and USER
NLMs, which detect the SFTIII environment and refuse to load,
sacrificing only Server Monitor and the file server control in Desktop
Access. For details, refer to document 5540 for Desktop Access, 5536
for Server Monitor, and 5539 for installation tips (NetWare v4.x, etc).
NetWare v4.1 is not yet officially supported. DO NOT load the LANDesk
Manager v1.51 or earlier Inventory Manager NLMs (LDINV or LDISCAN) on a
NetWare v4.1 file server.
WIDE-AREA NETWORK ENVIRONMENT
Some WAN routers are set to filter SAP packets that certain LANDesk(R)
Manager tools need to function properly. Inventory Manager and Software
Probe require routers to pass object type 0x102 (OT_INTEL), and Server
Monitor needs 0x001BF. Desktop Access doesn't SAP--it lists servers
populated by 0x0004 (Novell's OT_FILE_SERVER).
INVENTORY MANAGER: CANNOT SEE ANY RECORDS IN THE INVENTORY DATABASE
If the main Inventory Manager screen is empty after running LDISCAN.EXE
/s=SERVERNAME (the server specified under Configure|Inventory Server),
then copy WBTRCALL.DLL and WBTRVRES.DLL from the SYS:PUBLIC directory to
the administrator's LANDESK(R) directory (SYS:LANDESK is the default).
See document 5534 for more information on Btrieve*, etc.
INVENTORY MANAGER: MACHINES.DAT AND OTHER BTRIEVE* ERRORS
Most Btrieve* errors are version or memory related. Make sure
BREQUEST.EXE loads at the administrator workstation. Rebuilding the
Inventory database after installing the proper Btrieve files fixes
MACHINES.DAT errors 1-100. Unloading programs in Windows* or freeing up
at least 500 KB for the largest executable program size in DOS addresses
errors 1002 and 2001. See document 5534 for more information.
We recommend Btrieve v6.1, although original NetWare* v3.11 file servers
have no problem with Btrieve v5.15. LANDesk(R) Manager ships with the
latest Btrieve v6.1 from Novell--it is in the self-extracting ZIP file
BTR61.EXE on the Desktop Remote diskette.
DESKTOP ACCESS: CREATE DEFAULT SECURITY TEMPLATE
Desktop Access, Chat, and File Transfer require that default security
settings exist in the file server bindery. Even if you don't make any
security changes, follow these steps the first time you run Desktop
Access.
1. Enter Desktop Access from the LANDesk(R) Control Panel.
2. Choose Tools|Control Options|Server Default Security.
3. Choose OK (regardless of whether you change any settings or
not).
The NetWare* v4.0x bindery context contains the serialization
information. See document 5539 for more information.
DESKTOP ACCESS: WUSER.EXE WILL NOT LOAD
The most common issue here is that USER.COM has not been loaded in DOS
before entering Windows*. Running the DOS command MEM /C will show if
USER.COM is in memory. Additional possibilities are listed in document
5540.
DESKTOP ACCESS: CONTROLLING STATIONS
Screen, keyboard, and mouse control often depend on the issues listed
below. See document 5540 for more information.
* Use the IPXODI supplied with LANDesk(R) Manager.
* Use EMM386.EXE to manage workstation memory. If you use Net
Satisfaxtion TSRs, load FAXNODE.EXE, then USER.COM, then
FAXPOP.EXE.
* Load the mouse driver before loading USER, LANSEL, and Windows* on
both the LANDesk Manager workstation and the target station.
* Make sure WUSER.EXE is in the Startup group in Windows v3.1. Also,
make sure WLANSEL.EXE is not found in the RUN= line of the WIN.INI
or in the Startup group (possibly from LANDesk Manager v1.0x).
* Set keyboard stuffing to interrupt-driven; if results are not
perfect, try BIOS. If viewing an EGA or VGA screen, choose
Configure... from the upper left horizontal bar and activate
Accelerated Mode. Make sure both stations have a mouse connected to
them.
* Ensure that VUSER.386 is loaded in the SYSTEM.INI file on both
stations and that MOUSE.DRV is in the Windows SYSTEM directory (we
use Windows' MOUSE.DRV, not IMOUSE.DRV or ILMOUSE.DRV).
DESKTOP ACCESS: CANNOT CONTROL WINDOWS* FOR WORKGROUPS TARGETS
Windows* for Workgroups must not use the IPX/SPX compatible transport
(with or without NetBIOS) in the Network Setup because this transport
uses NWLINK.DLL. Microsoft has recommended that we avoid using the
NWLINK driver. Instead, use Microsoft NetBEUI for your workgroup
connectivity.
SERVER MONITOR: SSTABLISHING AND MAINTAINING NOS CONNECTION
NetWare* sometimes fails to accurately report if the Server Monitor NLMs
are loaded. We modified our executables to bypass NetWare and maintain
connection in such cases. Download SMON.EXE from Intel's online services
(LANDesk(R) Manager current area). Use EMM386.EXE to manage memory on
the Server Monitor workstation.
If you use a Compaq NetFlex NIC in your file server, make sure you have
the latest version from Compaq's LAN Driver section on CompuServe (v2.10
or later) AND that you are using all of the new NLMs supplied by Compaq
with the new driver (especially MONITOR.NLM). Our NLMs will not load
after CPQ*.LAN v1.0 and may not work properly with v1.1. Load
MONIT386.NLM before the Compaq NetFlex LAN driver loads.
See document 5536 for more information.
PROBLEMS WITH LOGIN.COM OR PUSHPOP.EXE
LOGIN.COM simply allows terminate-and-stay-resident (TSR) programs to
load from the system or user login scripts. Intel supplies it in an
effort to allow the USER and LANSEL TSRs to load during the login
process.
If these TSRs load from a batch file that is invoked from a login script
via the "EXIT" command or in a batch file after logging into the
network, LOGIN.COM is not necessary. Rename (or delete) LOGIN.COM in
both the SYS:LOGIN and SYS:PUBLIC directories. In the system login
script, REMark out (or delete) the lines for OK4TSRS.EXE or LOADTSR.EXE,
USER.COM, LANSEL.EXE, warning messages, and the pause used if LOGIN.COM
is gone.
PUSHPOP.EXE is new to LANDesk(R) Manager v1.51 in order to support
NetWare* v4.01's drive letter requirement for executing programs in a
login script. NetWare v3.11 and NetWare v3.12 do not need PUSHPOP.EXE;
select any drive mapped to the same volume as the shared LANDESK
directory to run LDISCAN.EXE, WKSTACFG.EXE, and the Desktop Access TSRs.
See document 5539 for more information on LOGIN.COM and PUSHPOP.EXE.
Trademark information