netstat TIME_WAIT

hi...

Sparc-10, Sol 2.4, 192Mb, running SQL Server.

Here is list of connections to a database listening on port 4100. I don't have a problem with the "ESTABLISHED" connections. But what about the "TIME_WAIT" ones? Whats happening here? and why does output of....
#netstat -n | grep 194.70.47.151.4100 | wc -l
vary constantly from 70 to 110. Users log in once, then log out at the end of the day (12 at the moment).

# netstat -n
TCP
   Local Address        Remote Address    Swind Send-Q Rwind Recv-Q  State
-------------------- -------------------- ----- ------ ----- ------ -------

194.70.47.151.4100   194.70.47.151.52448   8192      0  8192      0 ESTABLISHED
194.70.47.151.54716  194.70.47.151.4100    8192      0  8192      0 ESTABLISHED
194.70.47.151.4100   194.70.47.151.54716   8192      0  8192      0 ESTABLISHED
194.70.47.151.2001   194.70.47.1.2049     17520      0  8760      0 ESTABLISHED
194.70.47.151.54939  194.70.47.151.4100    8192      0  8192      0 ESTABLISHED
194.70.47.151.4100   194.70.47.151.54939   8192      0  8192      0 ESTABLISHED
194.70.47.151.55231  194.70.47.151.4100    8192      0  8192      0 TIME_WAIT
194.70.47.151.55233  194.70.47.151.4100    8192      0  8192      0 TIME_WAIT
194.70.47.151.55235  194.70.47.151.4100    8192      0  8192      0 TIME_WAIT
194.70.47.151.55237  194.70.47.151.4100    8192      0  8192      0 TIME_WAIT
194.70.47.151.55239  194.70.47.151.4100    8192      0  8192      0 TIME_WAIT
194.70.47.151.55241  194.70.47.151.4100    8192      0  8192      0 TIME_WAIT
194.70.47.151.55243  194.70.47.151.4100    8192      0  8192      0 TIME_WAIT
194.70.47.151.55245  194.70.47.151.4100    8192      0  8192      0 TIME_WAIT
194.70.47.151.55247  194.70.47.151.4100    8192      0  8192      0 TIME_WAIT
194.70.47.151.55249  194.70.47.151.4100    8192      0  8192      0 TIME_WAIT
194.70.47.151.55251  194.70.47.151.4100    8192      0  8192      0 TIME_WAIT
194.70.47.151.55253  194.70.47.151.4100    8192      0  8192      0 TIME_WAIT
194.70.47.151.55255  194.70.47.151.4100    8192      0  8192      0 TIME_WAIT
194.70.47.151.55257  194.70.47.151.4100    8192      0  8192      0 TIME_WAIT
194.70.47.151.55259  194.70.47.151.4100    8192      0  8192      0 TIME_WAIT


regards
LVL 3
rickyrAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ahoffmannCommented:
does man netstat not give the answer?
0
rickyrAuthor Commented:
Sort of!!!!

TIME_WAIT - Wait after close for remote shutdown retransmission.

It doesn't make much sense to me, There are no remote shutdowns.
Anyway what is a remote shutdown retransmission when it's at home. I really need a detailed explanation of whats going on here. The network connections vary wildly but the users on the system are constant
0
rjhowardCommented:
Found this article in our Knowledge Base.  Hope it helps.

Question:
     Sun Solaris: Why do ports get stuck in the TIME_WAIT state?

     Configuration Data:


     Answer:
     This is due to the 2MSL timeout value, which is a part of the TCP specification. After a connection has been closed by
     both the client and the server, the port becomes unavailable for a certain amount of time, so that a new program does not
     inadvertently get packets that were intended for the old program. On Solaris machines, the 2MSL value may be modified
     by adjusting the /dev/tcp tcp_close_wait_interval ndd variable. (ndd -set /dev/tcp tcp_close_wait_interval value.)

     Q: Why do I get "address already in use" when I try and reuse a port which a previous program had used.

     A1: It could be that the port is still in the TIME_WAIT state (see above). You may confirm this by running netstat, and
     examining the port in question. If this is the case, you must simply wait the couple of minutes it will take for the port to get
     out of the TIME_WAIT state.

     A2: It could be that the program you are using does not correctly list the port as one that may be reused. You should
     verify that your program is setting the SO_REUSEADDR socket option.

     References to Procedures:


     Additional Information/Comments:
     For additional information on how to use ndd to change TCP parameters, do man ndd. Under Solaris 2.5 or higher, you
     will need to be root to display network configuration values using ndd.The above information is from Sun Technical
     support. SO#: 3165922 - TCP Questions
     Product Support Document (PSD) for Sockets Programming Including Sockets Programming
     Revision 1.3
     Date: April 9, 1996
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
rickyrAuthor Commented:
Hello rj....
Thanks for that detailed answer. It makes alot of sense to me
as The users that log in do not send/receive anything for long periods of time while they are doing other tasks, this could explain the time-outs you talk about, along with the rest of the info you supplied, This is a good starting point for more investigation.

Thanks again

ricky
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Networking

From novice to tech pro — start learning today.