Is this a Kind of TCP/IP Port Exhaustion ? , Whenever we had this issue we are rebooting server.

Issue

We have an application server and a client - Server Application which uses socket connections where port numbers of each client to server were defined in client on \driver\etc\services

Sometime we are facing the issue that the clients were unable to connect to the server application and to establish a socket connection.

During this if we run netstat -a we see too many socket connections were in established state. But in actual none of the clients were able to connect to server application and the client pc were not able to reach through ping tool.

I read the article that its kind of TCP/IP Port Exhaustion

When a client initiates a TCP/IP socket connection to a server, the client typically connects to a specific port on the server and requests that the server respond to the client over an ephemeral, or short lived, TCP or UDP port. On Windows Server 2003 and Windows XP the default range of ephemeral ports used by client applications is from 1025 through 5000. Under certain conditions it is possible that the available ports in the default range will be exhausted.

TCP/IP port exhaustion can occur on a client computer if the client computer is engaging in an unusually high number of TCIP/IP socket connections. This can occur if many client applications are initiating connections.

If all of the available ephemeral ports are allocated to client applications then the client experiences a condition known as TCP/IP port exhaustion. When TCP/IP port exhaustion occurs, client port reservations cannot be made and errors will occur in client applications that attempt to connect to a server via TCP/IP sockets.

Server Details : OS:Windows 2003 (X86). Hardware : HP Provilion

Client Details: OS: Windows XP SP2 / SP3 : Hardware: Multibrand.

Our Server application is created using C# .Net and using the port range from 31000-31150 to connect with clients.

Need your suggestion / fix how to fix this issue ,IS this can be fixed by application or by changing settings in OS.

NETSTAT -A --> Result as below

NOTE: when we see the above result , connection as established and tried to ping the host  Machine1computer.Plantfloorswitch1.Mycompany.com will not be reachable anywhere

When Pinged from a Normal PC within the Same Switch and or from a PC connected in Core Switch were not Pinging.

C:\ >ping Machine1computer.Plantfloorswitch1.Mycompany.com

Pinging Machine1computer.Plantfloorswitch1.Mycompany.com [192.168.100.75] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.100.75:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),