I've previously had this working but with multifunction printers. Starting yesterday I began working to get scanners to work. When I log into the workspace the FabulaTech icon is gray and gives a message that there is no workstation connection. I get this message from multiple systems. The workstation package has been installed to the physical computer and the server component to the workspace at AWS. The host computers run Windows 7 64-bit, the workspace is essentially a terminal server session to a Windows 2012 R2 Datacenter server.
Thank you for any ideas on this problem
Scott L
IP Logged
Sergey_Jarovski FabulaTech Forum Moderator
FabulaTech Forum God
Gender: Posts: 559
Re: Scanner not showing in AWS Workspace Reply #1 on: Oct 18th, 2017, 9:36am
As I understand that you have a "No connection to workstation module" message of Scanner for Remote Desktop (server) GUI (on the remote side within RD session), correct? If yes, please check the status of "FabulaTech Scanner for RD Workstation" and "FabulaTech Netlink 3 supervisor" services on Scanner for Remote Desktop (workstation) PC, run them if needed.
The workspace shows the following services as running FabulaTech License Server, FabulaTech Netlink 3 session service, FabulaTech Netlink 3 supervisor service and FabulaTech Scanner for RD Server; There isn't a workstation service showing on the remote Workspace.
Scott
IP Logged
Sergey_Jarovski FabulaTech Forum Moderator
FabulaTech Forum God
Gender: Posts: 559
Re: Scanner not showing in AWS Workspace Reply #3 on: Oct 19th, 2017, 7:47am
One clarification. You must: - install Scanner for Remote Desktop (workstation) locally (on Win7x64 PCs); - install Scanner for Remote Desktop (server) on the remote (AWS) side (on Win2k12r2 PC).
I wrote "please check the status of "FabulaTech Scanner for RD Workstation" and "FabulaTech Netlink 3 supervisor" services on Scanner for Remote Desktop (workstation) PC". But you are talking about Scanner for Remote Desktop (server) PC.
Have you tried testing with a different scanner or updating the scanner's TWAIN/WIA driver? I've seen cases where the RDP side was working fine, but an older driver caused inconsistent behavior. It's a quick thing to rule out before digging deeper.
Home
Search
Members
Login
Register
Reply
Notify of replies
Print
Author
Quote
Modify
IP Logged
Posts: 559