I have been looking at this for a couple weeks now and for the life of me cannot truly figure out what is going on.
We have large print jobs, that are setting to a printer. At times, the printer will sit paused, as it waits for the printer Labels to be changed. Some of these long pauses cause a Windows 2019 Print server to Reset the connection, but I cannot figure out why. You can see from the screen shot, the printer will go into a zero window hold, 35 mins of waiting in this example. When the printer comes back, it updates the window, and the server then ACK, and sends traffic. It than sends a RST, ACK to the printer which marks the job as printed, kills the session, without it truly finishing the job, and starts the next print job.
There is no Firewall between them, nor is it enabled on the print server.
Is there anything in a timeout of over 30 mins of zero window probes, that could cause the server to drop the connection?
Image of Wireshark https://drive.google.com/file/d/19xNz7SDHWAgWQKzygXlB635xN6SPUYwB/view
