Win 2003 TS: Local Printers Not Showing Up

[Allan]

All remote clients are Win XPP using RDC. At some remote sites, the local
printers do not show up in TS session. Local printers are a mix of jet
directs, LPT1, and USB. Having read the other posts on printing, the only
commonality for printers not showing up is that their internet connection is
ADSL. There is an ADSL modem connected to a router. The local router is
running dhcp, and at every remote site the subnet is different that the main
office. Why are the local printers not showing up?

[Vera Noest [MVP]]

ADSL or not shouldn't make a difference, I've worked for years with
printer redirection over a 19 kb modem connection (painstakingly
slow, but it works :-)
Is there anything in the EventLog on the 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 Allan
All remote clients are Win XPP using RDC. At some remote sites,
the local printers do not show up in TS session. Local printers
are a mix of jet directs, LPT1, and USB. Having read the other
posts on printing, the only commonality for printers not showing
up is that their internet connection is ADSL. There is an ADSL
modem connected to a router. The local router is running dhcp,
and at every remote site the subnet is different that the main
office. Why are the local printers not showing up?

[Allan]

I have been reviewing the System Log in the Event Viewer. It appears that
those local printers, lpt1 - usb - jetdirect - etc, that do not show up on
the remote workstations while logged into a TS session may have drivers not
included in the W2K3 printer database, ie "Dell Laser Printer 1700n". When I
setup the RDC clients, I checked "Printers" under the "Local Resources" tab
to enable local printing while logged into a TS session. I did not install
any printers on the Terminal Server. In the System log I am getting some
Event ID: 1111, Source: TermServDevices. Is this the reason some printers
show up and others do not? Do I simply create printer objects on the Terminal
Server for those printers that are not included in the driver database? If
so, what port do I use, ie: lpt1? tks.

Post by Vera Noest [MVP]
ADSL or not shouldn't make a difference, I've worked for years with
printer redirection over a 19 kb modem connection (painstakingly
slow, but it works :-)
Is there anything in the EventLog on the 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 Allan
All remote clients are Win XPP using RDC. At some remote sites,
the local printers do not show up in TS session. Local printers
are a mix of jet directs, LPT1, and USB. Having read the other
posts on printing, the only commonality for printers not showing
up is that their internet connection is ADSL. There is an ADSL
modem connected to a router. The local router is running dhcp,
and at every remote site the subnet is different that the main
office. Why are the local printers not showing up?

[Vera Noest [MVP]]

Yes, that's the reason.
No, you should not create the printers on the TS, and absolutely
not install any 3th party drivers on the server. Such drivers are
very often not TS-compatible, and they often cause print spooler
crashes.

What you have to do is to map the local printer driver (which you
get from Event 1111) to a native (=build in 2003) printer driver,
by creating a custom ntprintsubs.inf file. Details are here:

239088 - Windows 2000 Terminal Services Server Logs Events 1111,
1105, and 1106
http://support.microsoft.com/?kbid=239088

If you are unsure which native driver to map to, check this site:
http://www.printingsupport.com/matrix.htm

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

Post by Allan
I have been reviewing the System Log in the Event Viewer. It
appears that those local printers, lpt1 - usb - jetdirect - etc,
that do not show up on the remote workstations while logged into
a TS session may have drivers not included in the W2K3 printer
database, ie "Dell Laser Printer 1700n". When I setup the RDC
clients, I checked "Printers" under the "Local Resources" tab
to enable local printing while logged into a TS session. I did
not install any printers on the Terminal Server. In the System
log I am getting some Event ID: 1111, Source: TermServDevices.
Is this the reason some printers show up and others do not? Do I
simply create printer objects on the Terminal Server for those
printers that are not included in the driver database? If so,
what port do I use, ie: lpt1? tks.

Post by Vera Noest [MVP]
ADSL or not shouldn't make a difference, I've worked for years
with printer redirection over a 19 kb modem connection
(painstakingly slow, but it works :-)
Is there anything in the EventLog on the 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 Allan
All remote clients are Win XPP using RDC. At some remote
sites, the local printers do not show up in TS session. Local
printers are a mix of jet directs, LPT1, and USB. Having read
the other posts on printing, the only commonality for
printers not showing up is that their internet connection is
ADSL. There is an ADSL modem connected to a router. The local
router is running dhcp, and at every remote site the subnet
is different that the main office. Why are the local printers
not showing up?

[Allan]

