Samba Group...?

[NoDoze]

It got deleted cause the tutorial says:

You should see the Zimbra accounts that you just created in the list.

Next, log in to Zimbra Admin UI, click on Aliases and remove root @ tm.local alias. Then run the following on the Samba server.

smbpasswd -a root

Hmmm....

Now when I test the login with:

Now test if Samba authenticates your new user correctly. In this example I went to the shell on my Zimbra server box and ran this command (as root):

smbclient -U ubuntu2 //gregzimbra2.zimbra.com/ubuntu2

I get:

NT_STATUS_BAD_NETWORK_NAME

What does that mean!?!

Thanks!

[ArcaneMagus]

Remove the alias, not the account. You appear to have removed the entire admin@ account rather then just the root@ alias that is created on that account.

Check to make sure that the NMB daemon is running on your samba server, this is the process responsible for broadcasting and maintaining the presence of the samba server on the network.
(Probably /etc/init.d/nmb start)

[ArcaneMagus]

Actually did a bit of research and it appears that that error could be caused by a "msdfs proxy = no" line in your smb.conf file. See 0002554: "msdfs proxy = no" in smb.conf causes shares to be unavailable. - CentOS Bug Tracker

Try removing that line and see if that fixes the problem (I had originally assumed that the error meant that it couldn't find the name of the server on the network)

[NoDoze]

woops...Hmm...I'll try to recreate the admin account heh....

Yea, it's starting...

[root@mail /]# service smb restart
Shutting down SMB services:                                [  OK  ]
Shutting down NMB services:                                [  OK  ]
Starting SMB services:                                     [  OK  ]
Starting NMB services:                                     [  OK  ]

Any other ideas...?

[NoDoze]

Hmmm...I don't have that line in there:

my smb.conf file

[global]
	netbios name = email server
	server string = email server
	workgroup = domain
	os level = 33
	enable privileges = yes
	wins support =yes
	name resolve order = wins bcast hosts
	log file = /var/log/samba/log.%m
	log level = 3
	max log size = 1000
	syslog only = no
	syslog = 0
	security = user
	encrypt passwords = true
	ldap passwd sync = yes
	passdb backend = ldapsam:ldap://mail.domain.com/
	ldap admin dn = "cn=config"
	ldap suffix = dc=domain,dc=com
	ldap group suffix = ou=groups
	ldap user suffix = ou=people
	ldap machine suffix = ou=machines
	obey pam restrictions = no
	passwd program = /usr/bin/passwd %u
	passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n *password\supdated\ssuccessfully* .
	domain logons = yes
	logon path = \\mail.domain.com\%U\profile
	logon home = \\mail.domain.com\%U
	logon script = logon.cmd
	add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u
	add machine script = /usr/sbin/adduser --shell /bin/false --disabled-password --quiet --gecos "machine account" --force-badname %u
	socket options = TCP_NODELAY
	domain master = yes
	local master = yes
[netlogon]
  comment = Network Logon Service
  path = /var/lib/samba/netlogon
  guest ok = yes
  locking = no
[profiles]
  comment = Users profiles
  path = /var/lib/samba/profiles
  read only = No
[profdata]
  comment = Profile Data Share
  path = /var/lib/samba/profdata
  read only = No
  profile acls = Yes

[NoDoze]

*bump*

Still unresolved...interested in any ideas people may have to the issue...

[ArcaneMagus]

Looking at some more of the results for that error on google it looks like some other possible causes for this error are improper permissions on the share directory, or selinux blocking things.

[NoDoze]

Woops! My fault! I started going back through my conf files, and found a typo!

Works like a charm now!

Thanks for ALL the help!

Much appreciated

Thank you!

[ArcaneMagus]

Awesome, glad you got it working