Printing to shared local printer via Terminal Services

[Guest Erimikos]

ok.. here is our basic setup...

 

Our network has 10 different locations, including the corporate

office. At the corporate office, there are 2 terminal services

servers running Windows 2000 Server, without any sort of load

balancing. Each of our locations are running on their own subnet,

and consist of Windows 95-XP client computers, as well as a couple

laserjet printers. Some of these printers are connected via a

network interface, while some are connected directly to one of the

client computers. We also have some automated systems here (some

using SQL, some using other custom built software) at corporate that

print things to some of these printers.

 

All computer work is done via terminal services. Here is a quick

example of a printing scenario.

 

Person A. logs into her computer, which has a shared local printer

connected to it, then into terminal services. When connecting, she

checks her default printer, as she is mapped to printers at all

locations, to ensure she is connected to the correct location. She

then starts one of our custom applications and prints an item from

there. The system then prints out labels to 1 printer, one item from

an server SQL on her local shared printer (using printer definition of

\\remoteprinter\printername located in SQL), and another page from the

program she is running to her currently selected default printer.

 

Due to this entire process, it seems that the best option we have is

to install printers locally on the clinic machines, and share them

out. We then have users in terminal services sessions connect to

those printer shares on their local machines.

 

This seems to work fairly well for the most part, but recently we have

been having some issues. One location in perticular, If i attempt to

open print properties on their printer from their local machine, it

opens almost instantally, and will print a test page perfectly. But

if I try to open the properties window from a correctly mapped

terminal services session, it takes 7-8 minutes before the window

opens, and a test page, most of the time, does not make it through.

 

I have replaced the drivers on the local machine, and the terminal

server... with no luck.. I cant see why this is running so

slowly... Does anyone have any ideas? Or perhaps a better solution?

[Guest Jiazhi Ou [MSFT]]

Re: Printing to shared local printer via Terminal Services

 

It seems that you are not using TS printer mapping instead you map the

client printers directly on the server. In that case there's a connectivity

problem between the client and the server, most likely the firewall on the

client is not opened for printer mapping. An easy check is to see if you can

browse the client printers from your server.

 

--

This posting is provided "AS IS" with no warranties, and confers no rights.

 

 

"Erimikos" <denlspe@gmail.com> wrote in message

news:1184082299.159564.45150@o61g2000hsh.googlegroups.com...

> ok.. here is our basic setup...

>

> Our network has 10 different locations, including the corporate

> office. At the corporate office, there are 2 terminal services

> servers running Windows 2000 Server, without any sort of load

> balancing. Each of our locations are running on their own subnet,

> and consist of Windows 95-XP client computers, as well as a couple

> laserjet printers. Some of these printers are connected via a

> network interface, while some are connected directly to one of the

> client computers. We also have some automated systems here (some

> using SQL, some using other custom built software) at corporate that

> print things to some of these printers.

>

> All computer work is done via terminal services. Here is a quick

> example of a printing scenario.

>

> Person A. logs into her computer, which has a shared local printer

> connected to it, then into terminal services. When connecting, she

> checks her default printer, as she is mapped to printers at all

> locations, to ensure she is connected to the correct location. She

> then starts one of our custom applications and prints an item from

> there. The system then prints out labels to 1 printer, one item from

> an server SQL on her local shared printer (using printer definition of

> \\remoteprinter\printername located in SQL), and another page from the

> program she is running to her currently selected default printer.

>

> Due to this entire process, it seems that the best option we have is

> to install printers locally on the clinic machines, and share them

> out. We then have users in terminal services sessions connect to

> those printer shares on their local machines.

>

> This seems to work fairly well for the most part, but recently we have

> been having some issues. One location in perticular, If i attempt to

> open print properties on their printer from their local machine, it

> opens almost instantally, and will print a test page perfectly. But

> if I try to open the properties window from a correctly mapped

> terminal services session, it takes 7-8 minutes before the window

> opens, and a test page, most of the time, does not make it through.

>

> I have replaced the drivers on the local machine, and the terminal

> server... with no luck.. I cant see why this is running so

> slowly... Does anyone have any ideas? Or perhaps a better solution?

>

[Guest Erimikos]

Re: Printing to shared local printer via Terminal Services

 

We are able to browse the client printers from the server without a

problem, although the connection is insanely slow (10 mins to open

printer properties page), it does work. The only firewall enabled in

the organization is the one between our network and the internet, so

this should not be an issue at all..

 

On Jul 13, 7:31 pm, "Jiazhi Ou [MSFT]" <jia...@online.microsoft.com>

wrote:

> It seems that you are not using TS printer mapping instead you map the

> client printers directly on the server. In that case there's a connectivity

> problem between the client and the server, most likely the firewall on the

> client is not opened for printer mapping. An easy check is to see if you can

> browse the client printers from your server.

>

> --

> This posting is provided "AS IS" with no warranties, and confers no rights.

>

> "Erimikos" <denl...@gmail.com> wrote in message

>

> news:1184082299.159564.45150@o61g2000hsh.googlegroups.com...

>

>

>

> > ok.. here is our basic setup...

>

> > Our network has 10 different locations, including the corporate

> > office. At the corporate office, there are 2 terminal services

> > servers running Windows 2000 Server, without any sort of load

> > balancing. Each of our locations are running on their own subnet,

> > and consist of Windows 95-XP client computers, as well as a couple

> > laserjet printers. Some of these printers are connected via a

> > network interface, while some are connected directly to one of the

> > client computers. We also have some automated systems here (some

> > using SQL, some using other custom built software) at corporate that

