After I updated my Samba to 3.5.14 on my FreeBSD box today, it stopped working. I couldn’t connect to the Samba server from my Windows clients. Initially, I thought it was the memory cache issues, and I thought the problem would be solved by rebooting both machines. Unfortunately, it didn’t work. Therefore, I accessed to the server and check the cause of the problem.
First, I found that Samba was not evening running.
ps -ax | grep smb
So I started the Samba service manually:
sudo /usr/local/etc/rc.d/samba start
And it returned me the following message:
Cannot 'start' samba. Set winbindd_enable to YES in /etc/rc.conf or use 'onestart' instead of 'start'.
Oh that was easy. All I need to do was to modify my rc.conf:
#Samba service samba_enable="YES" winbindd_enable="YES"
And then I started the Samba again:
sudo /usr/local/etc/rc.d/samba start
Yay, Samba is up and running again!
–Derrick
Our sponsors:
I don’t know whether it’s just me or if perhaps everyone else experiencing problems with your
blog. It appears like some of the written text on your posts are running off the screen.
Can somebody else please provide feedback and let me know if this is happening to
them as well? This might be a problem with my internet browser because I’ve had this happen previously.
Kudos
I need to to thanк you for thiѕ great read!! I certainly enjoyed every bit of it.
I have you book marked to check out new things you post…