On Fri, 2006-04-28 at 11:38 +0000, Barry Samuels wrote:
The traceroute problem mentioned in the previous post was caused by the firewall which has now been updated.
Traceroute lists computer A as line 1 then the printer as line 2.
Computer B still won't send the print job though.
Still sounds very much like a firewally thing to me.
Out of interest are you able to access the Jetdirect web admin page from Computer B ?
You could also try opening a telnet session to the printers port (9100 I think)
Try telnet printeraddress 9100
It won't do anything useful of course (unless you can speak Jetdirect IP protocol) but it will either fail to connect if it's a firewall issue or either print garbage on the screen or just sit there blank if it's ok. Compare this to the results you get if you do the same thing on Computer A