Guest mwagener Posted August 23, 2007 Posted August 23, 2007 Windows server 2003 x64 running TS for user app. Users are able to establish session and print if they are printing to a network printer. Users cannot print if they have a local printer connected usb. The driver is loaded on the server, but what port should it direct to? Currently DOT4. When users print, the jobs stack up on that printer on the server and do not redirect back to the user.
Guest Vera Noest [MVP] Posted August 23, 2007 Posted August 23, 2007 Re: TS client print to local usb printer Check the EventLog on the TS to verify that the issue isn't driver related. If you do not see *any* printer driver related event at the time the user logs on, then you know that the problem is related to the DOT4 port. If so, either update the rdp client to the lates version, which supports non-custom ports, or apply this registry change: 302361 - Printers That Use Ports That Do Not Begin With COM, LPT, or USB Are Not Redirected in a Remote Desktop or Terminal Services Session http://support.microsoft.com/?kbid=302361 _________________________________________________________ Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server TS troubleshooting: http://ts.veranoest.net ___ please respond in newsgroup, NOT by private email ___ =?Utf-8?B?bXdhZ2VuZXI=?= <mwagener@discussions.microsoft.com> wrote on 23 aug 2007 in microsoft.public.windows.terminal_services: > Windows server 2003 x64 running TS for user app. Users are > able to establish session and print if they are printing to a > network printer. Users cannot print if they have a local > printer connected usb. The driver is loaded on the server, > but what port should it direct to? Currently DOT4. > When users print, the jobs stack up on that printer on the > server and do > not redirect back to the user.
Recommended Posts