User manual LAPLINK REMOTE NETWORK ACCELERATOR

[. . . ] Copyright notice No part of this publication may be reproduced, transmitted, stored in a retrieval system, or translated into any human or computer language, in any form or by any means, without the express written permission of LapLink, Inc. , 18912 North Creek Parkway, Bothell, Washington, 98011, U. S. A. Trademarks LapLink, the LapLink logo, and SpeedSync are trademarks or registered trademarks of LapLink, Inc. Other brand and product names are trademarks or registered trademarks of their respective holders. Patents SpeedSync® U. S. Patent Number 5, 446, 888 LapLink® Remote Network Accelerator © 1998-2002 LapLink, Inc. All rights reserved 18912 North Creek Parkway Bothell, WA 98011 U. S. A. LapLink® Remote Network Accelerators Administrator's Guide © 1998-2002 LapLink, Inc. 1 Contents What is LapLink Remote Network Accelerator (RNA)? [. . . ] LapLink RNA accumulates the changes in the cache until either the program requests them or the file is closed. Write-behind caching improves response time because the application does not have to wait while changes are written to the network drive. The speed increase depends on many factors, including the programs running on the client computer, the type of file, hardware and software configurations, and how busy the system is. Turning off write-behind caching can dramatically slow remote network performance. Using write-behind caching only slightly increases the risk of data loss. Because changes are sent to the network less frequently, if the client is disconnected from the network while file handles are open, information could be lost. However, there is always a greater risk of data loss over remote connections. !TIP 19 Administering client settings Recommending cache size LapLink RNA monitors the cache on disks as large as 4 GB. If the disk where the cache is stored is greater than 4 GB, LapLink RNA only recognizes 4 GB of the disk space. Suggest that client users allow a large amount of disk space for the cache. A greater allowed space means that LapLink RNA can cache more data, which can greatly improve performance. Because LapLink RNA caches files in a database, it always accesses cached data quickly, regardless of the cache size. Recommending logging options The client computer's log is a good source to help you troubleshoot problems with the client service. Therefore you should be sure that users keep a log of acceleration activity. The client logging options in Windows NT, Windows 2000 or Windows XP are the same as those for LapLink RNA Server. For information about the LapLink RNA logging options in Windows NT, Windows 2000 or Windows XP see the LapLink RNA Installation and Quick Start Guide. 20 4 Troubleshooting In This Chapter: Introduction to troubleshooting Troubleshooting LapLink RNA Server Troubleshooting LapLink RNA clients 22 22 25 Introduction to troubleshooting Introduction to troubleshooting This chapter provides suggestions for solving problems and improving performance. These suggestions are designed as a quick overview of possible solutions, with enough information to guide experienced users to solutions. For detailed, step-by-step information, consult the troubleshooters in LapLink RNA Help. The troubleshooters are designed to solve problems you can encounter configuring, monitoring, and connecting LapLink RNA services. To use a troubleshooter, open a troubleshooting book in Help Topics and display one of the topics. Then answer the questions about your problem and try the suggested remedies. In some cases you will find shortcut buttons to dialog boxes; use these buttons to resolve the problem faster. Troubleshooting LapLink RNA Server General concerns Description text reads: Communications error <number> occurred. Go to Troubleshooting in Help. This description appears when an RPC error occurs. Make a note of the error number in case you need to contact your support representative. [. . . ] If the error remains, reinstall LapLink RNA. Error initializing LapLink RNA RPC interface. The LapLink RNA service could not communicate with the user interface (the properties dialog box or the LapLink RNA Service Manager). This can occur if another program causes a serious error on the computer. If the error remains, reinstall LapLink RNA. Error loading module <module name>. One or more of the dynamic link libraries LapLink RNA uses to accelerate remote network access is unavailable. This can occur if another program causes a serious error on the computer. [. . . ]