Samba workgroup

madivad · 03-18-2008, 11:52 PM

I have been having trouble getting my Samba server (on open solaris) to be seen on my local home network workgroup. Here are the lines of my smb.conf file:

Code:

[global]
# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
   workgroup = INNER

# server string is the equivalent of the NT Description field
   server string = RAIDBox

# Security mode. Defines in which mode Samba will operate. Possible 
# values are share, user, server, domain and ads. Most people will want 
# user level security. See the Samba-HOWTO-Collection for details.
   security = user

# This one is useful for people to share files
[SolaRaidZ]
   comment = RAIDZ
   path = /solaraid
   writable = yes
   browsable = yes

My network is running on Smoothwall 3.0, the PC's are all on the green network, IP addresses are correct and the workgroups are all set to inner. My other PCs are Windows XP Pro, Windows 2003 Server, Xandros, and Ubuntu. The server is not running any DNS or active directory on the 2003 Server.

On the other PCs the Samba server does not appear in the workgroup. But I can access it if I type the IP address in directly.

Am I missing something in my Samba config, or is there another service that needs to be activated. Anyone have any ideas?

jschiwal · 03-19-2008, 01:01 AM

Since you can access a share by entering in the IP address, is sounds like the samba services (smbd & nmbd) are running. You might want to check your firewall settings. Do you have 139 & 445 open?

You also want to use smbpasswd to create a username/password entry in the smbpasswd file. This doesn't effect browsing much but will help by possibly retaining more properties such as user & group names instead of being mapped to nobody.

If this is a publicly accessible share, make sure it's directory's permissions were created with "chmod a=rwxt" so that the permissions allow everyone to read and write to it and to set the sticky bit which will prevent one user from deleting another users file. Ownership and permissions for the other Linux users will work out better as well if they mount this share using the cifs filesystem instead of smb. They could even use getfacl and setfacl to offer more granular control on who can read edit particular files.

madivad · 03-19-2008, 01:53 AM

Nothing on the solaris box is being shared with the outside world. I don't think it's the firewall, I only mentioned it just in case someone knew of anything that may be conflicting. The firewall is between the network and the internet. The network itself has no restrictions other than OS based authentication.

Or did you mean any firewall within the solaris box? I have no idea on anything related in that way. I assumed that they would be open. How can I check?

kebabbert · 03-19-2008, 04:59 AM

In recent OpenSolaris, CIFS server is included. I know nothing about it, but it is some Samba-esque thingy? Or?

jschiwal · 03-19-2008, 06:26 AM

I meant on the solaris box. I don't know how you would check. See if there is a security & firewall config program or something similar. In Linux, the kernel uses netfilter and you enter rules using the iptables command either directly in a script that runs when you boot up, or indirectly via a GUI setup program.

You can check the ports that are open on the solaris server by using nmap on another host in the network.
From that computer also run "smbclient -L <solaris-host-name>". That will display the services being offered.

Code:

Not shown: 1689 closed ports
PORT     STATE SERVICE
22/tcp   open  ssh
111/tcp  open  rpcbind
139/tcp  open  netbios-ssn
445/tcp  open  microsoft-ds
2049/tcp open  nfs
3306/tcp open  mysql
6000/tcp open  X11

Code:

smbclient -L hpmedia
Password:
Domain=[HPMEDIA] OS=[Unix] Server=[Samba 3.0.26a-3.5-1616-SUSE-SL10.3]

        Sharename       Type      Comment
        ---------       ----      -------
        profiles        Disk      Network Profiles Service
        users           Disk      All users
        print$          Disk      Printer Drivers
        public          Disk      Public Share test
        secret$         Disk      secret share
        IPC$            IPC       IPC Service (Samba 3.0.26a-3.5-1616-SUSE-SL10.3)
        hplaser         Printer   HP Color Laserjet 3550N
Domain=[HPMEDIA] OS=[Unix] Server=[Samba 3.0.26a-3.5-1616-SUSE-SL10.3]

        Server               Comment
        ---------            -------

        Workgroup            Master
        ---------            -------
        JESNET               HPAMD64

On the server, run "testparm" to test your smb.conf file for errors.

jlliagre · 03-19-2008, 07:39 AM

Quote:

Originally Posted by kebabbert

