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.

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.

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?

Originally, this post was published on Monitis Blog, you can check it
here
.
It goes without saying that technology has transformed society and the very nature of how we live, work, and communicate in ways that would’ve been incomprehensible 5 ye…

Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…

Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…