Forum Discussion
print servers load balancing
Hi
I got a VS to load balance two print server. it's a fastl4 VS that works i can access the print server on port 445. the problem i have is that once i access the VIP on port 445 i click on a printer it doesn't install the printer it just pops out a error. i have open all port to the VS for testing so i'm not sure what the problem is...
4 Replies
- What_Lies_Bene1
Cirrostratus
Hey Angelo. Can you confirm the print servers have a route back to your client(s) via the F5? - uni
Altocumulus
Angelo, could you post the config for your virtual server? - Angelo
Nimbostratus
I got it working this is the config
VS configuration on F5
ltm virtual vs_bc_printing {
destination 10.237.0.1:any
ip-protocol tcp
mask 255.255.255.255
partition BRC
persist {
/Common/source_addr {
default yes
}
}
pool pool_bc_citrix_printers
profiles {
FastL4_Print { }
}
rules {
LB_logging
}
snat automap
translate-port disabled
vlans-disabled
}
In conjunction to this a loopback adapter will need to be created on the Wintel server (no reboot is required for this setup and the commands must be run to activate the adapter..)
Click Start, select Run and enter hdwwiz to start the Hardware Installation Wizard
When the Wizard has started, click Next
Select 'Install the hardware that I manually select from a list (Advanced)', click Next
Select 'Network adapters', click Next
Select 'Microsoft' & 'Microsoft Loopback Adapter', click Next
1. Right click network icon in the systray and click Network and Sharing Centre
2. Click Change adapter settings
3. Right-click the new loopback adapter and select Properties
4. Un-check all items except Internet Protocol Version 4 (TCP/IPv4)
5. Select Internet Protocol Version (TCP/IPv4), click Properties and configure the IP address to be the same as the Virtual Server (VIP), with a full subnet mask of the individual IP e.g. 255.255.255.255. Do not add a gateway.
6. Click OK on the TCP/IP popup window, then click Close on the Local Area Connection window to save the new settings For Windows 2008, its not necessary to modify the interface metric on the advanced tab and should be left set to Automatic
8. Rename the loopback "Loopback" from localareaconnection 2
9. Run the following in a command prompt:
netsh interface ipv4 set interface "Local Area Connection" weakhostreceive=enabled
netsh interface ipv4 set interface "Loopback" weakhostreceive=enabled
netsh interface ipv4 set interface "Loopback" weakhostsend=enabled
10. Now repeat the above process for all other Windows 2008 real servers - Terrence
Nimbostratus
I've seen a couple of posts similar to this regarding load balancing print servers, and they all seem to indicate that the loopback address is required in order for it to function as expected. However looking at your configuration for your virtual server you do not have "translate-address disabled", so is it actually required?
Am I completely off base here? I only ask because a colleague was looking to accomplish something similar.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com