How to Fix Common ScanRouter EX Professional Connection Errors
Ricoh’s ScanRouter EX Professional is a foundational document distribution software used to route scans from multifunction printers (MFPs) to network destinations. Because it relies heavily on legacy network protocols and specific Windows services, connection errors are common.
When delivery fails, users are typically met with vague error codes on the MFP operation panel or connection timeout logs in the ScanRouter administration utility.
Here is how to troubleshoot and resolve the most common ScanRouter EX Professional connection failures. 1. Verify the ScanRouter Windows Services
ScanRouter relies on background Windows services to communicate with your MFPs. If these services stop running, all network connections fail immediately. Action Steps: Press Windows Key + R, type services.msc, and press Enter.
Scroll down to find the services starting with ScanRouter (e.g., ScanRouter V2 Administration Service).
Check the Status column. If it does not say Running, right-click the service and select Start.
Right-click the service, select Properties, and change the Startup type to Automatic to ensure it launches after a server reboot. 2. Address IPv4 vs. IPv6 Communication Conflicts
ScanRouter EX Professional is a legacy application designed primarily for IPv4 networks. Modern operating systems and routers prioritize IPv6, which can cause severe handshake and connectivity timeouts with the software. Action Steps:
Open the Control Panel on the hosting server and navigate to Network and Sharing Center.
Click Change adapter settings, right-click your active network adapter, and select Properties.
Uncheck the box next to Internet Protocol Version 6 (TCP/IPv6). Click OK to apply changes and reboot the server.
Ensure your Ricoh MFP is also configured with a static IPv4 address within the same subnet. 3. Configure Windows Firewall and Port Exceptions
Firewall blockages are the most frequent cause of the “Cannot connect to the delivery server” error displayed at the copier panel. ScanRouter requires specific ports to remain open for bi-directional communication. Action Steps:
Open Windows Defender Firewall and click on Advanced Settings.
Create a new Inbound Rule for the following TCP and UDP ports:
Port 55434: Used for administrative commands and server communication. Port 10021 / 10022: Used for standard data transmission.
Ensure that the Network Discovery and File and Printer Sharing profiles are set to allowed on private or domain networks. 4. Resolve “Access Denied” and Permissions Issues
If the ScanRouter software connects to the printer but fails to deliver the file to the destination folder, the issue lies with network share permissions or the service logon credentials. Action Steps:
Locate the destination folder where scans are saved on your network.
Right-click the folder, go to Properties, and select the Sharing tab.
Click Advanced Sharing, then Permissions. Ensure the user account or group running the ScanRouter service has Full Control.
If saving to a remote network drive, open services.msc, right-click the ScanRouter service, go to the Log On tab, and switch it from “Local System Account” to a dedicated Domain Administrator or network user account. 5. Rebuild the Device Routing Table
Corrupted device mapping tables within the ScanRouter administration console will cause individual copiers to drop their connections intermittently. Action Steps: Open the ScanRouter EX Professional Administration utility. Navigate to the Meters / Devices section.
Select the problematic MFP, right-click it, and select Delete.
Click Add Device (or Auto-Discover) to re-add the printer using its current IPv4 address.
Click Update Delivery Server to force the software to push the new routing table configuration down to the physical machine.
If you want to dive deeper into a specific error code you are seeing, let me know. I can help you pinpoint the issue if you tell me: The exact error code or message shown on the MFP panel
The Windows Server operating system version hosting ScanRouter
If you recently made any network changes (like a new router or IP subnet change)
Leave a Reply