I have been trying for a year to get samba to work with Suse (first started with SuSE 9.0) and have had no success. Have one machine setup as a server with its default settings in Yast One machine is client, again with default setting in Yast. It does not work with the firewall on either machine even though I enabled tcp and udp ports 137, 138, 139. Without the firewall, I can browse the network and it shows groups, users, and profiles If I click on users, it asks for login and password. I put in the user and password for the server, it does not authenticate. 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
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, -- Jan Elders the Netherlands http://www.xs4all.nl/~jrme/ "Home of the Network Acronyms"
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,
Art, It should be straight forward. (1) each user must have a unix account on each machine (2) each user needs a smbpasswd on each machine (smbpasswd -a [username]) **(I usually try and keep the unix account password and smbpasswd the same) (3) set up the shares you want to share in /etc/samba/smb.conf (4) use testparm to verify the smb.conf (5) restart smb and all should work (rcsmbd) How is name resolution handled?? BIND? /etc/hosts? for your situation /etc/hosts is the simple answer. If your still having problems, post your smb.conf -- David C. Rankin, J.D., P.E. RANKIN * BERTIN, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 (936) 715-9339 fax www.rankin-bertin.com -- ----- Original Message ----- From: "Art Fore" <art.fore@comcast.net> To: <suse-linux-e@suse.com> Sent: Sunday, January 02, 2005 11:44 AM Subject: [SLE] Samba 3.09 & Suse 9.2
I have been trying for a year to get samba to work with Suse (first started with SuSE 9.0) and have had no success.
Have one machine setup as a server with its default settings in Yast One machine is client, again with default setting in Yast.
It does not work with the firewall on either machine even though I enabled tcp and udp ports 137, 138, 139.
Without the firewall, I can browse the network and it shows groups, users, and profiles
If I click on users, it asks for login and password. I put in the user and password for the server, it does not authenticate.
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
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
You're right is _should_ be straightforward, but it's surprising how many people struggle with it - and more often than not it's down to SuSE's firewall :( Not sure if it's better under 9.2 yet? I mean how difficult would it be to have a little script that opens the ports that are absolutely essential for SAMBA to work at all. Hey - it could even warn you that it was doing it.... :) Yours, A.Curmudgeon David Rankin wrote:
Art,
It should be straight forward.
(1) each user must have a unix account on each machine (2) each user needs a smbpasswd on each machine (smbpasswd -a [username]) **(I usually try and keep the unix account password and smbpasswd the same) (3) set up the shares you want to share in /etc/samba/smb.conf (4) use testparm to verify the smb.conf (5) restart smb and all should work (rcsmbd)
How is name resolution handled?? BIND? /etc/hosts? for your situation /etc/hosts is the simple answer.
If your still having problems, post your smb.conf
-- David C. Rankin, J.D., P.E. RANKIN * BERTIN, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 (936) 715-9339 fax www.rankin-bertin.com -- ----- Original Message ----- From: "Art Fore" <art.fore@comcast.net> To: <suse-linux-e@suse.com> Sent: Sunday, January 02, 2005 11:44 AM Subject: [SLE] Samba 3.09 & Suse 9.2
I have been trying for a year to get samba to work with Suse (first started with SuSE 9.0) and have had no success.
Have one machine setup as a server with its default settings in Yast One machine is client, again with default setting in Yast.
It does not work with the firewall on either machine even though I enabled tcp and udp ports 137, 138, 139.
Without the firewall, I can browse the network and it shows groups, users, and profiles
If I click on users, it asks for login and password. I put in the user and password for the server, it does not authenticate.
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
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- Jonathan Brooks (Ph.D.) Research Assistant. PaIN Group, Department of Human Anatomy & Genetics, University of Oxford, South Parks Road, Oxford, OX1 3QX tel: +44(0)1865-282654 fax: +44(0)1865-282656 web: http://www.fmrib.ox.ac.uk/~jon
participants (4)
-
Art Fore -
David Rankin -
Jan Elders -
Jonathan Brooks