On 2018-12-08 12:48, Alex McHugh wrote:
> Alex McHugh wrote:
>
>> alekz <alekz@no-mx.forums.microfocus.com> wrote:
>>> On 2018-12-06 09:21, Alex McHugh wrote:
>>> What kind of problems does the exhaustion of ports create? How do I know
>>> that I have that problem or not?
>>>

>>
>> Check with netstat and count how many ports are in TIME_WAIT state. If you
>> see a trend that these peak well over 10k (Windows) 30k (Linux) you might
>> have the issue.
>>
>> On Windows, there will be an event log that pops up (not always though)
>> warning that it has started forcibly recycling ports due to exhaustion.
>>
>> Event ID 4231 is the event to look for if I recall correctly.
>>

>
> Actually just checked my notes, it is event ID 4227 (in the system log) that
> hinted at this problem.
>
> On windows - you can see how large a range is allocated for dynamic ports on
> your windows system via this command
> netsh int ipv4 show dynamicport tcp
>
> On your eDir box, you should compare the number of established and waiting to
> close ports connecting to port 524.
>
> If you observe these numbers occasionally peak at a combined total that
> approaches the dynamic port range, then you might see the problem.
>

Thanks Alex, that's the sort of information that should be in the
release notes!

--
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.