Multi-honed LINUX box routing between 2 networks cannot print on both networks
We have a multi-honed LINUX box routing between 2 networks the Users on the 192.168.10.x network can access the 170.94.133.x network to run their queries and print them to the attached laser printers (192.168.10.x network). The other users specifically on the 170.94.133.x network cannot print to the laser printers on the 10.x network. When you try to send a print job to the printers the job hangs in the print queue on the LINUX box.
So it appears that the route statement is working to allow the users to access the 170.94.133.x network from the 192.168.10.x. to do their quiries.
So it appears that the route statement is working to allow the users to access the 170.94.133.x network from the 192.168.10.x. to do their quiries.
ASKER
You are correct the workstations on the 192.168.10.x network route through the LINUX box to the 170.94.133.x network to query a database using a local application and print the information on the network printers attached to the 192.168.10.x (this works)
The workstations on the 170.94.133.x network query the database and should print the information on the network printers attached to the 192.168.10.x.
I will send another comment with the IP Table information
The workstations on the 170.94.133.x network query the database and should print the information on the network printers attached to the 192.168.10.x.
I will send another comment with the IP Table information
Can you print from the linux box to 192.168.10.x?
ASKER
No When you print a test page from the LINUX box to the printer on the 10.x network it hangs in the print que
So the problem is with the linux box... I bet you cannot ping machines on 10.x either.
Check that you have a route for that network. Another possibility is a SW firewall (like firestarter), check the iptables -L output.
Check that you have a route for that network. Another possibility is a SW firewall (like firestarter), check the iptables -L output.
ASKER
Let me do some more explaining we want to print from a windows machine on the 133.x network to network printers on the 10.x network. The path from the 133.x network to the 10.x network is a
Dual-hone LINUX box routed between the two networks. We can ping the 10.x network and the 133.x network from the LINUX box. We can print from the LINUX box to the printers on the 10.x network. We just cannot print form the 133.x network to the printers on the 10.x network. It seems that if both networks are routed and working that printing on the windows machine (Print drivers loaded) on the 133.x network should see the printer and print. I am apparently missing something on the LINUX box that allows a pass through.
Dual-hone LINUX box routed between the two networks. We can ping the 10.x network and the 133.x network from the LINUX box. We can print from the LINUX box to the printers on the 10.x network. We just cannot print form the 133.x network to the printers on the 10.x network. It seems that if both networks are routed and working that printing on the windows machine (Print drivers loaded) on the 133.x network should see the printer and print. I am apparently missing something on the LINUX box that allows a pass through.
Can you please post the output of your iptables rules so I can have a look at them. Also, don't forget any NAT rules (-t nat) if you are doing it this way.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Resolved by our Network Engineer
It'd be nice to know what the problem was....
To make sure I correctly understand your requirements you need the following to occur:
192.168.10.x -> 170.94.133.x (Queries)
170.94.133.x -> 192.168.10.x (Printing)
When the users are connected to machines in the 170.94.133.x range, are they using a local application or for arguments sake sshing to these servers and then need to print?