Have you checked the EventLog on the Terminal Server?
If you see an Event 1111, indicating that redirection of the
printer failed, because the driver was not found, then you probably
have a mismatch in driver names.
If that is the case, you can solve it by creating a custom
ntprintsubs.inf file to map the driver names.
Documented here:
239088 - Windows 2000 Terminal Services Server Logs Events 1111,
1105, and 1106
http://support.microsoft.com/?kbid=239088
If you don't see any Event at all regarding redirection of the
printer, then check the local printer port.
HP has a habit of creating a custom printer port, often called
DOT4. If that's the case, you have to make a registry change on you
client to get the printer port redirected.
Details here:
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
http://hem.fyristorg.com/vera/IT
___ please respond in newsgroup, NOT by private email ___
=?Utf-8?B?TWl0ZXNoIFBhdGVs?=
<(E-Mail Removed)> wrote on 06 jul 2005 in
microsoft.public.win2000.termserv.apps:
> Hi,
> I have win2000 server running terminal services in Application
> mode. I have laptop and local HP 4000 Leaser printer installed.
> But when I connect to terminal server using Remote desktop
> client or Terminal client my local printer is not showup there.
> On terminal server serivce configuration I put check mark on map
> local printer but didn't help.