smbclient not in YAST services (network or otherwise)

[dungareez]

I am a newbie to linux and have set up a small home network consisting of several XP machines and my single suse 10.1 machine. I have my samba inoperability fully functional (can see and be seen by all computers in network) when the firewall is off. However the linux machine can not see the XP computers when firewall is on. Here is the problem, I cannot allow smbclient service in the firewall via YAST2 because the smbclient does not show up in the "services to allow" list on the firewall configuration allowed services page (samba server is there and has been allowed). It also does not show up in the network services (samba server does though), but in the software management it shows as installed. I would really like to be able to allow the smbclient service access through the firewall so I do not have to shut it down all the time. Also, I am curious why the smbclient is not showing up in the YAST2 areas I mentioned..

Any help would be very appreciated.

Thanks

[unchiujar]

I'm not sure if this is correct (I never used Suse) but maybe you should look into the firewall settings using iptables if the GUI manager doesn't help you.

http://www.linuxguruz.com/iptables/h...les-HOWTO.html

You'll probably just have to set a rule to allow Samba.
Have fun reading

[gogalthorp]

I've seen the same here Samba client only works if you turn the firewall off. I suspect a bug in the configuration of the firewall in 10.1

[dungareez]

Thanks unchiujar, I have been looking into manually configuring the firewall settings. To tell you the truth it makes my head hurt as I read add chain [what?] insert into kernal [huh?], and It think, what is the protocol [ouch] that I need to forward in the newchain to make sambaclient work.

This stuff is interesting and I will probably get there, but for now I will be turning off the firewall as the easier solution. Thanks for the link though, I will read up on it.

[unchiujar]

Well, it's not easy (I know because I tried setting up a router once) but after you understand how it works you would actually know what your computer does instead of praying that it works ( /me looks at windows users ).
Have fun reading

[unchiujar]

I don't think its good to have your firewall down all the time (being naked is baad )...

By the way, after a quick google I found out samba uses ports 135, 137,138,139 and 445 for both tcp and udp , so probably you'll have to set an allow rule for these ports.
can you post your iptables rules ?

as root
/sbin/iptables -L

Rules : (don't know if it works)

iptables -I INPUT 1 -p tcp udp --dport 135 137 138 139 445 -j ACCEPT
iptables -I OUTPUT 1 -p tcp udp --sport 135 137 138 139 445 -j ACCEPT

What it does (theoretically - someone correct me I'm not an expert at this)
Inserts (-I) INTPUT/OUTPUT ACCEPT rule in the first chain (1) at the first position with the protocols (-p) and source (-sport) and destination (-dports) ports specified.
It's inserted as the first because the order is important, I think first rules are considerd before last rules .

[dungareez]

Well I must say this information kind of links together a few of the pieces. Thanks alot unchiujar. I never was going to have the firewall down for any extended period, and definitely not by default, but rather on an as needed basis. I am also behind a router which helps considerably.

As far as my liptable rules (I did look at them earlier but I think my brain had given up on me) are concerned I will most definitely look into them tomorrow (I have now [cough, cough] switched back to my Xp machine and have the linux one offline as I sit here with my massaging chair working out the kinks I developed going through the Sambaclient crap, as well as simultaneously trying to configure a moodle site that will easily move between domains without corrupting links.

Tomorrow...tomorrow. I will look much closer into this tomorrow and probably be able to post the tables. Thanks again, the help is much appreciated.