Indy,
Sorry it took so long to get back. I did look at the smb.conf, and I couldn't find anything blatently wrong either.
Peter V.
I have been following Stormbringer's How-to set up networking since version 8.04. It has always worked a treat.
I have just installed 10.04 and followed the steps, butgets the replyCode:sudo /etc/init.d/samba stopSame forCode:sudo: /etc/init.d/samba: command not foundHas anything changed with samba under 10.04 or am I doing something wrong?Code:sudo /etc/init.d/samba start
Just look back a few posts, where mfraser states that the recommended way to restart the Samba server is now:
Code:sudo service smbd restart
Last edited by luvr; April 30th, 2010 at 12:01 PM. Reason: Oops... Had misread mfraser's post: "sudo service" is the recommended command now.
Thanks for that I had started reading from the start and gave up somewhere aound page 50. Should have persisted
Does anyone have any idea why they would change a nice obvious command like "samba xxx" to something obscure like "smbd"?
Doesn't look like much of an improvement.
It's literally been years since I had to start samba with a smbd daemon but isn't the "correct" way to restart samba this way:
sudo service smbd restart
sudo service nmbd restart
The previous "samba" daemon would start the two daemons in sequence. Now that they are separate again I think you need to restart both individually.
???? What is "nmbd" ???
As I remember it, when Red Hat created the "samba" or "smb" "service" it combined the launching of the smbd and nmbd daemons in sequence.nmbd - NetBIOS name server to provide NetBIOS over IP naming services to clients
Just found this reference in the RHEL reference:
The "smb service" combined the smbd and nmbd daemons. Now that we're going back to the olden days I think we need to run both separately in sequence.The nmbd daemon
The nmbd server daemon understands and replies to NetBIOS name service requests such as those produced by SMB/CIFS in Windows-based systems. These systems include Windows 95/98/ME, Windows NT, Windows 2000, Windows XP, and LanManager clients. It also participates in the browsing protocols that make up the Windows Network Neighborhood view. The default port that the server listens to for NMB traffic is UDP port 137.
The nmbd daemon is controlled by the smb service.
If you go back to jaunty and issue the following command you would get this result:
sudo service samba status
* nmbd is running
* smbd is running
If I understand correctly, the "nmbd" deamon is the NetBIOS name resolution service; whenever you want to connect to a Windows Networking server (be it a Microsoft Windows machine, or a Samba server), it will translate the NetBIOS server name into its IP address.
At least, that's my understanding, currently. I'm still trying to make sense of Windows Networking, and it is my goal to learn how to configure Samba in such a way that NetBIOS name resolution works flawlessly in a small home network (without a dedicated server machine)--just as it does between Windows machines.
Bookmarks