Network Printer not showing up as session printer on terminal server - windows server 2003

Hi guys,

I am having an issue where a remote user is unable to print to his home printer via session printer in server 2003.

A bit of research told me that this function is only avaliable for locally installed printers.

is there a way of getting around this and having the network printer as a session printer?

If anyone has any idea's it would be greatly appreciated.

Thanks
LVL 2
SM17CHAsked:
Who is Participating?
 
kuohConnect With a Mentor Commented:
Odd that this older KB says it does work.

http://support.microsoft.com/kb/300698
0
 
kuohCommented:
Is it a network printer in the sense that it is shared off another PC in the user's home LAN or just one that is directly attached to the LAN?  If it's the latter, then it is still considered a locally installed printer.  Usually, you would also need to install the identical print driver on the server.  After that, the printer should show up.
0
 
SM17CHAuthor Commented:
Not shared off another Lan PC.
Installed using tcp/ip port.
0
Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

 
kuohCommented:
Then it should work, did you install the print driver on the server?  You might also have the user double check that printers in the "Local Resources" tab of the RDP client options is checked.
0
 
SM17CHAuthor Commented:
I haven't installed the print driver on the terminal.
I thought that tcp/ip printers did not redirect.
I found this support article which says the same.
http://support.microsoft.com/kb/302361
I found this, ran through the fix but it did not work for me.
0
 
kuohCommented:
The KB does seem to imply that, but I know it works for some RDP clients, because we had to make a change in the ASA to allow local lan access for a VPN user so they could use their network printer.  Before the change, the OS would just queue up the print jobs until the user disconnected the VPN, then everything started spitting out once IP access to the printer was restored.  The thing I can't remember now is whether the user's OS was XP, Vista or 7.  Perhaps it's an undocumented "fix" in the newer RDP clients?
0
 
SM17CHAuthor Commented:
Thanks for the help, it turned out to be a driver issue.

adding a new driver on the server solved my problem.

(under printers and faxes > file > server properties > Drivers)
0
All Courses

From novice to tech pro — start learning today.