Discussion:
No remote printers
(too old to reply)
JRR
2005-02-07 12:35:37 UTC
Permalink
I'm having a big problem lately with remote printing and 2003 and 2000 TS.
The drivers are the same on the TS and the client, the printers have exactly
the same name, but they just are not showing up in a session.

Also having a problem on one TS where the session printers are not deleted
when the client logs out. This one is a 2000 TS. There are only 3 clients
on this TS, so the Microsoft KB doesn't apply.
Vera Noest [MVP]
2005-02-07 21:31:54 UTC
Permalink
And printer redirection is enabled on the server and client side, I
assume?
Anything in the EventLog on either TS?

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
Post by JRR
I'm having a big problem lately with remote printing and 2003
and 2000 TS. The drivers are the same on the TS and the client,
the printers have exactly the same name, but they just are not
showing up in a session.
Also having a problem on one TS where the session printers are
not deleted when the client logs out. This one is a 2000 TS.
There are only 3 clients on this TS, so the Microsoft KB doesn't
apply.
b***@gmail.com
2005-02-09 00:01:11 UTC
Permalink
You may want to check out this MS article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;302361

If the printers are not on a port that starts with COM, LPT, or USB,
they won't be mapped by default. There's a registry hack to remove this
filter.
JRC
2005-02-10 14:22:50 UTC
Permalink
Interestingly enough, the terminal server in question (2000) does not have
the key mentioned in the KB article.
Post by b***@gmail.com
http://support.microsoft.com/default.aspx?scid=kb;en-us;302361
If the printers are not on a port that starts with COM, LPT, or USB,
they won't be mapped by default. There's a registry hack to remove this
filter.
Vera Noest [MVP]
2005-02-10 21:31:39 UTC
Permalink
The article isn't very clear on this point, but the registry key has
to be edited on the client, not on the server.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
Post by JRC
Interestingly enough, the terminal server in question (2000)
does not have the key mentioned in the KB article.
Post by b***@gmail.com
http://support.microsoft.com/default.aspx?scid=kb;en-us;302361
If the printers are not on a port that starts with COM, LPT, or
USB, they won't be mapped by default. There's a registry hack
to remove this filter.
JRC
2005-02-11 14:12:27 UTC
Permalink
Well, that would make a difference... I hope. You ain't kidding the
article isn't clear. It blantantly leads you to doing this at the server.
Post by Vera Noest [MVP]
The article isn't very clear on this point, but the registry key has
to be edited on the client, not on the server.
--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
Post by JRC
Interestingly enough, the terminal server in question (2000)
does not have the key mentioned in the KB article.
Post by b***@gmail.com
http://support.microsoft.com/default.aspx?scid=kb;en-us;302361
If the printers are not on a port that starts with COM, LPT, or
USB, they won't be mapped by default. There's a registry hack
to remove this filter.
Loading...