In recent OpenSolaris, CIFS server is included. I know nothing about it, but it is some Samba-esque thingy? Or?

It is an alternative to the samba server.
http://www.opensolaris.org/os/projec...Guide/toc.html

kebabbert · 03-19-2008, 03:44 PM

Quote:

Originally Posted by jlliagre

It is an alternative to the samba server.
http://www.opensolaris.org/os/projec...Guide/toc.html

It is THE server, right? It uses Microsofts own protocol and it mimics Windows servers exactly, right? Much better than Samba, yes? Thanx for the link, I will read it. I would prefer a windows server (i.e. my OpenSolaris CIFS server) in my network, instead of Samba.

Holey Moley. I started to read but there was to much I didnt understand, AD, WINS, etc etc etc etc.

Does anyone know the basic steps for a homeuser with a 2-3 computers connecting to the ZFS raid? Can someone outline the steps, then I can read about the steps?

madivad · 03-21-2008, 03:44 AM

Code:

Interesting ports on solaris.loc (10.0.0.21):
Not shown: 1690 closed ports
PORT    STATE SERVICE
22/tcp  open  ssh
25/tcp  open  smtp
111/tcp open  rpcbind
139/tcp open  netbios-ssn
445/tcp open  microsoft-ds
587/tcp open  submission
901/tcp open  samba-swat

Nmap finished: 1 IP address (1 host up) scanned in 343.766 seconds

So the required ports are open. I also but I still can't see it on the network as being part of the workgroup

jschiwal · 03-21-2008, 04:44 AM

My smb.conf isn't that different than yours. I will select the "profile" service from my laptop and enter my password the first time to get to my home directory on my desktop and vice versa.

I also have a public service where a password isn't needed:

Code:

[global]
        workgroup = JESNET
        map to guest = Bad User
        printcap name = cups
        logon path = \\%L\profiles\.msprofile
        logon drive = P:
        logon home = \\%L\%U\.9xprofile
        wins server = eth1:192.168.1.105, eth2:192.168.1.105
        usershare allow guests = Yes
        printing = cups
        cups options = raw
        lpq command = %p
        include = /etc/samba/dhcp.conf

[profiles]
        comment = Network Profiles Service
        path = %H
        read only = No
        create mask = 0600
        directory mask = 0700
        store dos attributes = Yes

[opensuse103]
        path = /suse
        guest ok = Yes

[wildswede]
        path = /srv/samba
        guest ok = Yes

The opensuse103 service is where I have an image of my install DVD on both services.
I just created the wildswede service to test an answer to another post. The public share on my desktop hasn't been toyed with (configuration wise) as much.

Code:

[public]
        comment = Public Share test
        path = /srv/samba/public
        read only = no
        guest ok = yes
        browseable = Yes

Code:

        map to guest = Bad User

If a user doesn't enter in the right password they are mapped to the guest user.

Code:

        wins server = eth1:192.168.1.105, eth2:192.168.1.105

I opted for "wins support = Yes" on the Desktop. One of the listed interfaces is for when I use wireless, the other is a NIC. I'm not using both at the same time.

If you use "wins support = yes" and then enter your server's IP address as the WINS server in your routers WINS entry, the other computers will pick it up during the DHCP configuration. This may help with browsing.

madivad · 03-22-2008, 09:10 PM

Ok, the problem is on a roadmap of recovery.

Apparently somewhere in the infinite wisdom of the community nmbd is not started with smbd. This is confirmed by ps -ef | grep nmbd which returns only the grep line.

This is solved one of two ways (and I have chosen the more difficult way :S)

1) start nmbd (just type it and it starts). You could create a legacy start up code for it (which I should have opted for), or
2) follow the instructions here which are relatively straight forward, but have issues.

1) I am getting a duplicate entry on the "samba_multi-user-server" dependency. Not wanting to remove it, I just renamed it. That has seemed to work
2) when doing a svcs samba I get a "maintenance state"

I am working on this. Should this not be successful, I am going to revert back to the old svccfg for samba, create a legacy start for it and upgrade it to the SMF format (for which I saw the walk-around for somewhere here)
edit: a reboot and all is online

kebabbert · 03-23-2008, 03:33 PM

Ok, found good information on setting up CIFS with Solaris:
http://www.genunix.org/wiki/index.ph...s_CIFS_Service