Network Load Balancing - 2003 r2 - Connection Reset Issue

[Fox1977]

Hi folks,

Apologies for cross posting. Just come across this forum. Just wondering if anyone can offer any advice to solve this problem we are having with setting up network load balacing between two win 2003 r2 standard servers.

We have two existing NLB clusters up and running behind the firewall in our datacentre. I have created the new cluster with the new IP addresses the same way as the other two servers. The cluster is set to use multicast with the port rules set to use single host.

The problem we are getting is that when any ip address is hit in the new cluster i am getting an error in the browser. In firefox i get a 'connection reset' error message. When i referesh the page a few times the page eventually loads fine. As you can appreciate it is a bit of a problem as we want to use the two servers to run as web servers. It doesnt seem to make any difference is the priorities are changed from one server to another.

I have tested the IP addresses outside of the NLB cluster and they work fine without any problems. I have rebuilt the NLB cluster several times and keep coming across the same problem.

Has anyone else come across the same problem? Any tips gratefully received. Anyone any tips on how to start trouble shoot the problem?

Thanks

 

[Fox1977]

I got this response from someone on another group and it cured the problem:
--------------------------
I'm not sure RSS is the source of problem. Anyway, pls try this.

Check your nic's Receive Side Scaling (RSS) setting.
HKLM\System\currentcontrolser\services\tcpip\parameters\
Set EnableRSS to 0.

otherwise, go to NIC's properties page, disable RSS.
--------------------------

 

[Fox1977]

Herre's the answer i managed to track down:

I'm not sure RSS is the source of problem. Anyway, pls try this.

Check your nic's Receive Side Scaling (RSS) setting.
HKLM\System\currentcontrolser\services\tcpip\parameters\
Set EnableRSS to 0.

otherwise, go to NIC's properties page, disable RSS.
-----------
Done the trick!

 

[burtsbees]

Could be an MTU issue in the router too...can you run a packet sniffer on the cluster in question?

Burt