> > print things to some of these printers.

>

> > All computer work is done via terminal services. Here is a quick

> > example of a printing scenario.

>

> > Person A. logs into her computer, which has a shared local printer

> > connected to it, then into terminal services. When connecting, she

> > checks her default printer, as she is mapped to printers at all

> > locations, to ensure she is connected to the correct location. She

> > then starts one of our custom applications and prints an item from

> > there. The system then prints out labels to 1 printer, one item from

> > an server SQL on her local shared printer (using printer definition of

> > \\remoteprinter\printername located in SQL), and another page from the

> > program she is running to her currently selected default printer.

>

> > Due to this entire process, it seems that the best option we have is

> > to install printers locally on the clinic machines, and share them

> > out. We then have users in terminal services sessions connect to

> > those printer shares on their local machines.

>

> > This seems to work fairly well for the most part, but recently we have

> > been having some issues. One location in perticular, If i attempt to

> > open print properties on their printer from their local machine, it

> > opens almost instantally, and will print a test page perfectly. But

> > if I try to open the properties window from a correctly mapped

> > terminal services session, it takes 7-8 minutes before the window

> > opens, and a test page, most of the time, does not make it through.

>

> > I have replaced the drivers on the local machine, and the terminal

> > server... with no luck.. I cant see why this is running so

> > slowly... Does anyone have any ideas? Or perhaps a better solution?- Hide quoted text -

>

> - Show quoted text -

[Guest Priya Raghavan [MSFT]]

Re: Printing to shared local printer via Terminal Services

 

Hi,

 

What is the network bandwidth/latency between the TS Server and the Print

Server ?

This could be causing the slowness between the TS server and the printer.

 

As an alternative option, you can use Terminal Services Redirected Printers

on the TS Server.

This requires you to allow printer redirection on the client and the TS

Server, and print on the redirected printer from the TS Server.

Please see this link for more details on how to enable printer redirection:

On the client:

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/mstsc_print_local.mspx?mfr=true

On the server:

http://thin.msterminalservices.org/whitepapers/Windows2000/W2kTSprn.doc

 

Redirected printers would use the local driver on the server - and so, tasks

such as opening Printer Properties page etc. would be faster. The print job

however would again be limited by the network constraints between your TS

Server and the Print Server.

 

 

--

 

Thanks,

Priya.

TS Team Blogs:

http://blogs.msdn.com/ts/

 

This posting is provided "AS IS" with no warranties, and confers no rights.

 

 

"Erimikos" <denlspe@gmail.com> wrote in message

news:1184382260.064999.299150@m3g2000hsh.googlegroups.com...

> We are able to browse the client printers from the server without a

> problem, although the connection is insanely slow (10 mins to open

> printer properties page), it does work. The only firewall enabled in

> the organization is the one between our network and the internet, so

> this should not be an issue at all..

>

> On Jul 13, 7:31 pm, "Jiazhi Ou [MSFT]" <jia...@online.microsoft.com>

> wrote:

>> It seems that you are not using TS printer mapping instead you map the

>> client printers directly on the server. In that case there's a

>> connectivity

>> problem between the client and the server, most likely the firewall on

>> the

>> client is not opened for printer mapping. An easy check is to see if you

>> can

>> browse the client printers from your server.

>>

>> --

>> This posting is provided "AS IS" with no warranties, and confers no

>> rights.

>>

>> "Erimikos" <denl...@gmail.com> wrote in message

>>

>> news:1184082299.159564.45150@o61g2000hsh.googlegroups.com...

>>

>>

>>

>> > ok.. here is our basic setup...

>>

>> > Our network has 10 different locations, including the corporate

>> > office. At the corporate office, there are 2 terminal services

>> > servers running Windows 2000 Server, without any sort of load

>> > balancing. Each of our locations are running on their own subnet,

>> > and consist of Windows 95-XP client computers, as well as a couple

>> > laserjet printers. Some of these printers are connected via a

>> > network interface, while some are connected directly to one of the

>> > client computers. We also have some automated systems here (some

>> > using SQL, some using other custom built software) at corporate that

>> > print things to some of these printers.

>>

>> > All computer work is done via terminal services. Here is a quick

>> > example of a printing scenario.

>>

>> > Person A. logs into her computer, which has a shared local printer

>> > connected to it, then into terminal services. When connecting, she

>> > checks her default printer, as she is mapped to printers at all

>> > locations, to ensure she is connected to the correct location. She

>> > then starts one of our custom applications and prints an item from

>> > there. The system then prints out labels to 1 printer, one item from

>> > an server SQL on her local shared printer (using printer definition of

>> > \\remoteprinter\printername located in SQL), and another page from the

>> > program she is running to her currently selected default printer.

>>

>> > Due to this entire process, it seems that the best option we have is

>> > to install printers locally on the clinic machines, and share them

>> > out. We then have users in terminal services sessions connect to

>> > those printer shares on their local machines.

>>

>> > This seems to work fairly well for the most part, but recently we have

>> > been having some issues. One location in perticular, If i attempt to

>> > open print properties on their printer from their local machine, it

>> > opens almost instantally, and will print a test page perfectly. But

>> > if I try to open the properties window from a correctly mapped

>> > terminal services session, it takes 7-8 minutes before the window

>> > opens, and a test page, most of the time, does not make it through.

>>

>> > I have replaced the drivers on the local machine, and the terminal

>> > server... with no luck.. I cant see why this is running so

>> > slowly... Does anyone have any ideas? Or perhaps a better solution?-

>> > Hide quoted text -

>>

>> - Show quoted text -

>

>