This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(140.8, 9%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
I have a virtual computer running W2019. This server is hosting an application providing a server port.
On the other hand I have also ca container instance running a linux hosted client, connection to my W2019 server.
I can see this estblished and working connection on both ends (netstat is quite helpful in this situation).
For some reason the connection goes down, but I can only see that the server sit shutting thow the client connection.
So on the W2019 machine netstat is confirming, that there is no client connection to my container instance.
But inside the container instance, netstat is still showin an active connection (probably to some proxy or gateway). But this connection is not reset or shut down.
Why? I don't want to enhance the communication with some magic-keep-alive-packets on application level. Would assume, this should never happen.
Thanks for any useful hints
Bernd
This symptom looks like the TCP connection is being terminated, perhaps due to an idle timeout, but a TCP reset is not sent to the client. The TCP reset is configurable in the case of Azure Load Balancer but it's not clear what components are involved based on the info in your question.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(220.8, 77%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EB%3C/text%3E%3C/svg%3E)
Meanwhile I added a Loadbalancer (Standard) into my setup of the VM.
I configured an inbound NAT rule to route the connection to my VM.
This rule also has the checkbox "Enable TCP Reset" enabled. I thought this would change anything, but the behaviour is still the same.
Somewhen the connection from LB to VM is disconnected, but the client connection from docker container instance to the load balancer still remains established.
No Azure Load Balancer. Just an Azure Virtual Machine in private network and with a public IP on the client side an Azure Container Instance (running linux). Both parties using a TCP IP connection made with .Net Core 6 and an SslStream. This the setup of it all.