12-12-2011 01:04 AM - edited 12-12-2011 10:36 PM
Hello,
we have our users working from home with a SA-2500 7.0R2 SSL VPN . They start a remote desktop session from within the juniper enviroment to our Terminal servers. This works great. Recently we have enabled the Microsoft function, easy print. What this does is it maps the client local printer in the remote desktop session. This works for about 98% of our users. However for the 2% that doesn't work, it does work with the windows client. MSTSC directly to the terminal server. So it doesn't work with the juniper rdp client but it does work with the microsoft client. How is this possible? is this a certain setting I missed?
The faulty users all use windows 7 x64. But its proven on other clients that this isn't a problem.
12-12-2011 11:43 AM
Hi Jellekamma,
if you're using Juniper RDP proxy you should permit local printers, it's a specific setting.
Hope this was the missing part ;-)
Regards
NULL
12-12-2011 10:32 PM
thanks NULL, but this setting is already enabled. otherwise the remaining 98% wouldn't be able to print at all. So I guess that wasn't it either..
12-21-2011 11:25 PM
anyone else who can help me?
03-14-2012 11:03 PM
Hello
Windows Easyprint isnt supported by juniper RDP client, and thats it.
Juniper SSL-VPN has their own solution called easyprint, but that means you need to get a license for the advanced RDP applet. And the easyprint function isnt liked by the users since the user needs to select printer everytime they print.
I dont know why Windows easyprint doesnt, work, but i sure hope juniper will fix it.
Juniper KB21906:
Summary:
03-21-2012 06:21 PM