TCP/IP Printing through firewall

[Claude Leduc]

External offices request printing jobs locally on the HP UX server and thos jobs have to be printed on remote external systems through ip addresses... The UX server has full access to the outside through the firewall...When a print job is created, the server doesn't print when the firewall is up, but does when the firewall is down...

[Uday_S_Ankolekar]

Hello,

Just a thought:

I would check some of your firewall rules for the protocol authentcation.
May be you need to check telnet protocol rule.
and also see if there is any rule that can be set for LP jobs.

Goodluck,
-USA..

[Jay Cantwell]

Claude..check the port the HP is using to do
print services (usually 515) then check the
firewall and make sure you have a rule in for the print services going to the print servers...

[Sridhar Bhaskarla]

Most of the printers operate at standard tcp port 515. You can probably enable this port in your firewall and see if it works.

-Sri

[Roger Baptiste]

Fire a printout and let the network folks
monitor the firewall to see what port requests
are getting in. That's the quickest way
to sort this out. Last week, i had a similar
issue in pushing Omniagent across the firewall
with the R* ports open, but it didn't work.
Turned out that the "echo" port also needed
to be open, since omni sends a echo to the
agent before starting to push the software.

-Raj

[Claude Leduc]

Thank you everyone... I'll try out those hitns you mentioned about port 515 and also about network monitoring... I'll let you know later this evening...

[Eddy Chan_1]

I also have this problem on Red-hat iptables firewall that can't accpet printing service from remote site, Anyone can know which others echo ports need? I wonder my firewall have problem to allow some tcp packet of printing go through....

Pls help me