Hi, There are two gotchas in using SuSE's SAMBA through their crummy firewall: 1.) edit /etc/sysconfig/SuSEfirewall2 (I think that's the file) - look for the section that says "If you want to use this machine as a SAMBA server, set SAMBA = yes" - and ignore it :) In my experience this doesn't work. You have to manually include the relevant ports into the EXT_TCP EXT_UDP fields - and don't even think about separating those port numbers with commas or colons - it's _spaces_ or NOTHING! I.e. 139 445 2.) in the same file have a look in the section below where it says, "If you modify any settings in the following section, we will come round and knee-cap you" and look for the bit that mentions broadcasts. You will notice that it helpfully suggests here that you might want to allow them if you want SAMBA to work. Hmmm - thanks SuSE! This may (if you're really lucky) get things working ;) Oh and use the command `SuSEfirewall restart` to bring the firewall down and up, that saves a bit of time. Apart from this gripe - it works nicely for me. Cheers, Jon. Jan Elders wrote:
On Sunday 02 January 2005 18:44, Art Fore wrote: //cut
All I want to do is to set up one machine as a server where both my wife and I can access a common directory from our two machines.
Any suggestions on how to do this or a detailed howto for a non-networking specialist would be appreciated.
Art, Here are my SAMBA settings for a similar environment (NO printing, just file sharing) :
[global] workgroup = PRIVE interfaces = 127.0.0.1 eth1 <-- eth1 is my network interface security = share guest ok = yes guest account = jrm <-- this is my account, which I want to share
[jrm] comment = Home Directories browseable = Yes read only = No guest ok = yes <-- enables remote access without password guest account = jrm <-- gives same access rights to remote user as “jrm” path = /home/jrm <-- gives access to /home/jrm only
Good luck,