Samba printer share access from different Network
Greetings, Here is the senario, I hope someone can give a bit of guidance here! ;-} I will try and explain as clearly as I can. Network layout. networkA 192.168.2.0 networkB 196.25.100.0 I have a printer on networkA @ ip 192.168.2.5 which is my laptop. (chadlap) I have another PC on networkB @ 196.25.100.120 which is a windows PC in between there is a PC running as a router called fireman with two ethernets ( eth0 192.168.2.1) and (eth1 196.25.100.151), fireman has ip_forwarding enabled and a tiny firewall script written in iptables. (default INPUT policy is to DROP, default OUTPUT is ACCEPT, default FORWARD is ACCEPT) 192.168.2.5 and 196.25.100.120 both use fireman as the default gw How would I configure the firewall with iptables to allow 196.25.100.120 to print to 192.168.2.5 ? Chadlap is configured with samba 3.0.2 and the printer sharing is tested and is working. TIA -- Chadley Wilson Redhat Certified Technician Cert Number: 603004708291270 Pinnacle Micro Manufacturers of Proline Computers ==================================== Exercise freedom, Use LINUX =====================================
On Thursday 28 October 2004 12:31, Chadley Wilson wrote:
Greetings,
Here is the senario, I hope someone can give a bit of guidance here! ;-} I will try and explain as clearly as I can.
Network layout.
networkA 192.168.2.0 networkB 196.25.100.0
I have a printer on networkA @ ip 192.168.2.5 which is my laptop. (chadlap) I have another PC on networkB @ 196.25.100.120 which is a windows PC in between there is a PC running as a router called fireman with two ethernets ( eth0 192.168.2.1) and (eth1 196.25.100.151),
fireman has ip_forwarding enabled and a tiny firewall script written in iptables. (default INPUT policy is to DROP, default OUTPUT is ACCEPT, default FORWARD is ACCEPT)
192.168.2.5 and 196.25.100.120 both use fireman as the default gw
How would I configure the firewall with iptables to allow 196.25.100.120 to print to 192.168.2.5 ?
You need to configure the routing table on "fireman" so that the packets are sent out the correct NIC. YaST2 -> Network Services -> routing Try entries like: Destination: 192.168.2.0 Gateway: 0.0.0.0 Netmask: 255.255.255.0 Device: eth0 (eth1, or whatever) Once the routing is setup each box should be able to reach the other. Jeff
On Thursday 28 October 2004 18:47, Jeffrey Laramie wrote:
On Thursday 28 October 2004 12:31, Chadley Wilson wrote:
Greetings,
Here is the senario, I hope someone can give a bit of guidance here! ;-} I will try and explain as clearly as I can.
Network layout.
networkA 192.168.2.0 networkB 196.25.100.0
I have a printer on networkA @ ip 192.168.2.5 which is my laptop. (chadlap) I have another PC on networkB @ 196.25.100.120 which is a windows PC in between there is a PC running as a router called fireman with two ethernets ( eth0 192.168.2.1) and (eth1 196.25.100.151),
fireman has ip_forwarding enabled and a tiny firewall script written in iptables. (default INPUT policy is to DROP, default OUTPUT is ACCEPT, default FORWARD is ACCEPT)
192.168.2.5 and 196.25.100.120 both use fireman as the default gw
How would I configure the firewall with iptables to allow 196.25.100.120 to print to 192.168.2.5 ?
You need to configure the routing table on "fireman" so that the packets are sent out the correct NIC.
YaST2 -> Network Services -> routing
Try entries like:
Destination: 192.168.2.0 Gateway: 0.0.0.0 Netmask: 255.255.255.0 Device: eth0 (eth1, or whatever)
Once the routing is setup each box should be able to reach the other.
Jeff
Thanks Jeff I can ping both boxes from each other, is that the same thing? -- Chadley Wilson Redhat Certified Technician Cert Number: 603004708291270 Pinnacle Micro Manufacturers of Proline Computers ==================================== Exercise freedom, Use LINUX =====================================
You need to configure the routing table on "fireman" so that the packets are sent out the correct NIC.
YaST2 -> Network Services -> routing
Try entries like:
Destination: 192.168.2.0 Gateway: 0.0.0.0 Netmask: 255.255.255.0 Device: eth0 (eth1, or whatever)
Once the routing is setup each box should be able to reach the other.
Jeff
Thanks Jeff I can ping both boxes from each other, is that the same thing?
If you can ping the boxes from each other then your routing is OK. Your firewall isn't stopping anything, so if you still have problems it's a smb configuration problem. Jeff
fireman has ip_forwarding enabled and a tiny firewall script written in iptables. (default INPUT policy is to DROP, default OUTPUT is ACCEPT, default FORWARD is ACCEPT)
This isn't related to your question, but this configuration blocks traffic from the LAN to the Host but lets all traffic destined for other machines pass through. This is OK for an internal LAN, but don't connect "fireman" to the internet with this configuration. Jeff
On Thursday 28 October 2004 18:54, Jeffrey Laramie wrote:
fireman has ip_forwarding enabled and a tiny firewall script written in iptables. (default INPUT policy is to DROP, default OUTPUT is ACCEPT, default FORWARD is ACCEPT)
This isn't related to your question, but this configuration blocks traffic from the LAN to the Host but lets all traffic destined for other machines pass through. This is OK for an internal LAN, but don't connect "fireman" to the internet with this configuration.
Jeff Fireman connects doesn't connect to the internet
-- Chadley Wilson Redhat Certified Technician Cert Number: 603004708291270 Pinnacle Micro Manufacturers of Proline Computers ==================================== Exercise freedom, Use LINUX =====================================
On Thursday, 28 October 2004 18.31, Chadley Wilson wrote:
fireman has ip_forwarding enabled and a tiny firewall script written in iptables. (default INPUT policy is to DROP, default OUTPUT is ACCEPT, default FORWARD is ACCEPT)
192.168.2.5 and 196.25.100.120 both use fireman as the default gw
How would I configure the firewall with iptables to allow 196.25.100.120 to print to 192.168.2.5 ?
You say the two machines can connect to each other, so what is it that isn't working? Or is the question that you want to block all others and *only* allow that machine?
participants (3)
-
Anders Johansson -
Chadley Wilson -
Jeffrey Laramie