file sharing between linux and windows

[rasputinnovgorod]

I have three suse 11 computers. One of them is running as a router.
I also have three Windows-2000 computers. They all successfully attach
to the internet via a switch, thru the router.

I'd like to be able to move files to and from the Windows and Linux
machines. I presume that means having a Samba server on my
router (and samba clients on the other linux boxes)?

I've experimented and have been remarkably unsuccessful.
I'd be grateful for advice. I've already waded thru some of the manuals.

Sincerely
/blair

[linuxforever]

Well, samba is quite complex, and it isn't told in a few words!
But you have to think over a few things.

You can setup any linux computer as a samba server.
And samba server means that windows (client) computers can log-on on that computer.
But you have to setup that samba server as a master browser for those win computers.
And you have to make share folders for all windows users.
And make a userfile with all user (hostnames=computernames) plus passwords.
Then you have to decide between samba security settings.
They are security is: share, user, server, domain.

There is a samba configuration file smb.conf and in this all settings are set.
So this file determines the behaviour of the samba server.
But you cannot set all files of a windows computer to be readable or writable.
You also have to share files or folders on the windows computers for other defined users.

For sharing files and folders on linux machines you should use a NFS server.
And here you have the same settings as on a samba server.

So in the end, it is no simple thing.
But I assume you have already discovered this.
Also remember that samba and nfs is for your local network.
And a router is a gateway to the external network called internet.

[gogalthorp]

I always found this link to be helpful in setting up samba

Samba and Suse: HowTo Set up an openSUSE-Windows Home Office LAN/Network. Versions 11.x

[linuxforever]

But both for samba and your local network it is advisable to use fixed IP-addresses.
And both for the linux and windows computers.
Also use hosts files for both of them.
These contain lists of the IP-addresses and the host/computernames.
It makes it much easier and overseeable.

A nice advise for samba has already been given.
But the big samba site is of course the root of all.
With also a lot of docs and howto's.

Samba - opening windows to a wider world

[linuxforever]

Anyway, I had to add the following entries in the [global] settings of smb.conf.

os level = 65
wins support = Yes
local master = Yes
preferred master = Yes
domain master = No

You also have to add users to the samba encrypted password file.
smbpasswd -a username

And that user must exist with username in the username/password file and have his home folder.

[rasputinnovgorod]

Thankyou everyone for your replies. With your help I fixed
several errors and it is now working, almost....
I'm sure with more study of your references, I'll cleanup
the rest of the bugs.

Sincerely
/blair

[rcgreen]

Your Windows machines will usually "just work" if you enable
file and printer sharing, and right click each folder you want
to share, and share it. The Linux clients, most distros, will be
able to see the windows shares and access them.

In order to share folders from your Linux machines, you must
install the samba server.

I have an absolutely no frills, bare bones /etc/samba/smb.conf
configuration file, with no security or other complications.

[global]
   
   workgroup = home

   netbios name = blue

   server string = blue

   security = share

   browseable = yes

   hosts allow = 192.168.1. 127.

   name resolve order = lmhosts wins bcast host

   wins server = 192.168.1.102   

   veto files = /*lost+found*/

[share1]

   path = /home/rcgreen/share

   comment = testfiles

   read only = No

   guest ok = Yes

   force user = rcgreen

   force group = rcgreen

[extra]

   path = /home/rcgreen/archive

   comment = bigdrive

   read only = No

   guest ok = Yes

   create mask = 0666

   force user = rcgreen

   force group = rcgreen

I have a dns server to help my computers resolve names,
but without that, you should have an /etc/hosts
file.

127.0.0.1    localhost
192.168.1.103	stacy
192.168.1.106	ocean
192.168.1.101	kirby
192.168.1.104	blue
192.168.1.102	shelly
192.168.1.100	lisa

and /etc/samba/LMHOSTS

192.168.1.103	stacy
192.168.1.106	ocean
192.168.1.101	kirby
192.168.1.104	blue
192.168.1.102	shelly
192.168.1.100	lisa

I am superstitious. I thought my system didn't act right until
I named LMHOSTS in all caps. YMMV

I designated one of my Linux machines to be master browser
and WINS server. Its /etc/samba/smb.conf is

 workgroup = home

   netbios name = shelly

   server string = shelly

   security = share

   browseable = yes

   hosts allow = 192.168.1. 127.

   socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192

   domain master = yes

   local master = yes

   os level = 35

   wins support = yes

   name resolve order = lmhosts wins host bcast


[share]

   path = /home/rcgreen/archive

   comment = movies

   read only = No

   guest ok = Yes

   create mask = 0666

   force user = rcgreen

   force group = rcgreen

   browseable = yes

If you want to control which user has what kind of access
to which shares, things can get complicated very quickly,
but I found, for frustrated people like me, a simple config
will at least get you started.

[rasputinnovgorod]

Samba wants to open ports in my firewalls; which is fine,
because I'm not using any firewalls.

EXCEPT my router linux box has a firewall. Samba wants
to open that firewall. Wouldn't that open Samba to
the world (internet)? I chose NO; did I make the correct choice?

Sincerely
/blair

[rasputinnovgorod]

> I have a dns server to help my computers resolve names,
> but without that, you should have an /etc/hosts file.

My router has a DNS server. would it be appropriate for
it to resolve computer names? How?

Sincerely
/blair

[rcgreen]

Your dns server in probably set up as a caching server,
and already resolves names on the internet. You will have to add
zone files for your local computers.

DNS HOWTO