K
Kevin Wallace
Hi,
One of our applications creates many local printers on
each node of a W2K cluster. By the nature of the
application these cannot be 'network printers', and hence
use the same server name, but different shared printer
names.
In the past I have used the Clustered Print Spooler to
allow these printers to be highly available to the
clients. This was done by installing TCP/IP Services i.e.
the lpd service, on each node, and creating new printers
under the Virtual Server name. These new printers each
connected to the local shared printer using a new LPR port
using the printer name and another Virtual IP address. (ie
the cluster group has two virtual IP addresses, one for
the Spooler and one for creating the LPR ports)
With W2K SP2 this worked just fine, but using SP3 this
functionality has gone away. It would seem that the LPD
service will only create print queues under the fixed IP
address(es) on the NIC and not on any of the Virtual IP
addresses created in the Cluster. (I seem to recall that
I also had a similar problem with SP1, but was fixed by
SP2, and gave no problems with our NT4.0 clusters)
Has anyone else encountered this problem? and is there a
solution?
Again these are local printers not network ones and all
use the same server name/ip address - the clients can
connect directly to them, but I would like to be able to
use the Cluster Print Spooler Virtual Server name so that
they don't need to think about which node they have to
connect to.
Any help is much appreciated.
Thanks in advance
Kevin
..
One of our applications creates many local printers on
each node of a W2K cluster. By the nature of the
application these cannot be 'network printers', and hence
use the same server name, but different shared printer
names.
In the past I have used the Clustered Print Spooler to
allow these printers to be highly available to the
clients. This was done by installing TCP/IP Services i.e.
the lpd service, on each node, and creating new printers
under the Virtual Server name. These new printers each
connected to the local shared printer using a new LPR port
using the printer name and another Virtual IP address. (ie
the cluster group has two virtual IP addresses, one for
the Spooler and one for creating the LPR ports)
With W2K SP2 this worked just fine, but using SP3 this
functionality has gone away. It would seem that the LPD
service will only create print queues under the fixed IP
address(es) on the NIC and not on any of the Virtual IP
addresses created in the Cluster. (I seem to recall that
I also had a similar problem with SP1, but was fixed by
SP2, and gave no problems with our NT4.0 clusters)
Has anyone else encountered this problem? and is there a
solution?
Again these are local printers not network ones and all
use the same server name/ip address - the clients can
connect directly to them, but I would like to be able to
use the Cluster Print Spooler Virtual Server name so that
they don't need to think about which node they have to
connect to.
Any help is much appreciated.
Thanks in advance
Kevin
..