My issue may be a duplicate from this earlier post: http://forum.support.xerox.com/t5/Copying-Faxing-Scanning/Workcenter-3220-and-network-scan/m-p/788/h...
I am using Windows Server 2003 and WorkCentre 3220 connected to the network. Users connect to the server via Terminal Services. While their session is active, network scan works exactly as expected. As soon as the user disconnects from their session or the session "locks" (requiring them to renter their password), selecting network scan from the scanner shows a "unavailable" message.
When logging back into a Terminal Services session, the status icon in the Network Scan program can be seen quickly changing from a red "X" to the normal "online" icon.
As users must be standing in front of the scanner to do a network scan, it's unrealistic to expect them to always leave their session active and unlocked while away from their computer.
Any suggestions on how to keep Network Scan (really) always running?
Thank you for using the Support Forum. Please take a look at this solution for setting up scan from the support pages for your machine. Make sure you have followed all the steps. If your setup checks out please consider contacting your support centre for further assistance.
Thanks for the info.
I've gone back and followed the instructions you provided, and they are in fact the exact procedure I follow when setting up the Network Scan utility (except for the email part, as I am not using that feature).
I ended up opening an official support ticket for this issue, and so far all I've been told is that my problem isn't usual, and asked if it happens on other computers.
I've done tests, installing the Network Scan utility on a Windows 7 Professional workstation. The utility works as expected when the user is logged in at the terminal, HOWEVER, when users log into the workstation via RDP (Remote Desktop) and then disconnet, the User ID is no longer available on the scanner.
So the problem exists on Windows Server 2003 and Windows 7 Professional, when users disconnect from (but do not log off of) their remote desktop / terminal services session.
I found another forum Topic which appear to be the same problem:
Yeah, looks like the suggestion from Xerox Support is to either work around it, or call them and go over all of this again.
Is email support through Xerox limited to level 1?
I do have more details on my issue:
This problem only seems to occur when using RDP to log into the console session on any operating system that supports RDP or Terminal Services. Once logged into the console session, if you setup the Network Scan application then disconnect, the application must recieve and handle some kind of a "disconnect" event from the OS, effectively disabling the application. I've been able to reproduce this behavior consistently.
Connecting to the console session, or administering a terminal server:
Old RDP Clients - http://support.microsoft.com/kb/278845
This must be by design, and I assume is an undocumented feature of which Xerox support is simply unaware.