Hi,
Recently I have discoved the Get-NetTCPConnection cmdlet while investigating an tcp port exhaustion issue we are having for one of our customer and it displayed a socket state that I have never seen before, the "Bound" state.
I cannot find a lot of information about it on the Microsoft website unfortunately and would like to get more information from this website if possible.
It seems that this particular state is not covered by the "TcpTimedWaitDelay" as they always seems to be alive and never close.
When running the cmdlet, I see a lot of bound state for the IIS worker process. It display a bit like this :
:: 65072 :: 0 Bound 2452 w3wp
:: 65074 :: 0 Bound 2452 w3wp
:: 65075 :: 0 Bound 2452 w3wp
:: 65125 :: 0 Bound 2452 w3wp
:: 65130 :: 0 Bound 2452 w3wp
:: 65184 :: 0 Bound 2452 w3wp
:: 65189 :: 0 Bound 2452 w3wp
:: 65194 :: 0 Bound 2452 w3wp
:: 65195 :: 0 Bound 2452 w3wp
:: 65290 :: 0 Bound 2452 w3wp
:: 65293 :: 0 Bound 2452 w3wp
:: 65295 :: 0 Bound 2452 w3wp
:: 65296 :: 0 Bound 2452 w3wp
:: 65378 :: 0 Bound 2452 w3wp
:: 65379 :: 0 Bound 2452 w3wp
:: 65380 :: 0 Bound 2452 w3wp
:: 65427 :: 0 Bound 2452 w3wp
:: 65428 :: 0 Bound 2452 w3wp
:: 65429 :: 0 Bound 2452 w3wp
:: 65430 :: 0 Bound 2452 w3wp
:: 65528 :: 0 Bound 2452 w3wp
:: 65529 :: 0 Bound 2452 w3wp
:: 65532 :: 0 Bound 2452 w3wp
Is this particular state can cause a port exhaustion issue ? Why do they always increment ?
Thanks