Ik heb de technet cd er nog ff naargelopen,
En ik heb de tepel gevonden hoor,
Het is wel mogelijk , maar dan moet je load balancing in cluster form aanmaken.
Hiermee kun je op 2 verschillende netwerk kaarten binnen je domein op 1 cluster virtueel ip adress laten draaien.
tevens geef je in load balancing( eigenschappen netwerk kaart, eigen schappen tcp/ip) aan welk ip adres (host in load balancing) de netwerk adapter in je local lan heeft, hierdoor gebruikt ie voor intern verkeer gewoon het lokale ip adress en voor iis het virtuele adress in het cluster.
______________________
Load Balancing HTTP with WLBS (Q219277)
--------------------------------------------------------------------------------
The information in this article applies to:
Microsoft Windows NT Server version 4.0
Microsoft Windows NT Server, Enterprise Edition version 4.0
Microsoft Windows NT Load Balancing Service
Microsoft Windows 2000 , Advanced Server
--------------------------------------------------------------------------------
SUMMARY
This article explains how to load balance traffic to Web servers using Windows NT Load Balancing Service (WLBS).
MORE INFORMATION
To load balance traffic to Web servers, perform the following steps:
Web servers typically listen on port 80. Configure one port rule on all cluster hosts for a port range of 80 to 80 and select Both for protocols (TCP and UDP).
Click to select Multiple Hosts . Affinity should be set to None , unless the Web server maintains client state in its memory, in which case Affinity must be set to either Single or Class C .
If you want to load balance HTTP over SSL (encrypted Web traffic), you need to configure a rule for this type of traffic; usually, the port is 443. Us the following steps:
Set up a rule for a port range of 443 to 443, both TCP and UDP.
Set Affinity to either Single or Class C to ensure that the client connections are always handled by the server that has the SSL session established.
______________________________________________________
Load Balancing
A load balancer processes requests and relays them to server address clusters. A server address cluster has the following properties:
Has an FQDN in the domain namespace (for example,
www.microsoft.com)
Has a pool of valid IP addresses to computers that can fulfill the requested service that is associated with the FQDN. That is, if the FQDN is to provide Web services, each IP address must correspond to an HTTP server (for example, Internet Information Server). These IP addresses can be valid IP addresses that are assigned by Internet Assigned Numbers Authority to you, or they can be IP addresses in the private address space as defined by RFC 1918: Address Allocation for Private Internets. For example:
Class A (10.0.0.0 through 10.255.255.255)
Class B (172.16.0.0 through 172.31.255.255)
Class C (192.168.0.0 through 192.168.255.255)
Uses a load specification from a list of predetermined load formulas. (For specific details, see the documentation for your load-balancing solution.)
Optional features to be provided by the specific solution include:
A TCP port that is designated to test for a server heartbeat. These tests only verify that the server is responding on the TCP level. For example, a server heartbeat for Internet Information Server (IIS) can perform an HTTP trace request (RFC 2069, Section 9.8), which checks to verify if the programs that are requested (in this case, HTTP services) are available on the requested server.
A specification for a fail-over server in the event that all computers become unavailable.
A balance interval to determine how much time to wait between balance cycles.
http://www.microsoft.com/technet/treeview/default.asp?Url=/TechNet/prodtechnol/iis/deploy/webclust.asp
______________________________________________________
Dus ik zal het even in praktijk testen als het inderdaad ook zo werkt.
In iedergeval bedankt voor de reacties, (zaten leuke tussen)
En mocht het inderdaad werken zoals Ome Bill het zegt horen jullie het wel.
"Quote"
These IP addresses can be valid IP addresses that are assigned by Internet Assigned Numbers Authority to you, or they can be IP addresses in the private address space as defined by RFC 1918