We are experiencing issues where a temporary loss of a PC’s network connection stops printing processes even once the network connection is restored. The only solution is to restart the client. However there are no errors - the print jobs just sit in the active list in System Monitor, and the user may not even be aware of the blip in their network connection. This has a knock on effect on downstream processes that may be reliant on the printed document. Does anyone have a suggestion on how this could be overcome? Is there a way to automatically re-start printing processes periodically? Appreciate any input.
1 Like
What binding are you using? (Windows or https?) https is FAR more resilient to network issues.
1 Like