[Samba] Re: specified network name no more available
>> I was stung by this bug yesterday myself and although >> there are numerous references to this error message >> I haven't seen any qualified resolution of the problem. >> .. >> ... Because I think someone >> from the Samba team should shed some light on the >> topic and explain under what circumstances this >> pathological behavious can be expected. > > I think Volker fixed this post 3.0.3 (see the latest > SVN SAMBA_3_0 tree). Thanks Jerry. Awfully nice of you to let me know that it was fixed in 303. There was no response to my posting but I didn't want to pester you on this assuming it is not a very popular problem. Nice that it has been resolved. Volker normally informs us when a package is ready. I look up his site from time to time but his mail is always first post so to say. I'll install it on my SuSE 9.1/64-bit as soon as he can bake it or else grab it myself. Cheers Dragan -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Re: specified network name no more available
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 7 Apr 2004, Dragan Krnic wrote: > I was stung by this bug yesterday myself and although > there are numerous references to this error message > I haven't seen any qualified resolution of the problem. > Not that the following rant hopes to be such, but it's > a good story. > > My setup is a stable 2.2.8a production domain and an > experimental 3.0.2a-SuSE domain. The passwd backend is > still smbpasswd. I wish there were a better openLDAP > primer for Sambatistas but in view of the relative > stability of the users landscape a simple copy from > time to time was replication enough to keep things > working smoothly even though not spectacularly pretty, > until I added a Windows 2003 Server Enterprise Edition > as a member client in the 2.2.8a domain. Since then > no operation requiring any writing, attribute setting > or directory modifications in the 3.0.2a domain could > be executed. Usually a long stall would precede the > famous last words "...no more available". > > I still don't know exactly why it turned out that way > but after removing (actually completely obliterating > the said W2K3 for good measure) I deleted all those > volatile TDB's on both servers and got a new lease > on life after a reboot. Luckily I joined the W2K3 to > the domain after-hours so nobody even noticed there > was any problem. > > So why am I telling you this? Because I think someone > from the Samba team should shed some light on the > topic and explain under what circumstances this > pathological behavious can be expected. I think Volker fixed this post 3.0.3 (see the latest SVN SAMBA_3_0 tree). cheers, jerry - -- Hewlett-Packard- http://www.hp.com SAMBA Team -- http://www.samba.org GnuPG Key http://www.plainjoe.org/gpg_public.asc "...a hundred billion castaways looking for a home." --- Sting -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQFAlXCbIR7qMdg1EfYRAgWfAJ9ZTWYap0//6x7qHT+geSgaW4CwBwCcDmnC 6kT4gIz6Tux7aXGSaTSFni8= =X3Ep -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Re: specified network name no more available
I was stung by this bug yesterday myself and although there are numerous references to this error message I haven't seen any qualified resolution of the problem. Not that the following rant hopes to be such, but it's a good story. My setup is a stable 2.2.8a production domain and an experimental 3.0.2a-SuSE domain. The passwd backend is still smbpasswd. I wish there were a better openLDAP primer for Sambatistas but in view of the relative stability of the users landscape a simple copy from time to time was replication enough to keep things working smoothly even though not spectacularly pretty, until I added a Windows 2003 Server Enterprise Edition as a member client in the 2.2.8a domain. Since then no operation requiring any writing, attribute setting or directory modifications in the 3.0.2a domain could be executed. Usually a long stall would precede the famous last words "...no more available". I still don't know exactly why it turned out that way but after removing (actually completely obliterating the said W2K3 for good measure) I deleted all those volatile TDB's on both servers and got a new lease on life after a reboot. Luckily I joined the W2K3 to the domain after-hours so nobody even noticed there was any problem. So why am I telling you this? Because I think someone from the Samba team should shed some light on the topic and explain under what circumstances this pathological behavious can be expected. I did quite a bit of debugging with Samba's log levels, ethereal and filemon.exe but hard as I tried to make any sense of the data there was never any indication that anything was our of ordinary. Samba maintains that everything is hunky-dorey, no problems there. Ethereal captures inconspicuous chatter on the wire but my W2K WS reaches for the tell-tale "chord.wav" accompaniment as soon as a close on the newly created file/dir terminates successfully. Sounds like Windoze clients get utterly confused when they just see a W2K3 idly standing by, not running the show. But this is just a wild guess. Can anyone tell us what is really going on? Cheers -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
