Processes Blocked by Firewall Applications Prevent Scanning Functions |
Document ID:SO6916 |
| Properties |
Microsoft Windows NT, Terminal Server; Microsoft Windows 2000 Advanced Server; Windows XP (32-bit); Windows XP Professional (64-bit); Windows Vista (32-bit); Windows Vista (64-bit); Windows 7 (32-bit); Windows 7 (64-bit); Windows 8 (32-bit); Windows 8 (64-bit); Microsoft Windows Server 2003; Microsoft Windows Server 2008;
Multiple symptoms may indicate a firewall is preventing communication.
Before you continue
You should eliminate other communication issues as a possible root cause for the symptoms described above.
First, if one function is failing you should always try another printer/scanner function to test communication.
For example,
| If... | Then... |
| You cannot print, but you are able to scan... |
Proceed to Suggested Remedy. It is important to understand that other print queue-related issues are possible. |
| You cannot scan, but you are able to print... | Proceed to Suggested Remedy. |
| You cannot scan or print... | You should see Additional Actions to further validate printer-to-pc communication before proceeding to Suggested Remedy. |
Additional Actions
| Action... | Purpose... |
| 1. Identify status "Connected" on the network setup (settings) page? To do this from the control panel:
|
A status of "Connected" indicates the printer is communicating on a network; however, it does not necessarily prove that it is communicating on your network. |
| 2. Access the printer's web page. To do this:
|
This guarantees that your printer is communicating with your PC. |
It is possible that a scan function is not working because the process utilized by one of the printer functions is blocked.
Step 1: Identify you firewall application.
Step 2: Identify any blocked processes that begin with LM or LEX.
Step 3: Grant access or create an exception for the process and a Microsoft™ Windows 7 Firewall Example
Identify your firewall application and identify where you can make changes to your firewall protection settings.
IMPORTANT! This is where you will create exceptions for processes that are listed in the next step below.
Here is a list of possible firewall types, listed from the most common to least common found on PC:
2. Identify the Blocked Process
Now that you have identified your firewall application and where you create exceptions for blocked processes, you will want to use the table below to identify whether a blocked process is visible.
Be aware of your printer model's prefix for the lscn.exe and mon.exe processes.
Model-specific prefixes:
Common prefixes: <LM>, <lex>
For example, LMADLmon.exe contains the prefix <LMADL> which references a Lexmark Pro5500 inkjet printer.
| Process <prefix> - lxcq | Function | Possible error/symptom if process blocked |
|
<prefix>lscn.exe Lean Scan |
Required for successful Scan Profile communication. For example, if you press Scan > Scan Profile... |
Computer Connection Error is displayed on the printer. |
|
<prefix>mon.exe Device Monitor |
This listens for button presses from the device for operator panel-initiated scanning. For example, if you press Scan > Computer... |
No response when you press |
|
LMsmc.exe/ lmab1err.exe (All Models)
Status Messenger in Windows |
The Status Monitor Center controls:
|
Logs and printer notifications will not be displayed. |
|
LMpsu.exe (All Models) Printer Setup Utility |
Allows for the configuration of printer fax settings and address book settings. Lexmark Printer Setup Utility or Fax Setup Wizard utilizes this process. | Unable to add/edit contacts or change settings on the printer from either of these utilities. |
|
LMwpss.exe (All Models) Wireless Print Server Setup Utility |
Necessary for the successful configuration your wireless printer. Lexmark Wireless Setup Utility requires this process. | Gray Continue button and the inability to configure wireless configuration parameters on the printer. |
|
(All Models) lextwprotocol.dll, lexnetworkds.ds LMabscw.dll LMabmini.dll LMabtwds.ds LMabtwpro.dll LMabtwui.dll LMabdrs.dll LMabdrs64.dll LMzzz_32__bc.dll LMzzz_32serv.dll |
These associated local/network TWAIN files require a network TWAIN compliant application to use them... |
If the application that uses these files is blocked by a firewall, then these are files are blocked by association.
Also, make sure your scanning software (.exe) is not blocked by a firewall. |
3. Grant access or create exception in the Firewall Application
You have now identified the blocked process in your firewall application. You will now need to grant permissions in your firewall application to allow these processes to communicate over the network.
Common Network TWAIN file directory locations
Some firewall applications require that you enter or identify the directory where the filename is located.
You can perform a search on the filename to identify the file path.
| Filename | Filename Location (Vista 32-bit OS example) |
| lextwprotocol.dll | Program Files/Lexmark/NetworkTwain |
| LMabscw.dll | C:/Program Files/Lexmark Pro5500 Series |
| LMabmini.dll | Program Files/Lexmark Pro5500 Series/Drivers/x86 |
| LMabtwpro.dll | Program Files/Lexmark Pro5500 Series/Drivers |
| LMabtwui.dll | Program Files/Lexmark Pro5000 Series/Drivers |
| LMabdrs.dll | Program Files/Lexmark Pro5500 Series/Drivers/x86 |
| LMabdrs64.dll | Does not exist (since OS simulated is 32bit) |
| LMzzz_32__bc.dll | Program Files/Lexmark/NetworkTwain |
| LMzzz_32serv.dll | Program Files/Lexmark/NetworkTwain |
Click here for examples showing how to create firewall exceptions.
To summarize, grant permission, access, or an exception for all <prefix> file types( .exe, .dll and .ds) listed below to allow full printer-to-computer communication.
IMPORTANT! You need to know where your firewall software allows you to grant exceptions or permissions.
NOTE: All firewall manufactures use slightly different terminology to reference this permission granting process; e.g., Permit Always, Allow Full Access, Allow, etc.
If you receive a Windows Security Alert, make sure you select Allow access for any LM process:

How to grant firewall exceptions with Microsoft's Windows Firewall
If you do not allow access for all LM and LEX processes, you may need to follow the procedure similar to this one.
To open Windows Firewall and allow exceptions in Microsoft™ Windows 7:
| Step | Action |
| 1 | Click on Start. |
| 2 | Click on Control Panel. |
| 3 | Click on Windows Firewall. |
| 4 | Click on Allow a program or feature through Windows Firewall. |
| 5 | Click on Change Settings. |
| 6 |
Place a checkmark in the box next to any the processes that require exceptions. Note: You may see more than one instance of the process. If so, make sure they are all selected for exceptions. |
| 7 | Place a checkmark in the box for all logged-in network connections. |
| 8 | Click OK. |

NOTE: Click here for more information provided by Microsoft™.
Related Article
Firewall Preventing Communication or "Communication Failure" Error When Trying to Scan, Print, or Perform a Smart Solution Function (For older printer models)
Still Need Help?
If you need additional assistance, please contact Lexmark Technical Support. NOTE: When calling for support, you will be asked for your machine/model type and serial number (SN).
Please call from near a computer and printer in case the technician on the phone asks you to perform a task involving one or all of these devices.