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