The Samba-Bugzilla – Bug 3171
Cannot Use Samba; Cannot Repair or Upgrade
Last modified: 2005-10-24 07:01:35 UTC
In August I upgraded my Fedora installation to FC-4. As of the day of the
upgrade my Samba server does not operate. As it had worked well for over a year
prior, it must be tied to the FC-4 upgrade.
I´ve used the Samba Checklist in the HOWTO docs to troubleshoot and here are the
results. I can ping each station both ways.
smbclient -L BIGSERVER,
nmblookup -B BIGSERVER __SAMBA__
nmblookup -B ACLIENT `*'
nmblookup -d 2 `*'
all work fine. The next step, ¨net view \\BIGSERVER¨ (run from Windows PC)
fails, with an error ¨The network path was not found.¨
The documentation says to repair nmbd, but gives no guidance how to do that.
smbclient -V and nmblookup -V both report I have Samba 3.0.14a installed. I
downloaded Samba 3.0.20b (Fedora RPM) from the Samba.org site and attempted an
install. The install fails with an error message ¨newer version already
I went to add/remove applications and instructed the system to remove Samba,
which it did. Now, an attempt to install Samba 3.0.20b returns the error
¨missing component -- cannot locate ´samba-common´ 3.0.20b -- installation
cannot continue until it is found.¨
So -- Samba 3.0.14a does not work, and I cannot upgrade to Samba 3.0.20b.
Here is an update: I´ve done a lot of learning.
The Windows machine shows that BIGSERVER (your name) shows in the LMHOSTS file.
It appears there automatically. Also, the Windows machine reports that
BIGSERVER is registered as its WINS server, and gives the correct local IP
Still, however, when I try to browse the network, the Windows machine does not
report any other machines on the network.
These are configuration errors. Have you posted to the samba
mailing list ? here is no indication of a Samba soufce level bug here.