Sie sind auf Seite 1von 6

LEXMARK SCAN TO NETWORK Readme for version 3.5.0 1.

OVERVIEW This Readme file pertains to the current release of the LEXMARK SCAN TO NETWORK application. Lexmark Scan to Network is an embedded solution that can be installed on printers that support the Lexmark Embedded Solutions Framework (eSF) v2.x or v3.x. Scan to Network enables users to scan documents to a network, with network destinations chosen by the administrator. Scan to Network: * Eliminates time spent transferring scanned files from a PC to a network drive. * Reduces the steps used to store scanned documents on a file share. * Simplifies the process of archiving scanned files. * Enables a destination to be configured to determine the actual network location via an LDAP lookup. Note: This unlicensed version of Scan to Network is fully functional and includes basic scan settings. A premium version of Scan to Network is available in the Lexmark Virtual Solution Center. Scan to Network Premium offers advanced features such as custom prompt creation and bar code scanning. Scan to Network Premium requires a license. To obtain a license, go to www.lexmark.com and click the "Contact Lexmark" link at the bottom of the screen. 2. ASSOCIATED FILES The following files and publications are included in the release. a. Application Files * scanToNet-fw2-3.5.0.fls * The Scan to Network application for eSF v2.x printers * scanToNet-fw3-3.5.0.fls * The Scan to Network application for eSF v3.x printers b. Other Files * scanToNet-fw2_3.5.0_desc.xml * The solution descriptor file * LicenseServer.exe * The network license manager c. Publications

* Lexmark_ScanToNetwork_AdminGuide.pdf * The Administrator's Guide * Lexmark_ScanToNetwork_UserGuide.pdf * The User's Guide * Readme.txt * (this file) 3. REQUIREMENTS a. A printer that supports eSF v2.x or v3.x applications. Supported eSF v2.x printers include: * X65x * Required firmware level: LR.MN.P510b or later. * X73x * Required firmware level: LR.FL.P510b or later. * X46x * Required firmware level: LR.BS.P510b or later. * X86x * Required firmware level: LP.SP.P510b or later. Supported eSF v3.x printers include: * X54x * Required firmware level: LHS1.VK.P141kX or later. * X74x * Required firmware level: LHSC.NY.P260e or later. * X79x * Required firmware level: LHS1.MR.P135r or later. * X92x * Required firmware level: LHS1.HK.P136m or later. * X95x * Required firmware level: LHS1.TQ.P145hea or later. * 6500e * Required firmware level: LJR.JR.P169 or later. b. Memory: The printer must have a minimum of 256MB RAM. c. Protocols Scan to Network uses the following protocols. * Note: Other protocols may also be supported.

* Common Internet File System (CIFS): A dialect of the Server Message Block (SMB) protocol. Destinations that use Windows Shares employ this protocol. * File Transfer Protocol (FTP): Destinations that use FTP Shares employ this protocol. * Lightweight Directory Access Protocol (LDAP): The application and printer use this protocol when authenticating using Directory Services such as Microsoft Active Directory. d. Ports Scan to Network uses the following ports. * * * * * * 137 138 139 445 9100 9400

4. LIMITATIONS AND COMPATIBILITY OF THE RELEASE a. MAXIMUM NUMBER OF IMPORTED DESTINATIONS WITH MARKVISION PROFESSIONAL This release Of Scan to Network supports importing a maximum of 25 destinations (without custom images) through MarkVision Professional (MVP). If custom images are used, less than 25 destinations can be imported through MVP. In addition, even if 25 destinations are imported successfully, MVP may display a "Failed to import Scan to Network Folder config. file" message. b. SAVED FILE BEHAVIOR WHEN SCAN IS CANCELLED A scan job can be cancelled in one of two ways: during the scan or after the scan is complete but the job has not been accepted. For each of these scenarios, the application may behave differently for "multipage" file formats (PDF, XPS, and multi-page TIFF) than for "singlepage" formats (JPEG and single-page TIFF). If preview is disabled and the job is cancelled after the scan is complete (i.e. when the "Scan the Next Page" or "Finish the Job" screen is displayed), the application will start writing the images as it starts receiving data from the scanner. This occurs immediately after "Scan It" is clicked. Therefore, the files will be saved on the network share, regardless of their format. Whether or not these files can be opened or used depends on the file type. JPEG files can be opened, but PDF, single-page TIFF, multi-page TIFF, and XPS files cannot be opened. c. CONFIGURATION FILE COMPATIBILITY Configuration files from this release are not compatible with those of earlier versions of Scan to Network. However, exported configuration files from Scan to Network v2.0.7 and higher can be imported into this version.

d. SUPPORTED OPERATING SYSTEMS FOR DESTINATIONS * Note: All Microsoft Windows operating systems listed below are 32 bit unless otherwise noted. Share drive * Windows * Windows * Windows * Windows * Windows * Windows * Windows * Windows * Windows * Windows * Windows FTP * * * * * * * * * * * * * * 7 Ultimate and Ultimate 64 bit 7 Home Basic Vista Ultimate Server Professional 2008 Server 2008 64 Bit Server 2003 Standard Edition SP1 Server 2003 Standard Edition R2 XP Professional SP2 XP Home 2000 Professional SP4 2000 SP4

