x64 Terminal Server Printer Driver Redirection Wizard
in [Terminal Services]
|
From: Vera Noest [MVP] on 11 Jul 2006 16:33 Yes, I routinely map all unknown printers by modifying ntprintsubs.inf. I wouldn't think that 64-bit Windows handles this differently. If the EventLog doesn't log any printer events at all, then it means that the Terminal Server doesn't even try to redirect your local printer. Either redirection is not configured on the server or the client, or the printer uses a non-standard port on the client (like a DOT4 port). 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?SmVmZmVyeSBKb25lcw==?= <JefferyJones(a)discussions.microsoft.com> wrote on 11 jul 2006 in microsoft.public.windows.terminal_services: > Vera: > Thank you for this. > > I will setup the redirection wizard manually using the Technet > article. Have you tried this procedure? Are there any > modifications to adapt this to 64 bit server? > > One other problem, the Event log is not reporting Events 1111. > That is, when I connect with RDP client, with printers enanbled, > no errors show in the log. > No printers show up in "Printers and Faxes". The print spooler > is setup to > log all printer events: Information, Warning, Error. Local > Security Policy is enabled for sucess and failure for all events > in the Audit Policy section. > > I am using a 32 bit client to connect to the 64 bit Terminal > Server. It is the latest version of the RDP client. > > I appreciate any help you can give.
From: Jeffery Jones on 11 Jul 2006 17:30
Vera: Thanks again for your comments. I discovered why I was not getting 1111 error messages. The reason is because I am still configuring the terminal server. It is not in an OU that forces "connect printers at logon". That same parameter is also not set in the environment tab of my user profile account in active directory. You are right, Terminal Server was not even trying to redirect my printers. Thanks again. -- Jeffery Jones "Vera Noest [MVP]" wrote: > Yes, I routinely map all unknown printers by modifying > ntprintsubs.inf. > I wouldn't think that 64-bit Windows handles this differently. > > If the EventLog doesn't log any printer events at all, then it > means that the Terminal Server doesn't even try to redirect your > local printer. Either redirection is not configured on the server > or the client, or the printer uses a non-standard port on the > client (like a DOT4 port). > > 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?SmVmZmVyeSBKb25lcw==?= > <JefferyJones(a)discussions.microsoft.com> wrote on 11 jul 2006 in > microsoft.public.windows.terminal_services: > > > Vera: > > Thank you for this. > > > > I will setup the redirection wizard manually using the Technet > > article. Have you tried this procedure? Are there any > > modifications to adapt this to 64 bit server? > > > > One other problem, the Event log is not reporting Events 1111. > > That is, when I connect with RDP client, with printers enanbled, > > no errors show in the log. > > No printers show up in "Printers and Faxes". The print spooler > > is setup to > > log all printer events: Information, Warning, Error. Local > > Security Policy is enabled for sucess and failure for all events > > in the Audit Policy section. > > > > I am using a 32 bit client to connect to the 64 bit Terminal > > Server. It is the latest version of the RDP client. > > > > I appreciate any help you can give. > |