Re: Printer autocreation failing
- From: "Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 06 Dec 2006 13:45:01 -0800
Which OS are you running on the TS?
And which version of the rdp client are you running?
No Events in the EventLog on the server means that redirection is
not attempted at all.
Check the configuration of local device redirection in the RDP
client, update the client to the latest version, which supports
redirection of network printers and apply KB article 302361 in case
of a non-standard local port name.
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 ___
"Rob Oldfield" <blah@xxxxxxxx> wrote on 06 dec 2006 in
microsoft.public.windows.terminal_services:
Hi,.
I've got a very strange problem with a couple of printers
failing to autocreate correctly. Basic setup is a single TS box
running at our head office, and two branch offices connecting in
to it. Both sites were working (and printing) fine, until we
had to replace a broken printer at one of the offices. The new
one was a Lexmark T640 which was failing to autocreate for
clients correctly (details are pretty similar to the other
printer which I'm going to go on to mention.) We gave in on
that and, because we have a Lexmark T632 working fine in the
other remote office, thought we'd just get another one of those
- as we know that that works fine.
Plugged the new 632 in, installed drivers (using the exact same
driver install file that I used at the office that works) on the
server at the remote office (set up in exactly the same way as
the office that works), installed printer to local desktops (in
exactly the same way, by double clicking the shared printer on
the local server)... and it still fails to autocreate. No
messages in event logs about why it's failing to do so.
Does anyone have any ideas about what might be going wrong?
- Follow-Ups:
- Re: Printer autocreation failing
- From: Rob Oldfield
- Re: Printer autocreation failing
- From: Rob Oldfield
- Re: Printer autocreation failing
- References:
- Printer autocreation failing
- From: Rob Oldfield
- Printer autocreation failing
- Prev by Date: Re: Terminal Services Usage
- Next by Date: Re: trace the terminal serice activity
- Previous by thread: Re: Printer autocreation failing
- Next by thread: Re: Printer autocreation failing
- Index(es):
Relevant Pages
|
Loading