Happened again tonight at 7:10 PM. This time I only rebooted one of the
cluster servers and it did the trick. It must be something to do with NLB
or sockets or something...
I don't know where to go. Nothing is logged anywhere.
Logged a call with Microsoft. After some Netstat analysis they have
suggested increasing the number of ports (MaxUserPorts) and the
TcpTimedWaitDelay registry settings on the two NLB servers. Apparently
they're nearing the default of 5000 so possibly out of ports.
> Happened again tonight at 7:10 PM. This time I only rebooted one of the
> cluster servers and it did the trick. It must be something to do with NLB
[quoted text clipped - 34 lines]
>>
>> Mike
Bob Barrows - 03 Jun 2009 15:08 GMT
Good to know - thanks for the update.
It will be interesting to hear if this works for you. I've not run into
the problem myself, but I'm sure it could crop up someday.
> Logged a call with Microsoft. After some Netstat analysis they have
> suggested increasing the number of ports (MaxUserPorts) and the
[quoted text clipped - 43 lines]
>>>
>>> Mike

Signature
HTH,
Bob Barrows
Mike Wazowski - 08 Jun 2009 19:54 GMT
Yes, well it's Monday and we're past the previous times of failure so
fingers crossed. The two webservers in the NLB cluster have been putting
out between 35 and 40 Mbps each for most of the day so it's looking good so
far. Incoming is about 10Mbps but of course that's duplicated to both
servers.
> Good to know - thanks for the update.
>
[quoted text clipped - 48 lines]
>>>>
>>>> Mike