Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

VPN - remoteVPN printing

Status
Not open for further replies.

davewalden777

Programmer
Dec 16, 2003
21
US
I am using the cisco VPN client for users to access our network through a pix501. After connecting, they use remote desktop to run programs off our terminal server. I am trying to set it up so a user can print from the remote desktop to a printer at their home.

But:
I can't see my (remote)computer on the network from the remote desktop - I can find out the given ip addr and gain access to shared folders but I can't connect to my printer.

When I share my home printer and use the ip addr to gain access, I can see the printer but I can't connect.

I don't want to have to coach my users on how to find their vpn ip addr and use it for access - is there a way to get the home computer to show up on the network and allow printer/shared folder connections?

I have checked the allow local lan access in the vpn client, but when I check the status it shows as no local lan access enabled. I have also tried the connect to local resources in the remote desktop settings with no luck.
 
As long as the print drivers are installed on the Windows Terminal Server you should have no problems. When you connect to the windows server your local printer (LPT) should create a virtual connection to the Windows server. The only big issue that you may ever have is a user printing to abother users printer, but that can be resolved with terminal services profiles and/or letting users administer their own printers.
if you are using the RDP Client, make sure that..........

The Printers option is checked under 'Local Resource' tab
&
The Print Drivers for the remote users printer are installed on the server (check event log for errors)

you do not have to share your printer for these and all communications ride over RDP (tcp 3389). If the remote clients can connect in and work successfully on the terminal server, it is probably not a firewall issue.


-gC-
 
thanks alot gconnect.
i actually had the user bring in her printer
drivers so i could load them, but she got a new computer
and took the cd back home before i could.

thanks again.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top