[Samba] Re: network name no longer available

[Bevan C. Bennett]

Still looking for a solution.
Still getting the same error.
Help?

Bevan C. Bennett wrote:
> I have a samba PDC/BDC setup with a small number of W2k clients.
> Not too long ago I set up a set of new servers on fresh Fedora 1 boxes 
> using Samba 3.0.1 and migrated my LDAP to the new schema. It was all 
> working quite well until recently.
> 
> Suddenly, when I try to change permissions on a windows share (from the 
> windows box), after I give the root password, I get a message that "The 
> specified network name is no longer available" and everything fails.
> 
> I get the same message when I go into network neighborhood and try to 
> browse to either of the SAMBA boxes. Something must have gotten 
> glitched, but I'm not quite stumped as to what. I even updated to 
> 3.0.2rc1 to see if it made a difference...
> 
> The one thing that may be relevant is that I had had my primary LDAP 
> server hang for a period of time (too many open files, hopefully now 
> resolved) which made everyone somewhat upset (oddly, even the BDC which 
> is it's own ldap server).
> 
> At this point I'd greatly appreciate any suggestions or debugging advice 
> that might be offered. I'll try to stick around and offer the benefit of 
> my limited knowledge in return.
> 
> The other samba system can see everything just fine.
>  > smbclient -L skuld
> Password: <enter>
> Anonymous login successful
> 
>         Sharename      Type      Comment
>         ---------      ----      -------
>         netlogon       Disk      Network Logon Service
>         foo            Disk      Test Share
>         IPC$           IPC       IPC Service (Samba BDC)
>         ADMIN$         IPC       IPC Service (Samba BDC)
> Anonymous login successful
> 
>         Server               Comment
>         ---------            -------
>         SKULD                Samba BDC
>         VERDANDI             Samba PDC
> 
>         Workgroup            Master
>         ---------            -------
>         FULCRUM              VERDANDI
> 
> net view on the windows client lists all of the local systems, including 
> the samba servers, just fine.
> 
> The BDC is currently configured in this fashion, although this hasn't 
> really changed:
> 
> % testparm
> Load smb config files from /etc/samba/smb.conf
> Processing section "[netlogon]"
> Processing section "[foo]"
> Loaded services file OK.
> Server role: ROLE_DOMAIN_BDC
> Press enter to see a dump of your service definitions
> # Global parameters
> [global]
>         workgroup = FULCRUM
>         server string = Samba BDC
>         passdb backend = ldapsam:ldap://ldap2.internal.avlsi.com
>         lanman auth = No
>         log file = /var/log/samba/%m.log
>         max log size = 50
>         name resolve order = wins host bcast
>         time server = Yes
>         server signing = auto
>         logon script = logon.cmd
>         logon path =
>         domain logons = Yes
>         local master = No
>         domain master = No
>         wins server = 10.0.80.13
>         ldap suffix = dc=internal,dc=avlsi,dc=com
>         ldap machine suffix = ou=computers
>         ldap user suffix = ou=people
>         ldap group suffix = ou=groups
>         ldap idmap suffix = ou=idmap
>         ldap admin dn = "cn=Manager,dc=internal,dc=avlsi,dc=com"
>         ldap ssl = start tls
>         ldap passwd sync = Yes
>         idmap backend = ldap:ldap://ldap2.internal.avlsi.com
>         idmap uid = 40000-50000
>         idmap gid = 40000-50000
>         hosts allow = 10.0., 127.
> 
> [netlogon]
>         comment = Network Logon Service
>         path = /var/lib/samba/netlogon
>         write list = Administrator
> 
> [foo]
>         comment = Test Share
>         path = /usr/add/foo
> 
>