Windows NT Printers are not auto connecting

  • Thread starter Thread starter stevie
  • Start date Start date
S

stevie

Does anyone know why my remote clients have to reinstall their printers every
morning? I have manually installed the printers on the server, but they won't
auto reconnect for my clients. I am running Terminal 2003, and have installed
all service packs.Any feed back would be appreciated.

Thanks
--
stevie6
 
Network printer connections are per user, even if created by administrators,
not per computer, so if you have "installed" network - as opposed to local -
printers, other users won't see them.

One way to make network printers available to all users is described at
http://members.shaw.ca/bsanders/NetPrinterAllUsers.htm

--
Bruce Sanderson MVP Printing
http://members.shaw.ca/bsanders

It is perfectly useless to know the right answer to the wrong question.



"stevie" <stevie@discussions.microsoft.com> wrote in message
news:FE470D62-35B4-48BF-A9B1-969200857133@microsoft.com...
> Does anyone know why my remote clients have to reinstall their printers
> every
> morning? I have manually installed the printers on the server, but they
> won't
> auto reconnect for my clients. I am running Terminal 2003, and have
> installed
> all service packs.Any feed back would be appreciated.
>
> Thanks
> --
> stevie6
 
Thanks for responding Bruce.
I wasn't clear in my question when I posted it. The problem is with my
remote users, and their local printers. Once they get a session, they have to
reinstall their printers, in every new session. I have Terminal setup to
automatically redirect the local printers.
I have a new project coming up, where there are going to be several users
accessing, a program through remote access, and I don't want them to have to
readd their local printers everyday. Especially the boss !
--
stevie6


"Bruce Sanderson" wrote:

> Network printer connections are per user, even if created by administrators,
> not per computer, so if you have "installed" network - as opposed to local -
> printers, other users won't see them.
>
> One way to make network printers available to all users is described at
> http://members.shaw.ca/bsanders/NetPrinterAllUsers.htm
>
> --
> Bruce Sanderson MVP Printing
> http://members.shaw.ca/bsanders
>
> It is perfectly useless to know the right answer to the wrong question.
>
>
>
> "stevie" <stevie@discussions.microsoft.com> wrote in message
> news:FE470D62-35B4-48BF-A9B1-969200857133@microsoft.com...
> > Does anyone know why my remote clients have to reinstall their printers
> > every
> > morning? I have manually installed the printers on the server, but they
> > won't
> > auto reconnect for my clients. I am running Terminal 2003, and have
> > installed
> > all service packs.Any feed back would be appreciated.
> >
> > Thanks
> > --
> > stevie6
>
 
Local printers should be automatically redirected, and neither you
nor the users themselves should ever have to install them manually.

Basically, there are 2 areas where printer redirection can fail:

1) redirection is not attempted at all
Solution: check the configuration of printer redirection in the RDP
client and on the Terminal Server, update the RDP client to at
least the XP SP2 version or apply KB article 302361 to get support
for redirection of non-standard local port names, including tcp/ip
ports. http://support.microsoft.com/?kbid=302361

2) redirection is attempted, but fails because the server doesn't
have a driver for the printer
Solution: whatever you do, do not install a 3rd party printer
driver on the Terminal Server, unless it is a Windows Hardware
Quality Labs (WHQL) signed driver. Many non-WHQL drivers are not
TS-compatible, and some are known to crash your printer spooler or
the whole server. In stead, map the printer to a native driver by
creating a custom ntprintsubs.inf file, as described in KB article
239088. http://support.microsoft.com/?kbid=239088

If you are running Windows 2003 SP1 on your Terminal Server, you
can configure a Fallback Printer Driver.
If you manage more than a handful of servers and more than a dozen
of printer models, it will be worth it to invest in a 3rd party
printer management solution. If you need to support Host based
printers using Lightweight Imaging Device Interface Language
(LIDIL), you must use a 3rd party Universal Printer Driver.
http://ts.veranoest.net/ts_printing.htm#printutils
_________________________________________________________
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?c3Rldmll?= <stevie@discussions.microsoft.com> wrote on
22 jul 2007 in microsoft.public.windows.terminal_services:

> Thanks for responding Bruce.
> I wasn't clear in my question when I posted it. The problem is
> with my remote users, and their local printers. Once they get a
> session, they have to reinstall their printers, in every new
> session. I have Terminal setup to automatically redirect the
> local printers. I have a new project coming up, where there are
> going to be several users accessing, a program through remote
> access, and I don't want them to have to readd their local
> printers everyday. Especially the boss !
 
Dear Stevie
Me too have faced the same problem, it was due to the printer driver, i
later changed the printer, the problem was due to non (WHQL) signed driver
files, now its ok, my printer driver is windows signed one & its working
perfectly. And also i recommend to use Network printers (NIC enabled printers
and now a days its cheap) in terminal server / client setup.

"Vera Noest [MVP]" wrote:

