tcp/ip printing through linux router

Hewlett-packard / 1320
December 23, 2009 at 01:34:33
Specs: CentOS
I set up an OpenVPN server in bridged mode - using tap0 - and client
both running CentOS 4.4. The VPN works perfectly, except for printing
from the client LAN - 10.1.2.x/24 to the server LAN - 10.1.1.x/24. I am
using a HP 1320n network printer with IP on the server side.
I can telnet to the printer's port 80 from anywhere in the client LAN
without a problem. However, trying to telnet to port 9100 results in a
connection refused error. If I telnet the printer's port 9100 from the
client side VPN server, it connects without a problem. My vpn iptables
rules on both sides look like this:

iptables -A INPUT -p udp --dport 1194 -j ACCEPT
iptables -A INPUT -i tun+ -j ACCEPT
iptables -A OUTPUT -o tun+ -j ACCEPT
iptables -A FORWARD -i tun+ -j ACCEPT
iptables -A FORWARD -o tun+ -j ACCEPT
iptables -A INPUT -i tap+ -j ACCEPT
iptables -A OUTPUT -o tap+ -j ACCEPT
iptables -A FORWARD -i tap+ -j ACCEPT
iptables -A FORWARD -o tap+ -j ACCEPT
iptables -A FORWARD -p 50 -j ACCEPT
iptables -A FORWARD -p 51 -j ACCEPT
iptables -t nat -A POSTROUTING -o tun0 -j MASQUERADE
iptables -t nat -A POSTROUTING -o tap0 -j MASQUERADE

No scope restrictions exists on the printer. Any ideas on how to fix this?

See More: tcp/ip printing through linux router

Report •

December 23, 2009 at 07:27:14
Even if you had everything on the same subnet, which is what I recommend, network printing with Linux & Unix, leaves a lot to be desired. I have an HP printer, which doesn't support telnet, BTW but you can open the web interface, the same as you can with the router.

Many Unix & Linux users use the cups driver for network printing. I haven't had any success with it, using FreeBSD nor Ubuntu. All the talk about Unix & Linux giving MS a run for their money, is exactly that, just talk. The open source community still hasn't provided a decent network print driver.

Try cups & please post the results, good or bad.

How do you know when a politician is lying? His mouth is moving.

Report •

December 23, 2009 at 10:26:20
You're using different subnets for the clients and the printer.
So the clients can't even ping the printer, because it's not in their subnet and there is no route set for the printer that the clients are aware of.

Report •

Related Solutions

Ask Question