Protocol Control messing with raw HP print to 9100

hrcrawford · 06-12-2009, 06:42 AM

Our small office uses Untangle 6.2 as a firewall/router/web filter.

Our office uses RDP to work on remotely hosted Windows servers. The common printers all print to a series of our public IP addresses that are NATed to the printers (firewall ensures only port 9100 traffic from our provider will pass).

This works great with the protocol control turned off. When I turn on protocol control, with nothing set for the printing protocol options (almost nothing set at all), printing gets gummed up. It appears that SOMEthing gets through, because the printers report "data" and "processing," but nothing is printed and the user gets a print error reported ....

UNTIL I turn the printer off and on again. Then the first print job in the queue prints. The ensuing jobs will again get "stuck."

This explicable by something I can fix? Is it a bug?

06-12-2009, 06:42 AM	#1 (permalink)
hrcrawford Newbie Join Date: Mar 2008 Location: Falls Church, VA Posts: 3	Protocol Control messing with raw HP print to 9100 Our small office uses Untangle 6.2 as a firewall/router/web filter. Our office uses RDP to work on remotely hosted Windows servers. The common printers all print to a series of our public IP addresses that are NATed to the printers (firewall ensures only port 9100 traffic from our provider will pass). This works great with the protocol control turned off. When I turn on protocol control, with nothing set for the printing protocol options (almost nothing set at all), printing gets gummed up. It appears that SOMEthing gets through, because the printers report "data" and "processing," but nothing is printed and the user gets a print error reported .... UNTIL I turn the printer off and on again. Then the first print job in the queue prints. The ensuing jobs will again get "stuck." This explicable by something I can fix? Is it a bug?