Samba share and Canon Push

Updated Oct 22 2002

Samba share and Canon Send
Samba 2.2.4 and the iR5000i
Results of basic testing by that Rick guy.

First I believe that the basic samba setup acts as a win98 box in terms of authentication and share levels. If this is the case then we can only use "security = share" (see page 4-20 of the iR5000i network guide). Using this I have been able to send to an open share and a closed share.

Does anyone know how to make samba ask for a user name and password before you can see the available shares? If we got that working then we could use security = user|server. I have captured the communications between samba and the iR5000i. The user name that the iR5000i sends out for the original connection is blank. You can’t authenticate to anything with a blank user name. This means we can’t use "security = user|server" until we get samba to force the connecting machine to ask for a user name and password for the initial connection like the newer MS OSes.

Anyway, here is how I got security = share to work.

The open share smb.conf looks like:
[global]
    workgroup = TS
    netbios name = penguin
    security = share
[share]
    comment = plubic share
    path = /home/incoming
    read only = no
    public = yes

The closed share smb.conf looks like:
[global]
    workgroup = TS
    netbios name = penguin
    security = share
    encrypt passwords = yes
[share]
    comment = private share
    path = /home/incoming
    read only = no
    public = no
    valid users = ts_tech

Here is a quick rundown on each option.

[gobal] – options that apply to whole system.

workgroup = TS – we are using a workgroup called TS. This is the workgroup the server will be found under when browsing the network.

Netbios name = penguin – when browsing the network under the workgroup ts you will find a server called penguin. You can leave this option out, if you do samba will use the hostname.

Security = share – This is the share level of the samba server. Options are share, user, server.

Encrypt passwords – win9x and nt4 use encrypted passwords when you need to use passwords.

[share] – header and name of the shared resource.

Comment = xxx xxx – appears with the share name when looking at details.

Path = /path-to-share - in the open share use a+rwx, in the closed u+rwx, g-rwx, o-rwx.   learn more about chmod and chown/chgrp if you don’t understand what that says. UNIX permissions also still hold true.

Read only – read only and writeable are synonyms. Read only = no and writeable = yes mean the same thing. Use the one you want. Attribute to the share. UNIX permissions also still hold true.

Public – also useable is "guest only". If yes, open share, any one can access it (remember that UNIX permissions also still hold true). If no, closed share only a valid user can access. In the case of [homes] (a special header) only the owner of the $HOME can access it. UNIX permissions blah blah blah.

Valid users – list of users that can access the share. Don’t forget to run smbpassword locally for each user.

Home UNIX

If you find an error or wish to comment please let me know.