Product:	ARCserve 5.0, 5.0a, 5.01
Module:		CLIENTS.NLM
Date:		12/29/94


This file contains updates to CLIENTS.NLM for customers experiencing 
symptoms described below.

Installation of this new CLIENTS.NLM:
This file can be copied over the current CLIENTS.NLM located in the 
ARCSERVE\NLM Directory.

Explanation of How the Client Tracker works:
The clients tracker first finds all known network addresses by broadcasting 
IPX diagnostic packets. Then for each network address, the clients tracker 
finds all workstations on that network. Finally, for each workstation, the 
clients tracker sends number of ipx diagnostic packets to the workstation to 
find the following detail information:
1. OS description and version 
2. Hardware type
3. Shell, Ipx and Spx version
4. Lan card type and Hardware settings on Lan card 
5. Symbolic Login Name

"W=N" Parameter
This option will disable Clients.nlm from retrieving the workstation specific 
information and avoid sending the ipx diagnostic packet to the workstation. 
Only thing that clients tracker or ARCserve misses is the workstation specific 
information which is not necessary to backup a workstation. This option will 
also reduce the network traffic significantly on large network environment.  

Symptom:  CLIENTS.NLM auto un-loading during the ASTART process.
Solution:           
This problem was primarily due to more than four LAN cards in the Server.  With 
NetWare, each network segment requires 1 buffer, and our buffer was only 64 
bytes.  If you had more than 5 cards, the buffer was too small.  The buffer now 
supports up to 8 LAN cards in a single Server.

Symptom:  The ARCserve Activity log reports: Error 4109- Failed to Receive 
Packet . . .
Solution:           
CLIENTS.NLM was only reporting an error which did not effect the backup process.
This error condition is no longer reported.

Symptom:  When running NetWare 4.x, the Server may Abend with Page Fault 
Process Exception.
Solution:           
CLIENTS.NLM performs calculations in which a time period for workstation 
response is expected.  With Servers running NetWare 4.x, the time had to be 
increased.

Symptom:  CLIENTS.NLM could periodically freeze workstations when heavy traffic 
on the Network was experienced.
Solution:           
When CLIENTS.NLM sent out a broadcast requesting workstation response, it would 
continue to broadcast until a request was answered, therefore bogging down the 
Network.  CLIENTS.NLM now only sends out two requests.

                                                                                                                                                                                               C                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     /  1  X        <  \  n            r  t          T  j      "	  8	  	  	  T
  j
  A  C                                                                                                                                                                                                                                                                                               !     !     !     !  %       F        	
              	       	         C     C   (  Times New Roman 	Symbol & Arial    m  m     m      m  "       h    Pkgkgk #   g  	       a   "Readme file for Clients.NLM Update   Cheyenne Software Inc.Cheyenne Software Inc.         