Hi guys, I've reinstalled my debian file server - was running 4.0 and went for a clean 5.04 install.

Everything worked out well, system is running even more smoothly but I cannot connect to the shares.

I had backed up my smb.conf and put that one in place, the users are created + smbpasswd's are set.
Samba is running and yesterday (day of reinstall) I was able to connect without any problem but today I get a message.

Smbstatus shows that there has been a connection, the username is listed in /etc/passwd and I entered the password once again but no difference.

At first, I thought there was a problem with file/directory permissions but I have restored the data with rsync so those permissions are like before.

I have read quite some about setting up/configuring Samba and I guess it must have something to do with credentials but no clue to where to look anymore.

Any help is highly appreciated!
Peter

What do the samba logs say?

1 members found this post helpful.

Hi zordrak,

Since I was out of options, I did a test in vmware and with the original smb.conf I could read the default shared homedrive. Then only changed the read only option to no and I can write as well.

When I put back the original smb.conf on my physical machine, the nmbd deamon didn't start properly so I rebooted the machine.
Right now I'm stuck with the checking of the file system which takes like forever. This was one of the reasons for reinstalling so I could partition since I thought that those long file systems checks were because of having everything in 1 partition.

Do you know if something has changed in the newest versions of Samba that could cause a problem with my own, very minimalistic smb.conf that was ok before? I cannot access it right now but it has a global section with the users, description, user acces option, writeable setting and 2 shares with path, valid users & comment.

TIA
P.

What do the samba logs say?

They will help.

System is still doing this file system check...

There seem to be multiple samba log files, which one is the one to look at?

You should look at the logs for the machine you are testing from as well as the syslog/messages for the machine itself where the primary daemon process will log what it's doing.