views:

240

answers:

1

i am using MaxUserPort setting (with 65000 as its value) in the registry on one of my servers (windows 2003 server). this was done to enable the box to handle a certain load profile. the setting has been working fine, along with the TcpTimedWaitDelay setting set at 30.

i have setup the same settings on another windows 2003 server box, in a different environment and have been doing some load tests. when i check netstat during the load test, i see a whole bunch of connections in TIME_WAIT state and only a few connections in ESTABLISHED state.

at this point, i see connection errors from the application and this makes me wonder, if the box is really using the MaxUserPort/TcpTimedWaitDelay settings that i have in the registry.

Is it possible that the box is still using its default 5000 ports, 240 seconds wait delay values and not using the registry values?

the total number of lines in the netstat output shows about 4000 lines. if i were to consider each line corresponding to a port, i would think, it is still under 5000 and this makes me think, that the server is still operating with the 5000 port default setting. please correct me if i my assumption is incorrect.

is there some way to verify that the box is using these registry settings?

please suggest, if you have come across a situation like this, and if there is a way to troubleshoot this.

thank you.

Related discussion:

http://blogs.technet.com/tristank/archive/2008/03/11/maxuserport-what-it-is-what-it-does-when-it-s-important.aspx

http://stackoverflow.com/questions/1745862/max-outgoing-socket-connections-in-net-windows-server

http://msdn.microsoft.com/en-us/library/cc296845%28BTS.10%29.aspx

A: 

I'm seeing this same problem. I have added these registry to settings to other 2003 Server machines without any issue - ie. port exhaustion failure is alleviated. However, on this machine, the settings are being ignored. The only difference I see is that this is an x64 version and other boxes aren't.

Hope someone else has seen this and will share a solution.

spond