Problems with applications that listen on specific TCP ports on Win 2000

  • Thread starter Thread starter Elisabete
  • Start date Start date
E

Elisabete

Hello

We are having a problem with some of our servers running Windows 2000
Server.

The Hardware configuration is
- Dual Xeon 2.4Mhz.
- Two network cards: Intel(R) Pro/1000 MT dual port network connection

We are running applications that listen on specific TCP ports.

The problem description is as follows:

1)
Sometimes when the application performs a hard restart, the ports are
kept
by the Operating System under the process System:8, either in a state
called "CLOSE_WAIT" other times in "TIME_WAIT".
When the server applications restarts, it is unable to listen on those
same ports,
as they are occupied by the System process.
Is there any workaround for this issue?

2)
Another problem is that sometimes, some 3rd party services seem to
loose their ability to properly accept incoming
client connections. We don't know exactly what cause this situation,
but sometimes, by simple running a packet analysis tool like
SysInternal's TDIMon, causes services like VNCServer and Firebird
database server, to stop accepting client connections
(i.e. - I can't telnet to the port they were previously listening).


The main problem is that situation 2) seems to happen randomly in some
of our servers, and without using tools such as TDIMon.

Thank you

Elisabete
 
Elisabete said:
1)
Sometimes when the application performs a hard restart, the ports are
kept
by the Operating System under the process System:8, either in a state
called "CLOSE_WAIT" other times in "TIME_WAIT".
When the server applications restarts, it is unable to listen on those
same ports,
as they are occupied by the System process.
Is there any workaround for this issue?
Click to expand...

See SO_REUSEADDR on the net and in MSDN. Make sure you understand what it
does and what tradeoffs it brings before using it.
2)
Another problem is that sometimes, some 3rd party services seem to
loose their ability to properly accept incoming
client connections. We don't know exactly what cause this situation,
but sometimes, by simple running a packet analysis tool like
SysInternal's TDIMon, causes services like VNCServer and Firebird
database server, to stop accepting client connections
(i.e. - I can't telnet to the port they were previously listening).
Click to expand...

Make sure your machine is free from LSPs, adware, rootkits etc.
 
Just as additional note : that and/or SO_EXCLUSIVEADDRUSE your single
option
Arkady
 
Back
Top