A server stack is the collection of software that forms the operational infrastructure on a given machine. In a computing context, a stack is an ordered pile. A server stack is one type of solution stack — an ordered selection of software that makes it possible to complete a particular task. Like in this post about How to simulate connection timeouts – on Windows 2016 – Windows firewall? was one problem in server stack that need for a solution. Below are some tips in manage your windows server when you find problem about windows, timeout, database-connection, test, .
We have an issue with some .Net applications getting connection timeouts when doing SQL requests to Db2. The code have been updated to improve logging when such timeout occurs. But, since we are not able to reproduce the errors and they only occur in production we need to “force” timeouts.
Is it possible to configure Windows firewall on Windows 2016 to enforce timeouts for all connections to ip-adress:portnumber?
To force a timeout, you simply need to drop/discard the packet without informing the sending process via a RST flag. However, from what I know, Windows firewall does not support dropping a packet without generating a corresponding RST packet (ie: it implements a deny action rather than a drop one).
Another simple method to test an application timeout is to point it to an non-existing/filtered address. If it does not work (due to ARP timeout being faster than TCP timeout) you can try pointing it to a reserved test IPv4 address as 192.0.2.1 but, in this case and before taking this route, be sure to not sending any valuable information outside.