Yes, that's the most interesting thing. On the physical client itself (from where i connect to the virtual desktop using the view client) the same printer works without any issues.
I haven't tried yet so far to add the network manualy on the virtual desktop as it get's its IP by a DHCP server responsible for the virtuel desktop IP range. (which is of course completely different than the one i am using at home on my physical machine.
i will try to setup the IP manually on the virtual desktop, but cannot really image it would makes a difference...
Thanks for the KB, i will try to go through as my next step...
The very interesting thing is, if i send a document to the mapped (redirected) printer on the virtual desktop and if i watch the both printer queues (virtual desktop and physical desktop), i am able to see the document gets first into the virtual desktops printer queue, and as is gets out there, it gets into the local (physical) printer queue...
meaning, the data is processed as expected and it must be somehow a local problem on the physical machine...
Of course i have already tried to use several different physical machines with different network and USB attached printers... but its everywhere the same issue...
The document (print) is getting lost somewhere between the local (physical printer queue) and the local attached printer...
Before i had the ThinPrint Client installed on my local physical machine, because i use it with some Terminal Servers and TP Server Engine... First i thought maybe that could be the issue... but also after removing the ThinPrint Client and even on a fresh installes client device with O.S. / printer / and view client only it's still the same issue...