On Thu August 27 2009 09:26 am, manchette fr wrote:
> After i apply Swerdna’s command lines i still can’t start nmb from Yast
> gui , it still returns 7 (not started)
> here’s what it gives from console :
> ~> sudo /etc/init.d/nmb stop
> root’s password:
> Shutting down Samba NMB daemon Warning: daemon not running.
> fabrice@opensuse111:~> sudo /etc/init.d/smb stop
> Shutting down Samba SMB daemon Warning: daemon not running.
> fabrice@opensuse111:~> sudo rm /var/run/samba/nmbd.pid
> fabrice@opensuse111:~> sudo rm /var/run/samba/smbd.pid
> rm: ne peut enlever `/var/run/samba/smbd.pid’: Aucun fichier ou dossier
de ce type
sudo /etc/init.d/nmb start
Starting Samba NMB daemon - Warning: /var/run/samba/nmbd.pid exists.
fabrice@opensuse111:~> sudo /etc/init.d/smb start
Starting Samba SMB daemon startproc: exit status of parent of
in linux i have this :
~> smbclient -L //192.168.0.12 -Uguest%
smbclient: symbol lookup error: smbclient: undefined symbol:
in windows it tells me that it is not recognized as an internal
smbclient is strictly a “nix” command.
i changed the register of windows
here are samba rpms versions , i suspect different versions disturbing
or something like that :
~> rpm -qa | grep samba
With neither smbd or nmbd running there is no hope for Windows networking, so
it is no surprise that everything fails. This must be fixed first. From
the error in smbclient I suspect that you need to update libtalloc as well as
the ones shown above.
I’m not clear just how you updated but at this time let me suggest that you do
a manual install. First download all the rpm’s in the i586 directory(or
x86_64 if you are running X86_64 architecture) and the documents rpm in the
noarch directory. Save these in a directory that just contains these files.
In a terminal window do:
cd <path to directory containing the rpms>
rpm -Uvh *.rpm
(Do not try to force the install, if you run into dependencies they need to be
This should install all the new Samba rpms. Now try to start smb and nmb. If
Yast fails try in a terminal window:
If this fails, look in /var/log/samba/log.smbd; /var/log/samba/log.nmbd
and /var/log/messages and see if any information is provided. It may also be
necessary to clear the pid files ala Swerdna.
If you are absolutely unable to get a working copy of Samba 3.4 to work, your
only hope is to roll back to the release version and see if the registry
entries will get you going.
In any event once you have a working Samba, try the smbclient on Linux if
dolphin fails. This could be a problem with dolphin.
Just for clarity; did you disable Windows Firewall while you tested?
“We’re all in this together, I’m pulling for you.” Red Green