I'm dealing with a weird issue involving an internal web application that's hosted on a `.local` domain within our Active Directory network. When I access a user record, I can either click a green button to automatically send attachments to the default printer or an orange button to open a preview for manual printing. The catch is this: when Windows Firewall is enabled, the green button doesn't do anything—no errors, no prints. However, if I disable the firewall, it works perfectly. Regular printing from other apps isn't affected by the firewall at all. I've already removed Group Policy settings enforcing firewall rules, tried various browsers like Chrome and Edge, and allowed all traffic for both the printer and the web server. I even created highly permissive firewall rules, changed the default printer, and restarted the machines. It seems like there's something particular about how this web app initiates printing with the green button that's causing a block. What else should I consider testing or troubleshooting? Thanks for your help!
2 Answers
You might want to look into capturing network traffic with a tool like Network Monitor to see what’s happening under the hood. Make sure that you’re allowing the default dynamic port range in Windows for both TCP and UDP protocols. Also, check if there’s interaction with a print server and whether communication to it is permitted!
You might want to double-check your Group Policy settings too, they can often interfere with printing functionalities in apps. Sometimes, restrictions can come from unexpected places!
Good call! I’ll take another look at the GPO settings to see if there’s something I missed.
Thanks for the suggestion! There is no print server involved, and I've set up rules for both directions allowing all protocols. I did notice that there might be Java calls to AWS IPs when I examined the button's function—trying to figure that out but I'm struggling with the filtering in Wireshark.