RemoteApp Printer Redirection (Help!)

[DocGreen]

I have a client trying to use RemoteApp to deploy their LOB database... everything is working just fine, except for printer redirection.

Workstations on the local LAN are fine... but remote workstations are forced to use printer redirection. On the remote workstations, printer redirection seems to work... the redirected printers show up in the list of available printers, but when I attempt to print to the redirected printer, nothing happens.

I've tried enabling Easy Print... I've tried disabling Easy Print... no difference.
I'm not seeing anything relevant in the event logs
The remote workstation is running Windows Vista (though I have the same result when attempting from my own W7 machine)
The server is running Server 2k8 R2 Enterprise
The workstations printer driver is already installed on the server (for a different, identical printer, on the same LAN as the server)

Please help!

 

[YeOldeStonecat]

Sometimes it's a struggle. Some things I try to do....
*Use the same exact version of driver on the server and remote machine.
*Try to use the barebones driver....not the full fluffy featured version
*Try to discourage saying it will work when it's some MFP, and various residential grade printers
*Unidrivers (HP) or Generic (Canon) drivers tend to help on supported machines
*Mainstream business grade printers that have been around for years and were on the list of "Terminal Server Compliant Printers" we followed back in the Citrix and early Terminal Server days work well.
*Once drivers are installed and it's still not working, try changing the ports....when you're remoted in from the client, within the RDP session, go to printers..and locate the printer object...go to its ports..and try changing the port. You'll see new ports there in addition to the usual LTP, USB, and TCP ports...you'll see terminal server ports. TS001, TS002, TS003, etc. Try changing that port to one of the other TS### ports.

 

[DocGreen]

Would connecting the printer directly to the workstation (via USB) potentially help anything? Currently it's connected via ethernet.

I'm working on setting up a site-to-site VPN (waiting on hardware)... once that's setup, won't the server be able to print directly to the network printer at the remote site?

 

[SAG]

By any chance, is the server ALSO the Domain Controller?

 

[DocGreen]

Yes

 

[SAG]

Yes

That can be.... problematic.
If the DC is the RDP server strange/funky things can happen, especially with remote printing.
Google your heart out on that one, there are a few workarounds.
Check this out though: http://support.microsoft.com/en-us/kb/968605

Like I said, a few hacks and tricks can make it work.
But there are PLENTY of ad-on software packages to make it REAL easy.

 

[DocGreen]

Yeah, I've been Googling.

I've fixed this exact problem before... about 4 years ago. Wish I remember what I did! LOL

 

[DocGreen]

That can be.... problematic.
If the DC is the RDP server strange/funky things can happen, especially with remote printing.
Google your heart out on that one, there are a few workarounds.
Check this out though: http://support.microsoft.com/en-us/kb/968605

Like I said, a few hacks and tricks can make it work.
But there are PLENTY of ad-on software packages to make it REAL easy.

You are my hero. The instructions in the MS article worked perfectly! Thanks!!!

 

[SAG]

Awesome!
Once in a while I get one right.

 

[YeOldeStonecat]

Currently it's connected via ethernet.

I'm working on setting up a site-to-site VPN (waiting on hardware)... once that's setup, won't the server be able to print directly to the network printer at the remote site?

Yes....as the VPN will effectively make it on the same network....and it's an IP printer.

 

[gadgetfixup]

Yeah, I've been Googling.

I've fixed this exact problem before... about 4 years ago. Wish I remember what I did! LOL

The older you get the more you say this. I've walked down so many roads recognizing the familiar scenery but for the life of me can't figure out how to get home

 

[DocGreen]

Thanks again for the help, guys. I got a call from the next day saying it wasn't printing again... I was afraid the fix was only temporary and I was still hosed. Turns out the user is just a complete idiot... it's printing just fine, both at the remote office and in my own office.