FC2 samba print problem

[savet]

On my office network, I have a FC2 print server running CUPS.

I have no problem printing to it over the network with Slack 9.1 or FC1.

I'm having trouble with an employee's laptop running FC2.

I am able to print if I completely open up eth0, but I'm unable to print otherwise.  I'm using Samba to print over the network.  Obviously leaving eth0 open is a bad security practice.  Does anyone have advice on how to allow printing vai smb without leaving the computer completely vulnerable?

Thanks for your input.

[skyman8081]

wait is it an all-linux shop?

samba/smb is really only meant to network windows pc/printers together.

try doing this over IPP

that might fix it.

otherwise it sounds like a problem with iptables/ipchains

you may need to add a rule to it to allow samba access

[savet]

Unfortunately, no....there are still a handfull of PCs running Windows XP/2000/98.

I should admit my experience with iptables is very limited.  I tried setting up an ipp network printer from my Slackware laptop, and when I list the server name, it can't find the host.  When I list the IP, it times out saying the server is busy.

Any thoughts?

[flap]

Surely if it's on an internal office network it doesn't matter?

[mobrien_12]

Why do you have to completely open up eth0?

Try printing and check the firewall logs.  See what ports need to be open.

[WMD]

quote:Originally posted by flap:
Surely if it's on an internal office network it doesn't matter?

Seconded...you don't need firewalls on every machine.  Just one protecting the internet connection.

[KernelPanic]

SMB and NMB require ports 137,139,445.

Run it through an SSH tunnel if you are worried about it being open. Or filter it rather than completely opening it.