Once the local print driver is mapped to the W2K3 TS, I am presuming that the
redirect port does not matter, ie: lpt1, usb, jetdirect, or p2p. KB239088
references W2K. Is the registry edit the same for W2K3? tks

Post by Vera Noest [MVP]
Yes, that's the reason.
No, you should not create the printers on the TS, and absolutely
not install any 3th party drivers on the server. Such drivers are
very often not TS-compatible, and they often cause print spooler
crashes.
What you have to do is to map the local printer driver (which you
get from Event 1111) to a native (=build in 2003) printer driver,
239088 - Windows 2000 Terminal Services Server Logs Events 1111,
1105, and 1106
http://support.microsoft.com/?kbid=239088
http://www.printingsupport.com/matrix.htm
--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

Post by Allan
I have been reviewing the System Log in the Event Viewer. It
appears that those local printers, lpt1 - usb - jetdirect - etc,
that do not show up on the remote workstations while logged into
a TS session may have drivers not included in the W2K3 printer
database, ie "Dell Laser Printer 1700n". When I setup the RDC
clients, I checked "Printers" under the "Local Resources" tab
to enable local printing while logged into a TS session. I did
not install any printers on the Terminal Server. In the System
log I am getting some Event ID: 1111, Source: TermServDevices.
Is this the reason some printers show up and others do not? Do I
simply create printer objects on the Terminal Server for those
printers that are not included in the driver database? If so,
what port do I use, ie: lpt1? tks.

Post by Vera Noest [MVP]
ADSL or not shouldn't make a difference, I've worked for years
with printer redirection over a 19 kb modem connection
(painstakingly slow, but it works :-)
Is there anything in the EventLog on the 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 Allan
All remote clients are Win XPP using RDC. At some remote
sites, the local printers do not show up in TS session. Local
printers are a mix of jet directs, LPT1, and USB. Having read
the other posts on printing, the only commonality for
printers not showing up is that their internet connection is
ADSL. There is an ADSL modem connected to a router. The local
router is running dhcp, and at every remote site the subnet
is different that the main office. Why are the local printers
not showing up?

[Vera Noest [MVP]]

Yes, KB 239088 applies to 2003 as well.
Regarding the printer ports: you might need this information:

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 ---

Post by Allan
Once the local print driver is mapped to the W2K3 TS, I am
presuming that the redirect port does not matter, ie: lpt1, usb,
jetdirect, or p2p. KB239088 references W2K. Is the registry edit
the same for W2K3? tks

Post by Vera Noest [MVP]
Yes, that's the reason.
No, you should not create the printers on the TS, and
absolutely not install any 3th party drivers on the server.
Such drivers are very often not TS-compatible, and they often
cause print spooler crashes.
What you have to do is to map the local printer driver (which
you get from Event 1111) to a native (=build in 2003) printer
driver, by creating a custom ntprintsubs.inf file. Details are
239088 - Windows 2000 Terminal Services Server Logs Events
1111, 1105, and 1106
http://support.microsoft.com/?kbid=239088
If you are unsure which native driver to map to, check this
site: http://www.printingsupport.com/matrix.htm
--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

Post by Allan
I have been reviewing the System Log in the Event Viewer. It
appears that those local printers, lpt1 - usb - jetdirect -
etc, that do not show up on the remote workstations while
logged into a TS session may have drivers not included in the
W2K3 printer database, ie "Dell Laser Printer 1700n". When I
setup the RDC clients, I checked "Printers" under the "Local
Resources" tab to enable local printing while logged into a
TS session. I did not install any printers on the Terminal
Server. In the System log I am getting some Event ID: 1111,
Source: TermServDevices. Is this the reason some printers
show up and others do not? Do I simply create printer objects
on the Terminal Server for those printers that are not
included in the driver database? If so, what port do I use,
ie: lpt1? tks.

Post by Vera Noest [MVP]
ADSL or not shouldn't make a difference, I've worked for
years with printer redirection over a 19 kb modem connection
(painstakingly slow, but it works :-)
Is there anything in the EventLog on the TS?
--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
wrote on 07 feb 2005 in

Post by Allan
All remote clients are Win XPP using RDC. At some remote
sites, the local printers do not show up in TS session.
Local printers are a mix of jet directs, LPT1, and USB.
Having read the other posts on printing, the only
commonality for printers not showing up is that their
internet connection is ADSL. There is an ADSL modem
connected to a router. The local router is running dhcp,
and at every remote site the subnet is different that the
main office. Why are the local printers not showing up?