Install a WINS server (windows internet name server server) for the NetBIOS machines. A samba machine can do it. Windows 3+, 95, 98, Me, NT, 2000 can all use it (unlike active directory). Adjust your DHCP server or point all NetBIOS nodes to this wins server, enable h-node (just in case the wins server fails, h-node will broadcast for resolution if it can't reach the wins server) resolution, and you're set.
i use spinbox.net's "virtual spinbox" and it has been decent to us; they have a habit of upgrading their software or changing server IPs, but other than that they don't do nasty things to you.
You go to this url: Linux Virtual Server Project and download the tools neccessary to build a load balancer based on Linux. This replicates the functionality of the Cisco LocalDirector, which is your other option (pricey $8k). People will tell you that the LocalDirector blows, and compared to the $18,000 load balancers, it does, but for what it is designed to do, it does it's job well. Just as the Linux VS project.
Database servers are often the bottleneck. I think people are nuts for load balancing their web servers when it is the database servers that are most often bogged down. A 486 running PHP can saturate multiple T1s if the database back end is fast enough (I've done it).
Slashdot Mirror
you dorkuses all are trolls.
See http://www.pcpowerandcooling.com/. By far the most reliable and quietist power supplies I have ever used, and I have used a lot.
Are you a homosexual?
Install a WINS server (windows internet name server server) for the NetBIOS machines. A samba machine can do it. Windows 3+, 95, 98, Me, NT, 2000 can all use it (unlike active directory). Adjust your DHCP server or point all NetBIOS nodes to this wins server, enable h-node (just in case the wins server fails, h-node will broadcast for resolution if it can't reach the wins server) resolution, and you're set.
i use spinbox.net's "virtual spinbox" and it has been decent to us; they have a habit of upgrading their software or changing server IPs, but other than that they don't do nasty things to you.
You go to this url: Linux Virtual Server Project and download the tools neccessary to build a load balancer based on Linux. This replicates the functionality of the Cisco LocalDirector, which is your other option (pricey $8k). People will tell you that the LocalDirector blows, and compared to the $18,000 load balancers, it does, but for what it is designed to do, it does it's job well. Just as the Linux VS project.
Database servers are often the bottleneck. I think people are nuts for load balancing their web servers when it is the database servers that are most often bogged down. A 486 running PHP can saturate multiple T1s if the database back end is fast enough (I've done it).