similar to: problem with starting a samba server

Hello, I've a problem with Samba version 2.0.6, where smbd does not start from inetd. nmbd starts from inetd and "smbd -D" works fine as well. And I didn't have that problem with 2.0.4b. The following is an extraction of the smb.log, which shows an "read_socket_data: recv failure for 4. Error = Invalid argument" error. Regarding this problem, what is the difference

after compile (gcc 3.0.2) install and configure (SWAT) on tcpps02 the following test failed # /usr/local/samba/bin/smbclient -L TCPPS02 added interface ip=172.16.207.7 bcast=172.16.255.255 nmask=255.255.0.0 session request to TCPPS02 failed (Call timed out: server did not respond after 20000 milliseconds) session request to *SMBSERVER failed (Call timed out: server did not respond after

Hi I need some help and am hoping you may be able to help me I have tried to install the latest 2.2.4 of samba with winbind and I am not geting anywere. This is what I have done I have installed Red Hat 7.2 cleanly on a system I have used RPM to remove all versions of samba that is installed Downloaded samba 2.2.4 extracted it then ran sh makerpms.sh created the smb.conf file with the following

thank you very much for your help...! i would be so happy if this works !!!! iv joined the domain scienceu : when i join the domain with smbpasswd, i type #./smbpasswd -j scienceu -r 11.1.9.100 -U administrateur and i have joined domain scienceu but if i type #./smbpasswd -j scienceu.org -r 11.1.9.100 -U administrateur i have the same answer here is my smb.conf : [global] workgroup

I have a FreeBSD server running Samba 2.2.7.. I've turned log levels to 10... I have a user who needs this machine to do her job, and she uses Mac OS X. She routinely cannot connect to this box, and gets an error -36. The logs show *NOTHING* when she tries to connect. The machine is properly joined to the domain, and I can reach it from Winblows. Help? Thanks, G. SMB log: [2003/06/30

(Some more info) I have a FreeBSD server running Samba 2.2.8 now (updated from 2.2.7).. I've turned log levels to 10... I have a user who needs this machine to do her job, and she uses Mac OS X, the latest 10.2 updates have been applied. She routinely cannot connect to this box, and gets an error -36, which means she needs to reboot every time she gets this. The logs show *NOTHING* when

Samba 3.0.11 on SLES8 on z/VM The system will be running fine then every few days the Winbind daemon will stop. Below are the last lines of the log file. [2005/03/03 14:15:00, 0] sam/idmap_rid.c:rid_idmap_get_id_from_sid(475) rid_idmap_get_id_from_sid: no suitable range available for sid: S-1-5-32-545 [2005/03/03 14:15:00, 0] sam/idmap_rid.c:rid_idmap_get_id_from_sid(475)

I'm continuously getting this message - it fills all of my logs... How can I fix this, or stop winbind from logging to syslog? Thanks! Nolan Jul 1 21:10:09 mgprisvr winbindd[2395]: [2006/07/01 21:10:09, 0] lib/util_sid.c:string_to_sid(285) Jul 1 21:10:09 mgprisvr winbindd[2395]: string_to_sid: Sid S-0-0 is not in a valid format. Jul 1 21:10:10 mgprisvr winbindd[2395]: [2006/07/01

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Looking at the winbind logs, I have found the following errors: Jul 7 08:00:01 desarrollo winbindd[1952]: [2006/07/07 08:00:01, 0] lib/util_sid.c:string_to_sid(285) Jul 7 08:00:01 desarrollo winbindd[1952]: [2006/07/07 08:00:01, 0] lib/util_sid.c:string_to_sid(285) Jul 7 08:00:01 desarrollo winbindd[1952]: string_to_sid: Sid S-0-0 is not in a

I was successful installing and configured Samba 2.2.5 on my first Solaris machine. However, the second Solaris machine returns errno=11 (EAGAIN ~ Service Temporary Unavailable). I have tried to delete the "locks" directory to remove possible "old" locks - upon startup the smbd create new log files, but the same errors are reported again. Why only on one of my systems - I

Hello! I posted before, figured I'd try again and provide more information in the original post. I'm running samba-3.0.22-1.fc5, joined to a W2K3 domain. All features appear to work - I've been running it this way for a month. This message appears not to actually affect anything, and it occurs every 30 seconds or so. I'll be happy to post my configs, if necessary. This set

Hello I have installed samba 2.2.6 with winbind and winbind-auth-challenge from ports. I have sucessfully added the machine to the win2k domain (still running in NT compat mode). when I try to run winbind... I get this: winbind -i -d100 winbindd version 2.2.6 started. Copyright The Samba Team 2000-2001 Initialising global parameters params.c:pm_process() - Processing configuration file

I'm running Winbind 3.0.33 with FreeRadius for windows authentication. Has anyone found a solution to these error messages in the samba.log? [root@pr01 log]# tail samba.log [2009/03/12 09:28:33, 0] lib/util_sid.c:string_to_sid(242) string_to_sid: Sid S-0-0 is not in a valid format. [2009/03/12 09:33:33, 0] lib/util_sid.c:string_to_sid(242) string_to_sid: Sid S-0-0 is not in a valid

Hey, I tried to set up samba to auth via LDAP for accessing shared home directories. However, whenever a connection is made, samba segfaults. Details follow: Machine Spec: Sun E450, 2G RAM, Solaris 9 Samba 2.2.7a ] -- all openldap-2.0.23 ] -- compiled nss_ldap-203.4 ] -- from pam_ldap-159 ] -- source Samba was compiled as follows: ./configure --prefix=/usr/local/samba --with-ldapsam

Okay, first the admisssions: I'll admit that I haven't been following the development as closely as I probably should have. And I'll admit in this case I might not be using Samba in the most efficient way possible. Also, I'm not 100% sure if I'm encountering a bug or just a seriously stupid misconfiguration issue. And I'm still collecting data on exactly what happened.

Hi list, We are mounting a PDC with samba+ldap. We are using samba2.2.5 and ldap from complanet.ath.cx/nexxus. All things go well, all tests are ok. Now we have to put our 4000 users in ldap and /etc/passwd, for this task we make an ldif file (for ldap) and two little scripts for linux passwd and samba smbpasswd set, see: script caduser: #!/bin/bash # # Adiciona usuarios for I in `<

Morning folks, Need some Help. I have a Solaris 2.5.1 system that runs Samba as simple shares but I want to attach it to an NT4 domain and use Winbind for NT authentication. But I get a broken pipe error when I run " smbpasswd -j thinktank -r testerpdc -U tester -D4". With the debug level set to 4 everything looks good until it connects to the pdc on port 445 then i get the broken

Hi, I'm going to scream. I have a "dell-installed" red hat 7.2 build and I have been attempting to get it to join my NT4.0 domain with samba... after getting past the old version of samba that shipped with it and updating to the latest samba from the samba web site, i still can't join my domain.... Here's the kicker: I CAN JOIN a test domain I set up a few weeks ago, NT4.0

Warning Really Long Message! Scenario Fresh install of Redhat 8.0 on two different servers. Samba 2.2.5-10 & Samba 2.2.7-5.8.0 Mandrake 9.0 client Samba 2.2.8a-2mdk (from Samba.org). I can not mount a share on the Mandrake client from either of the two Redhat server. I can mount shares on the wife's Windows 98 computer with out any problem. I have searched the Samba Mailing list

Hi, I want to switch from 'security = server' to 'security = ADS'. Kerberos is working and I can login to the server. With Samba 3.0.22 I was able to restrict access to shares with the 'valid users' directive. ve is local unix group. valid users = +ve And force the group ownership with the 'force group' directive. force group = +ve [foo] comment = foo