Windows 7 Ultimate and Ultimate 64 bit Windows 7 Home Basic Windows Vista Ultimate Windows Server Professional 2008 Windows Server 2008 64 Bit Windows Server 2003 Standard Edition SP1 Windows Server 2003 Standard Edition R2 Windows XP Professional SP2 Windows XP Home Windows 2000 Professional SP4 Windows 2000 SP4 Redhat Linux Enterprise Edition Sun Solaris 10 Novell OES Linux SuSE 9

The following Microsoft Windows Server 2003 configurations are supported. * Standalone Distributed File System (DFS) * Domain-based DFS * Domain-based DFS with one child domain used for authentication e. CONNECTION DROPPED BEFORE SCAN DATA IS SENT The amount of time before the application begins to send the scan data to an FTP server may exceed the amount of time the server will keep an idle connection open. This results in the connection being dropped before the scan data is sent. The application shows an "application error has occurred" message. When the user selects the "OK" button, a "Scan Failed" confirmation screen appears along with another "application error has occurred" message that has three options: "Yes, to same destination," "Yes, to a different destination," and "No." If the user selects "No," the application returns to the home screen. This issue can be resolved by having the network (FTP server) administrator increase the idle session timeout for the FTP passive mode. f. NETWORK SAVE FAILS IF FILE IS ALREADY IN USE

If the file to which the scan data is being written is already in use by another application or user, the network save operation will fail. The application shows a "The scan cannot be completed using this filename. The file is currently being used by another program" message. When the user selects the "OK" button, a "Scan Failed" confirmation screen appears along with another "The scan cannot be completed using this filename. The file is currently being used by another program" message that has three options: "Yes, to same destination," "Yes, to a different destination," and "No." If the user selects "No," the application returns to the home screen. g. "START IN USER DIRECTORY" BEHAVIOR If the administrator selects the "Start in user directory" option, the application will attempt to store the scanned file in a subdirectory with the same name as the user ID. Some file systems may automatically place the user in the "user" directory, so the application may create yet another subdirectory named for the user. If this behavior is noted and is not desirable, turn off the "Start in user directory" option. h. "START IN USER DIRECTORY" BEHAVIOR WITH LDAP PATH ATTRIBUTE SET On a Windows FTP server, if the value returned by the LDAP server for the path attribute is the same as the username, an issue similar to the one documented in 5.g above occurs. The user is automatically placed in the "username" directory (see above), and the application's attempts to connect to the FTP server will fail because it will not be able to find the "username" directory. i. SAVED FILES WITH LONG CUSTOM FILENAMES CANNOT BE OPENED If the length of a custom filename is between 241 and 255 characters, the scanned image will be saved successfully in the destination, but it cannot be opened or previewed. This issue occurs only on Windows machines. If the filename exceeds the limit of 255 characters, an error message and a "Scan Failed" confirmation are displayed. j. START BUTTON DOES NOT INITIATE SCANNING On eSF v3.x printers, the scan does not start when the printer Start button is pressed from the destination Summary screen. k. SCAN EDGE TO EDGE AND EDGE ERASE CAN BE USED SIMULTANEOUSLY On eSF v3.x printers, the "Scan Edge to Edge" and "Edge Erase" settings can be used simultaneously even though they are incompatible with one another. l. PDF FILES WITH NON-ENGLISH CHARACTERS IN FILENAME CANNOT BE OPENED If a destination uses a string prompt to ask users to enter a PDF image filename and a user enters Greek, Hungarian, Czech, or Russian characters in the filename prompt, the PDF file cannot be opened in Adobe Reader 7.x. The file can be opened in Adobe Reader 8.x.

m. USING FULLY-QUALIFIED HOSTNAMES WHEN CONNECTING TO DESTINATIONS When the printer's DNS server address is different from the destination server's DNS server address and/or the printer is in a domain/workgroup while the destination server is in a workgroup, the application may fail to connect to the destination server using only the hostname. If the destination server is in a domain, providing the fully-qualified hostname followed by the share name may facilitate a successful connection with the destination. For example, if "myhost.domain.com" is the fully-qualified server name and "myshare" is a shared folder, if "\\myhost.domain.com\myshare" is entered in the "Address" field, Scan to Network should be able to connect to the destination successfully. n. SECURE PDF FILE FORMAT + PDF/A VERSION NOT SUPPORTED The application does not support combining the Secure PDF file format with the PDF/A version. If the file format is set to Secure PDF and the version is set to PDF/A, PDF 1.2, or PDF 1.3, the printer will ignore the Secure PDF file format. The document will be scanned as a regular PDF. On eSF v2.x printers, this occurs automatically. On eSF v3.x printers, the user will be informed of the compatibility issue before the scan starts and will be prompted to continue or cancel the scan. o. PDF DOCUMENT PROPERTIES WINDOW ISSUES A scanned PDF file accessed from a destination may have garbage characters in its Document Properties window or the Document Properties window may not open. This is due to the PDF file format and PDF version compatibility issues described above. For further installation and configuration instructions, please see the Lexmark Scan to Network and Scan to Network Premium Administrator's Guide provided with the application. Adobe Acrobat Reader is required to view this guide.