Our forums are currently in maintenance mode and the ability to post is disabled. We will be back up and running as soon as possible. Thanks for your patience!

General discussion


Cannot connect to server port after TCP connections go to CLOSE_WAIT state

By rollythegoalie ·
I have a situation in which a file server associated with a CAD data management system (Pro/INTRALINK) becomes unavailable for use. All of the services required for running the data management system are up and running when the system becomes unavailable for use. However all of the TCP connections on the file server associated with the data management system enter into a CLOSE_WAIT TCP state and at this point the data management system becomes unavailable for use. I've read about increasing the number of ephemeral TCP ports to more than the default 5000 allowed in order to improve data retrieval times. I've also read that when there are no more ephemeral ports available, the server stops responding and cannot accept any new requests. However, I have done testing in which I've checked out 12,000 object CAD assemblies without causing the data management system to become unavailable for use. Has anyone ever experienced a similar situation and if you have, how did you resolve the issue? Your feedback would be greatly appreciated.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

We have a similar issue

by suttonc In reply to Cannot connect to server ...

the nfsserv.exe process is maxing out at 100%. Did you end up reolving the issue

Related Discussions

Related Forums