sarahgower
MIS
Hi,
I've changed the default route for one of our LAN printers to the router which is attached to our new datacentre via a 100mbps leased line. This is so that users who connect to the datacentre via terminal server clients can print to a printer on our local LAN. We connect to the datacentre by adding a persistent route to each machine of the router connected to the datacentre lan (xxx.xxx.xxx.254), which is not the router which is our normal default gateway (xxx.xxx.xxx.1). Both routers have a NIC on our private class C address range (the ip addresses in brackets above). This is just a temporary solution until I upgrade our local LAN to W2K and we become a child domain of the datacentre and the printers are published on AD.
The print spooler is set to WINNT\system32\spool\PRINTERS on a File/Print server on our LAN. When the printer was installed at the datacentre, I think it set the spool file to the same directory on the terminal server. Now print jobs that have been completed remain on the print queue until they are manually cleared. It's almost as if the keep printed documents check box has been ticked - except it hasn't at either location.
Is the problem caused by the dual print spool locations? Should I change the print spooler at the datacentre to our local Lan file/print server? Are windows print queues friendly representations of items in the spool directory? I'm really confused as to what the difference is between a print queue and items in the spool directory.
Please help!
Thanks!
I've changed the default route for one of our LAN printers to the router which is attached to our new datacentre via a 100mbps leased line. This is so that users who connect to the datacentre via terminal server clients can print to a printer on our local LAN. We connect to the datacentre by adding a persistent route to each machine of the router connected to the datacentre lan (xxx.xxx.xxx.254), which is not the router which is our normal default gateway (xxx.xxx.xxx.1). Both routers have a NIC on our private class C address range (the ip addresses in brackets above). This is just a temporary solution until I upgrade our local LAN to W2K and we become a child domain of the datacentre and the printers are published on AD.
The print spooler is set to WINNT\system32\spool\PRINTERS on a File/Print server on our LAN. When the printer was installed at the datacentre, I think it set the spool file to the same directory on the terminal server. Now print jobs that have been completed remain on the print queue until they are manually cleared. It's almost as if the keep printed documents check box has been ticked - except it hasn't at either location.
Is the problem caused by the dual print spool locations? Should I change the print spooler at the datacentre to our local Lan file/print server? Are windows print queues friendly representations of items in the spool directory? I'm really confused as to what the difference is between a print queue and items in the spool directory.
Please help!
Thanks!