VPN SSL Print Problem

[#1]

Newbie here, I’m having a very hard time trying to setup SSL VPN. I can connect to the tunnel, and then I RDP to the Terminal Server 2003. The main problem now is trying to print. I thought the easiest way is to print to a LPT1 port. But I’m having no such luck. Did anybody out there get SSL VPN to print?? Or am I going to have to go to IPSec route.

[rwpatterson]

Welcome to the forums. When you' re connected via RDP, the printers are all on the remote server, not the printer(s) next to you... I thought (I may be wrong here) that there was a way to redirect the RDP printer using the Remote Desktop software to the local machine. Take a look at the options in the RDP client.

[#3]

Rwpatterson, Thanks for the reply, I don' t know how to do that. Is there a way you can do that with just the xp version of RDP and terminal server 2003? Also, it does works ok when I bypass the SSL VPN page, and just connect directly from the web.

[rwpatterson]

You' ll have to do some detective work if it succeeds without the SSL VPN. Maybe you are not allowing some additional port (9100 TCP, for example) that the printer option requires...

[Kess]

There are a lot of options in your " Remote Desktop Connection Client" like bandwidth colors, details, animations and LOCAL RESOURCES also. Printers, Serial Ports, Smart Cards, etc. These Options are useless if on the remote Terminal Server the policies deny these local resources. It' s a windows problem, not a FG issue. For me it works great :-) Hope it helps...

[#6]

Kess, Thanks for reply, I have those all turned on, except for audio in terminal services configuration. But I still can' t see my local printers when I use SSL VPN. I opened it up so I could RDP directly from the web. That works, I' m just useing the microsoft version on xp going to windows 2003. So, I don' t think there is a setting on microsoft part.

[Kess]

Network Printers and local printers are different when used with Microsoft Terminal Server 2003. You can understand how they' re configured if on your local machine the port assigned to the printer begins with \\ or not. If the port begins with \\ you won' t be able to take these printers to your terminal server. All the resources must be local in order to be taken to your terminal server. This problem has been resolved in Windows Server 2008.