Windows 2000 NLS Problem

[Moonark]

I just purchased 4 Dell PowerEdge 2500 systems for work to run a cluster of terminal servers. I can ping the entire cluster and each machine seperately. I am just going to use NLS to balance the load between the servers. I have a rule set up to allow TCP port 3389 for the load, and each machine will take 25% of the total load. Here is the problem. I connected to terminal server cluster with 5 different machines at the same time. They do not seem to roll over to the other servers to balance the load. Everything takes place on the first node which kinda defeats the purpose of NLS. Is there a way that I know everything will roll over and distribute properly? I am using single affinity on each machine because Class C for what I am doing is not needed at this point. Are there some other settings that I need to mess with? When I run wlbs.exe query 192.168.1.24 I can see all the servers in the cluster. Also I can stop and restart the cluster using wlbs as well. There are entries for each machine in my DNS as well as an entry for the entire cluster. Am I doing something wrong, or will windows, when it reaches a certain CPU level, roll over to the next machine? Also using NLS if a machine fails within the cluster and there are users in Terminal Server will they be redirected to another machine or no? And if they are redirected, will they have to log back in or will the same programs that they had open on one machine be opened on another? I know with the actual clustering service this can happen but Terminal Services application mode is not supported within the clustering service.