Configuration has yet to be fully verified, Kemp Support will gladly assist if your Microsoft Print Servers is not flowing as expected.
Using the Kemp Load Master it is possible to Load Balance your Microsoft Print Servers.
1.1 Document Purpose
This section details a configuration for a specific application that has been provided by a customer but has yet to be fully tested.
This specific configuration will enable your Microsoft Print Servers to be Load Balanced.
Configuration has yet to be fully verified, Kemp Support will gladly assist if Print Server traffic is not flowing as expected.
2 Configuration Required
2.1 Before you configure your Virtual Service you will need to configure the Print Servers in your cluster and configure the second print server with the same print queues, assuming two print servers.
Some Registry edits are required to allow printers to be addressed by their Netbios name and should be made on your version of windows server.
Windows Server 2008 Reg Edits
Data: PrintSerice (this is an example)
Data: Server 1 of PrintService cluster
2.1 Direct Server Return
Direct Server Return is also required for this to work correctly. Please see our guide (https://support.kemptechnologies.com/hc/en-us/articles/203861685-Configuring-DSR)
Please note in DSR guide section 3.2. "Changing Network Interface Metric" in order to have the value permanently configured, you will need to change this value using NETSH.
"NETSH INT IP Set <Interface ID> metric = 254" without quotes.
2.2 Activate NETBIOS
Since we are using a NETBIOS based service (the Load Balanced Name of the Print Service), NETBIOS should be activated on the Loopback NIC, to register the Name in the NETBIOS Name Table on the system.
2.3 Disable DNS registration
Since the loopback NIC is configured with the load balanced IP, registering in DNS would conflict with the (static) DNS Record that will be created for the Load Master.
2.4 Deactivate NETBIOS
NETBIOS must be deactivated on the LAN Adapter on each system. Failure to do so would cause a failure where only one of the load balanced servers could register the load balanced NETBIOS Name. This would result in a situation where only the system that registered the load balanced name, answers requests for the load balanced name. Rendering the other systems unusable.
2.5 Implement DNSOnWire Registry Key on Servers
The DNSOnWire Registry Key specifies if the Host tries to resolve the load balanced name via DNS. This functionality has to be deactivated.
[HKLM\SYSTEM\CurrentControlSet\Control\Print] "DnsOnWire" (REG_QWORD) Decimal = 0
3.0 Global Configuration
>No Changes Required
3.1 Virtual Service Configuration:
3.2 Virtual Services
> New Virtual Service
> Enter IP Address
> Port = * (Wild Card)
> Name = MS Print Servers
> Add New Virtual Service
3.3 Standard Options
> Disable Force L7
> Persistence = Source IP
> Persistence Time = 1 Hour
> Scheduling Method = Round Robin
> Idle Connection Timeout = 660 (Default)
3.4 Real Servers
> Checker Parameter Type = TCP
> Check Port = 135
> Add New
> Enter Real Server IP Address
> Port = *
> Forwarding Method = Direct Return
If you have successfully Load Balanced your Microsoft Print Servers environment by implementing this specific configuration, please give a thumbs up or please leave a comment on a possible alteration that was required to make it function. Thank you
This procedure is simple and efficient. I succedded to implemant it easily with 2 W2012R2 print server and a VLM-2000 184.108.40.206.
It's working almost fine but I receive a lot of error from the Kemp about "Real Server Connect ".
Apr 3 12:13:48 SrvLM01 kernel: L7: Real Server Connect failed (clientIP:63715->PrintClusterIP:*->RealServerIP:49158)L7: Real Server Connect failed (ClientIP:63716->PrintClusterIP:*->RealServerIP:49158)
And there is often a latency (<10s) from the client to open printer properties. I think it's in relation with the error.
Have you got an idea to resolve this trouble.
Thanks in advance.Best regards