Windows Server 2003
--
Questions
--
Followers
Top Experts
I need known how to close this until connections because i can't restart this server.
i attach the details of: Â netstat -aon
LAST-ACK.TXT
Zero AI Policy
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Typically how long does it take to close the connections from LAST_ACK state?
Cheers,
rsivanandan
And i don`t known how many time to close i don`t see the connection closed, the number of LAST_ACK is incremental only.
Are you using IIS?
have you tried my recommendation?
I issue seems to be, he server is not closing sessions in an orderly time






EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
The issue what you're seeing is a TCP stack problem at the root, but it has to be known on the application as well. LAST_ACK means, after the connection is closed, the last acknowledge has not been reached the server and is the reason why you see it that way. A lot of things could cause that (for instance, if you're using load balancer, some times this might happen since the load balancer closes the connection quickly).
Cheers,
rsivanandan
Yes i tried that, because the sessions i see never died, the number is only incremental. The session timeout is 20 minutes.
rsivanandan:
I upload the images with the server info, this server have teaming with one IP, and run  one application with IIS to run CGI and Authentication and back have tomcat with application. I talk with provider but he said the problem is with the users no have logoff and close the explorer, but i see the number os sessions never decrase.
Now have 215 LAST_ACK.
I mean, connect to it from within your local LAN, watch the TCP connection on the server.
Then close the explorer and see how long it takes to close it out.
There isn't going to be a ready made and cooked solution for this, if we want to resolve this then we need to first find what is going on here.
Cheers,
rsivanandan

Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
I make a capture with WireShark but i don't see nothing out of normal. Today the problem ocurr 2 peoples in the same moment. In different vlans and different floors.
I think your recommendation is only for asp. But this case is for a CGI.
Thanks






EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
The solution if for IIS web server, not a ASP setup.
As rsivanandan mentioned, your issue is linked to sockets not closing in an orderly manner
Jfer
We test the solution with parameter in Registry but we have't good result. The problem still persist
jfer0x01:
What happend with the others users using application?.
Cheers,
rsivanandan

Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Their sessions will close in more orderly time.
Thats all
Jfer
I have an application that has a CGI called him up IIS pdmweb.exe it connects with another process called webengine.exe and this is connected to the main process domsrvr.exe. Currently it is losing the connection between the CGI and webengine.exe, we try to throw a sniffer but not pass through a plate we see no network traffic. There any way to internally monitor the communication between 2 processes?.






EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
please keep us informed
Jfer

Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Seems the code does not closed the session handlers after use.
Jfer






EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
Windows Server 2003
--
Questions
--
Followers
Top Experts
Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).