D
Dirk
Hi,
We are deploying a Citrix and WIN2003 based infrastructure with a
central and multiple remote sites. Only the central site will host
servers except for print servers.
A print cluster will be placed in the central site with print queues
for every print device in the enterprise. Remote locations will have
PC-class servers with print queues for the local print devices.
in this way we create a cascading mechanism for print jobs that are
generated on the central Citrix farm. The print cluster queue
(configured with local port with UNC path to remote queue) should
redirect jobs for remote sites to the appropriate remote print server
queue.
this works fine for any job that is generated on the print cluster
itself, but not an another client. A print error is generated on the
client and the job blocks the queue on the print cluster and isn't
spooled.
Any idea why client jobs are not spooled whereas local job are spooled
?
Additional question: is there a way to compress the IP traffic between
the central print cluster and the remote print servers ? I was
thinking about software compression/decompression on the NIC with
maybe a dedicated extra NIC for this traffic...
any suggestions are welcome
thanks in advance
Dirk
We are deploying a Citrix and WIN2003 based infrastructure with a
central and multiple remote sites. Only the central site will host
servers except for print servers.
A print cluster will be placed in the central site with print queues
for every print device in the enterprise. Remote locations will have
PC-class servers with print queues for the local print devices.
in this way we create a cascading mechanism for print jobs that are
generated on the central Citrix farm. The print cluster queue
(configured with local port with UNC path to remote queue) should
redirect jobs for remote sites to the appropriate remote print server
queue.
this works fine for any job that is generated on the print cluster
itself, but not an another client. A print error is generated on the
client and the job blocks the queue on the print cluster and isn't
spooled.
Any idea why client jobs are not spooled whereas local job are spooled
?
Additional question: is there a way to compress the IP traffic between
the central print cluster and the remote print servers ? I was
thinking about software compression/decompression on the NIC with
maybe a dedicated extra NIC for this traffic...
any suggestions are welcome
thanks in advance
Dirk