Bonjour, Mon serveur Samba 2.2.1a (sur Suse 7.3 PPC) a quelques soucis depuis 2/3 jours. Le dernier en date : les utilisateurs sont authentifi?s mais le lecteur ne se connecte pas correctement dans le script (si on ouvre le lecteur concern? il est vide). L'architecture : 2 serveur Samba (fichiers / impression) avec 30 utilisateurs depuis 1 an plusieurs serveurs NT4 dont le contr?leur principal de domaine Clients NT4 Wstn Tous nos utilisateurs ont un script de connexion sur le serveur principal de domaine (*.bat) qui mappent les lecteurs r?seaux par utilisateur. Ce matin certains utilisateurs se connectent correctement. Les derniers utilisateurs ne peuvent pas ouvrir le lecteur r?seau du samba : il est dans la liste (ex: U:\) mais si on clique dessus il est vide (pas de contenu). Si on d?connecte ce lecteur manuellement sur le poste et on le reconnecte Ok cela fonctionne. Dans le log.smbd pour ces utilisateurs j'ai le message suivant : "Gethostbyaddr failed for adresse IP" Connaissez vous ce probl?me ? P.S. : Ce probl?me fait suite ? un pb de sessionid jeudi (nombre de connexions > 3000) qui ressemble ? un bug. La solution trouv?e : arr?t du serveur samba "rm sessionid.tdb" red?marrage du serveur samba ----------------------------------------------- Same message in English (my English is so bad) I have some trouble with my samba 2.2.1a (on Suse 7.3 PPC) since 2/3 days. This file server samba run for one year ! The last problem is a problem of connection for few users (not all). You can see on the PC (NT Wstn) the connexion (the server) but there is nothing in it (if you open/explore it) Our architecture : 2 serveurs Samba (file / printing) with about 30 users (for one year) few NT4 servers (with the PDC) PC on NT4 Wstn All ours users use a script to connect share folders and disk on servers. This morning some using are running normaly. But few others users can't open the mapped server (i.e. U\). There is nothing in it. If you disconnect this manually and after you connect it manually all is ok (You can all the files of this share folder). Users are recognised but not connected (you can't find any "active connections" on swat), active shares are ok. In log.smbd for these users with this trouble i have this message : "Gethostbyaddr failed for 1.1.1.1.0 "(ip adress) What is that ? What can i do ? P.S. : Is it a problem with a tbd corrupted ? On thuesday i had a trouble with sessionid.tdb (connexion number > 3000). I think it's the beginnig of my current problem For this problem (a collegue sayed me to do this) I stopped samba I destroyed this table I restarted samba All was ok
On Mon, 2004-03-08 at 21:38, Dominique Rouvier wrote:> Same message in English (my English is so bad)It is better than my french :-)> I have some trouble with my samba 2.2.1a (on Suse 7.3 PPC)This is a *very* old version, with known major security holes and many flaws corrected by later 2.2 and more importantly the 3.0 releases of Samba.> since 2/3 > days. This file server samba run for one year ! > The last problem is a problem of connection for few users (not all). You > can see on the PC (NT Wstn) the connexion (the server) but there is > nothing in it (if you open/explore it) > > Our architecture : > 2 serveurs Samba (file / printing) with about 30 users (for one year) > few NT4 servers (with the PDC) > PC on NT4 Wstn > > All ours users use a script to connect share folders and disk on servers. > This morning some using are running normaly. But few others users can't > open the mapped server (i.e. U\). There is nothing in it. If you > disconnect this manually and after you connect it manually all is ok > (You can all the files of this share folder). > Users are recognised but not connected (you can't find any "active > connections" on swat), active shares are ok. > > In log.smbd for these users with this trouble i have this message : > "Gethostbyaddr failed for 1.1.1.1.0 "(ip adress) > > What is that ? What can i do ?This means that your reverse DNS is not setup correctly. Later Samba 2.2 versions avoided doing reverse DNS lookups (unless configured), as most sites cannot configure this correctly.> P.S. : > Is it a problem with a tbd corrupted ? > On thuesday i had a trouble with sessionid.tdb (connexion number > > 3000). I think it's the beginnig of my current problemThis issue has been resolved in Samba 3.0, and occurs if smbd processes die without cleaning up their entries...> For this problem (a collegue sayed me to do this) > I stopped samba > I destroyed this table > I restarted samba > All was okThis is the correct solution to an 'over-full' sessionid table. This should not be nearly as much of an issue in Samba 3.0. Andrew Bartlett -- Andrew Bartlett abartlet@pcug.org.au Manager, Authentication Subsystems, Samba Team abartlet@samba.org Student Network Administrator, Hawker College abartlet@hawkerc.net http://samba.org http://build.samba.org http://hawkerc.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.samba.org/archive/samba/attachments/20040308/d835219d/attachment.bin