Hi There
I have just read your problem and sounds like one that I had a while ago when I first started using LocalDirectors, but I hesitate to write because I did not want to sound like I was trying to teach to suck eggs.
Anyway, I was having the same trouble with a client who had a couple of webservers. They could not get a response from the virtual address but could get a response from both real address. In correct network layout, the LocalDirector, as it acts like a bridge, should be the only way that the requests can get to the servers that it is supposed to be load balancing. If it is not the only path to them, Load balancing will not occur. Hence, just check that the LocalDirector is in series with the servers and there are not any other connections to the switches that the server and LocalDirector connect to (unless you are using a resilient topology, but that still needs to be hidden behind the LDR). When we may these changes to the customers network, then everything worked perfectly.
Sorry if you have already tried this, but it is the most obvious reason for this behaviour that I can think of.
