🚀 go-pugleaf

Graham wrote:

>I think we need nore details. If you are using terminal services, 
>presumably this is running on a server?

Sorry it's a bit of a red herring really. I'm trying to solve a slow 
terminal server printing problem. But I'm trying to minimise the amount of 
data that's sent across the network (as a start) So I'm investigating 
printing locally. In fact all 'my' local printers are all connected by ip 
address. So they spool on my machine.
>What is the printer connected to?  Conventionally it would be connected to 
>the server.

That would be lnot very useful. Terminal services are often connected to 
over a vpn in which case, you obviously want your locally connected printer 
to print. Alternatively you may connect from another domain where you don't 
want to print to the terminal servers printers directly installed on the 
server. Alternatively you may connect via a cirtix server (though this is 
rather different, you still usually want to be able to print locally)

>Nothing whatever to do with printing passes over the terminal services 
>connection.

In fact,  in the cases mentioned above the raw data is sent at least three 
times over the network, so it's essential (I think) to minimise the amount. 
Although (of course) the print job is spooled on the terminal/citrix server 
first.