Thanks for the response. In our circumstances we need to load balance the
servers and not the printers. We have two print servers supporting about
four thousand printers in several buildings. Both print servers have the
same printers (drivers and net names) configured. Our workstations are
configured to print to one or the other print servers - it's pretty random.
If one server goes down, users and the help desk are instructed add the same
printer/different server to their workstation. This is probably not the
best practice. We'd like users and the help desk to only know one print
server name. We would like two or identically configured print servers to
respond to that one printer name (load balance).
"Phillip Windell" <@.> wrote in message
news:%(E-Mail Removed)...
> You don't "load balance" print servers,...you load balance the printers
> themselves by creating "printer groups". You put several pinters in a
> group and locate them physically right by each other. The printer group
> will
> appear as a single printer. The print job will come out of any one of the
> printers depending on which printer accepted the job at that particular
> moment.
>
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
> "Jims" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> Is it possible to put a couple win 2003 print servers behind a load
>> balancer? We've experimented with this concept by creating two dns A
>> records called PrintServers.mydomain.com and assigning them the IPs of
>> the
>> two win 2003 print servers but when we try to connect to
>> PrintServers.mydomain.com we receive a "duplicate name on network error".
>> Can this be done?
>> Thanks,
>> Jim
>>
>>
>
>