> Local printers should be automatically redirected, and neither you
> nor the users themselves should ever have to install them manually.
>
> Basically, there are 2 areas where printer redirection can fail:
>
> 1) redirection is not attempted at all
> Solution: check the configuration of printer redirection in the RDP
> client and on the Terminal Server, update the RDP client to at
> least the XP SP2 version or apply KB article 302361 to get support
> for redirection of non-standard local port names, including tcp/ip
> ports. http://support.microsoft.com/?kbid=302361
>
> 2) redirection is attempted, but fails because the server doesn't
> have a driver for the printer
> Solution: whatever you do, do not install a 3rd party printer
> driver on the Terminal Server, unless it is a Windows Hardware
> Quality Labs (WHQL) signed driver. Many non-WHQL drivers are not
> TS-compatible, and some are known to crash your printer spooler or
> the whole server. In stead, map the printer to a native driver by
> creating a custom ntprintsubs.inf file, as described in KB article
> 239088. http://support.microsoft.com/?kbid=239088
>
> If you are running Windows 2003 SP1 on your Terminal Server, you
> can configure a Fallback Printer Driver.
> If you manage more than a handful of servers and more than a dozen
> of printer models, it will be worth it to invest in a 3rd party
> printer management solution. If you need to support Host based
> printers using Lightweight Imaging Device Interface Language
> (LIDIL), you must use a 3rd party Universal Printer Driver.
> http://ts.veranoest.net/ts_printing.htm#printutils
> _________________________________________________________
> 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?c3Rldmll?= <stevie@discussions.microsoft.com> wrote on
> 22 jul 2007 in microsoft.public.windows.terminal_services:
>
> > Thanks for responding Bruce.
> > I wasn't clear in my question when I posted it. The problem is
> > with my remote users, and their local printers. Once they get a
> > session, they have to reinstall their printers, in every new
> > session. I have Terminal setup to automatically redirect the
> > local printers. I have a new project coming up, where there are
> > going to be several users accessing, a program through remote
> > access, and I don't want them to have to readd their local
> > printers everyday. Especially the boss !
>
 
I would like to thank all who responded to my problem, especially Vera and
Bruce. I would up at Vera's web page, and decided to test a Third party print
manager. That took care of the issues, that were perplexing me. Thanks again
for your help!
--
stevie6


"Raneesh Chitootharayil" wrote:

>
> Dear Stevie
> Me too have faced the same problem, it was due to the printer driver, i
> later changed the printer, the problem was due to non (WHQL) signed driver
> files, now its ok, my printer driver is windows signed one & its working
> perfectly. And also i recommend to use Network printers (NIC enabled printers
> and now a days its cheap) in terminal server / client setup.
>
> "Vera Noest [MVP]" wrote:
>
> > Local printers should be automatically redirected, and neither you
> > nor the users themselves should ever have to install them manually.
> >
> > Basically, there are 2 areas where printer redirection can fail:
> >
> > 1) redirection is not attempted at all
> > Solution: check the configuration of printer redirection in the RDP
> > client and on the Terminal Server, update the RDP client to at
> > least the XP SP2 version or apply KB article 302361 to get support
> > for redirection of non-standard local port names, including tcp/ip
> > ports. http://support.microsoft.com/?kbid=302361
> >
> > 2) redirection is attempted, but fails because the server doesn't
> > have a driver for the printer
> > Solution: whatever you do, do not install a 3rd party printer
> > driver on the Terminal Server, unless it is a Windows Hardware
> > Quality Labs (WHQL) signed driver. Many non-WHQL drivers are not
> > TS-compatible, and some are known to crash your printer spooler or
> > the whole server. In stead, map the printer to a native driver by
> > creating a custom ntprintsubs.inf file, as described in KB article
> > 239088. http://support.microsoft.com/?kbid=239088
> >
> > If you are running Windows 2003 SP1 on your Terminal Server, you
> > can configure a Fallback Printer Driver.
> > If you manage more than a handful of servers and more than a dozen
> > of printer models, it will be worth it to invest in a 3rd party
> > printer management solution. If you need to support Host based
> > printers using Lightweight Imaging Device Interface Language
> > (LIDIL), you must use a 3rd party Universal Printer Driver.
> > http://ts.veranoest.net/ts_printing.htm#printutils
> > _________________________________________________________
> > 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?c3Rldmll?= <stevie@discussions.microsoft.com> wrote on
> > 22 jul 2007 in microsoft.public.windows.terminal_services:
> >
> > > Thanks for responding Bruce.
> > > I wasn't clear in my question when I posted it. The problem is
> > > with my remote users, and their local printers. Once they get a
> > > session, they have to reinstall their printers, in every new
> > > session. I have Terminal setup to automatically redirect the
> > > local printers. I have a new project coming up, where there are
> > > going to be several users accessing, a program through remote
> > > access, and I don't want them to have to readd their local
> > > printers everyday. Especially the boss !
> >
 
You're welcome, Stevie! I'm glad that your printer problems are
solved, seems a wise decision to go with a 3rd party printing
solution. Thanks for reporting back here!
_________________________________________________________
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?c3Rldmll?= <stevie@discussions.microsoft.com> wrote on
22 aug 2007 in microsoft.public.windows.terminal_services:

> I would like to thank all who responded to my problem,
> especially Vera and Bruce. I would up at Vera's web page, and
> decided to test a Third party print manager. That took care of
> the issues, that were perplexing me. Thanks again for your help!
 
Back
Top