Skip to main content

Scanning to USB with the Xerox WorkCentre 3210 and 3220 (part 1)

The WorkCentre 3210 and WorkCentre 3220 are two variants of an entry level Xerox business level multifunction printer.  The couple bring a lot to the table in terms of features and longevity, but it's not always clear as to how to operate the machines.  While the printers do come with a manual, like most documentation for consumer devices, it's awful.  Well, awful in that it's brief.

It's a catch 22 situation really.  Literature for consumer devices is seldom referred to, but there's, for some reason, a demand for it.  As a consequence, it's typically brief and offers no assistance when problems arise.  This is the first of a two-part piece on extending the documentation that comes with the 3210/3220.


Scanning to USB:  The media


This first piece is actually a log of the troubleshooting steps used to resolve a problem with the scan to USB feature.

The WorkCentre has a feature whereby it can scan documents directly to a drive through its built-in USB port.  Upon attempting this for the first time, there was some difficulty getting the device to scan.  In fact it wouldn't even try.  Instead what happened was the printer stepped through some output on the LCD display panel.  It said, "Updating Data Please Wait...."  The printer would go through this step and then just return to the state it was in before.  After trying a few things such as using different SD cards, verifying that there was enough space on the disks, and reformatting one, all attempts were abandoned.

The disk that was connected to the printer was an SD card via a USB card reader.  The next attempt was with an actual USB flash drive and this was the ticket!  For whatever reason, card readers are not allowed.  Using the flash drive however, the scanner started right away without a hitch.  It should be noted though, that the "Updating Data Please Wait..." operation was run again.  Only this time, it was after the scan.  It's not clear what this step in the process is actually accomplishing, but it will likely run with each scan.

Part 2:  The document files

Comments

Post a Comment

Popular posts from this blog

Remove control of Chrome being managed by organization on personal devices

Chrome may indicate that it's being managed by a user's organization. This warning is provided by the Chrome Policies feature of the browser. To know if an instance of Chrome is managed by an organization, there will be an entry at the bottom of the browser’s hamburger menu (three dot menu), on the right side of the browser window that reads, "Managed by your organization." This is likely due to an entry in the Chrome Policies listing, which can be found by loading this page in the browser: chrome://policy The policies listed in this section are stored in the computer's file system in one of the following locations as JSON files. /usr/share/chromium/policies/managed /usr/share/chromium/policies/recommended Remove the offending JSON files, and click the Reload policies button. The Managed by your organization entry in the browser menu should be gone. A notice like this on instances of Chrome for work, school, library, or other devices that belong to an organizati...
Post a Comment
Read more

Allow Windows authentication using SQL Server driver with DBeaver

DBeaver will allow Microsoft Windows single sign on access when connecting to Microsoft SQL Server using the SQL Server driver (rather than jTDS ).  From the driver properties settings, set the integratedSecurity flag to true . Open the Connection configuration panel and choose the Driver properties section. Set the integratedSecurity flag to true . A subtle, but important step is to not provide username and password credentials to the connection.
7 comments
Read more

Connecting to SQL Server with jTDS using Windows Authentication

UPDATE:   At one point the tip in this article to set the USENTLV2 flag to true was accurate, but it appears it is no longer necessary, at least as far as DBeaver 's use of the driver is concerned.  If it solves an authentication problem, then great.  The expectation is that, an update in one of the packages that make this sort of connection possible has resolved the issue that at one time made this flag necessary. Connecting to Microsoft SQL Server using jTDS with a username and password that's managed by the database manager is pretty straightforward.  It may become a little more problematic however, when trying to use Windows authentication when connecting from a Windows machine. Do not supply a username and password. Set the USENTLMV2 property to true. NOTE:   Step 1 assumes a connection being made from a Windows machine.  If the connection is being made from something else, user credentials may actually be necessary. If the connect...
7 comments
Read more