similar to: Server signing bugs with CIFS VFS client

I'm having problems connecting from my laptop, and the logs show lib/util_sock.c:send_smb(769) Error writing 116 bytes to client. -1. (Broken pipe) : 1 Time(s) lib/util_sock.c:write_data(562) write_data: write failure in writing to client 192.168.0.91. Error Broken pipe : 1 Time(s) libsmb/smb_signing.c:srv_check_incoming_message(737) srv_check_incoming_message: BAD SIG: seq 2 wanted

Greetings, I've set up a Samba 3.0.23a PDC on Fedora Core 5 and joined a couple XP clients to the domain successfully. However, when I start using the Samba PDC's "homes" share from the XP client, I eventually get errors such as the following: [2006/08/05 03:28:07, 0] libsmb/smb_signing.c:srv_check_incoming_message(657) srv_check_incoming_message: BAD SIG: seq 798 wanted

Hello, after an update from Samba 2.2.12 to 3.0.22 and running the daemons 2-3 days my Samba Server freeze the whole Server. First the clients get connection problems, timing out to access the shares and then some minutes later the whole Server freeze, i can't even logon on the console. Only a cold reset is possible. I convert all files from latin-1 to a UTF-8 and then from UTF-8 to ISO-8859-1

On a CentOS 5.1 server samba works perfectly as long as connections exist. If no connections exist nmbd shuts down: service smb status smbd (pid 2970 2934) is running... nmbd dead but pid file exists On this last occasion it had been less than 5 minutes between connections. What could be causing this? Anne -------------- next part -------------- A non-text attachment was scrubbed... Name:

Hello I seem to be having signing problems with 3.2.0 I have 2 PDCs on 2 different sites (say A and B) both running 3.2.0, with the line server signing = auto in smb.conf. There is a one way trust (B trusting A) setup. While everything works correctly on both sites for local machines access to local shares (a site A user logged on a site A machine can perfectly access shares of site A PDC). The

I need to have the following services from my server: imap - mostly by lan, but occasionally external file and print serve samba access - read and write to some directories The problems I'm seeing are inconsistent, making it difficult to know how to find the source. Samba access is essential to me. I use a server-based korganizer, and without samba it's inaccessible. Sometimes it is

Hello, I am trying to connect a 2nd Linux machine to my Samba PDC using smbmount. Both machines run Samba 3.0.14a. However, when trying to mount using machine2# /usr/local/samba/bin/smbmount //pdc/wpkg /raid/samba/mount -o username=abc,password=123 it takes some seconds and then only brings up an I/O error. The log on the primary machine brings up [2005/07/19 10:28:36, 1, effective(1008,

Hi *! I have a samba (3.0.20b)+ldap pdc and I this problem: I can't mount a samba share from a linux client. samba/error.log: [2006/01/18 14:51:42, 1] smbd/service.c:make_connection_snum(662) ? 192.168.10.41 (192.168.10.41) signed connect to service pubblica initiall y asuser sambauser (uidP1, gidQ2) (pid 11527) [2006/01/18 14:51:42, 0] libsmb/smb_signing.c:srv_check_incoming_message(78 2)

LAN - mixed architecture - 2 x win98, 1 x winME, 1 x win2k, 3 x Mandrake Linux 10.0. Most samba activity is between the Mdk boxes, file-moving, etc. Versions - Mandrake 10.0, with all updates applied, Samba 3.0.6-4.1 I had a properly working lan, with occasional problems between box1 and box2 (Mdk boxes). Now I have no connection between them, for file-sharing purposes, at all. Box3,

--- branches/SAMBA_3_0_RELEASE/source/smbd/dosmode.c 2004/10/25 19:25:54 3220 +++ branches/SAMBA_3_0_RELEASE/source/smbd/dosmode.c 2004/11/07 20:42:45 3605 @@ -344,7 +344,9 @@ return(-1); } - get_acl_group_bits(conn, fname, &st->st_mode); + if (!get_acl_group_bits(conn, fname, &st->st_mode)) { + return(-1); + } if (S_ISDIR(st->st_mode)) dosmode |= aDIR; This

Hi, Rowland, and thanks for the reply. The PDC OS is Slackware 13. The BDC OS is Slackware 14. The choice to use Samba 4.0 was merely due to its inclusion on the Slackware 14 distro. I'll worry about upgrading that once I have the migration complete. I will post the two machine's respective smb.conf's later today. -- View this message in context:

As promised, I'm posting the smb.conf files for the two servers in question. One minor correction I should offer is that the new SAMBA server will be version 4.1, not 4.0. Following is SMB.CONF for the current PDC, which is Samba 3.3.4 on Slackware 13. I've omitted all share definitions to allow focus more on the configuration side. Actual server/domain names have been omitted.

On 12/02/15 02:43, soonerdave wrote: > As promised, I'm posting the smb.conf files for the two servers in question. > > One minor correction I should offer is that the new SAMBA server will be > version 4.1, not 4.0. > > Following is SMB.CONF for the current PDC, which is Samba 3.3.4 on Slackware > 13. > I've omitted all share definitions to allow focus more on the

I'm running OS X 10.3.9/Samba 3.0.10. When I try to connect to my Windows 2000 machine from my user account, I enter the correct workgroup/user/password and then get the message 'The Finder cannot complete the operation because some data in "smb://machinename" could not be read or written. (Error code -36).' (Error code -36 in OS X is "i/O error (bummers)".) I

Hi all hope you can help, I have a mixed XP / 2K client deployment, and the samba server is running as a PDC. On most machines I have no problems, but on 2 2K machines and 1 XP machine I'm getting the same behaviour every time I either try to write the file or execute a file, no matter whether I log on to the domain or which userid I log on as. I'm also running debian woody 2.4.19, and

Dear All, I have configured ldap with uid='some numeric' instead of uid=username like that; dn: uid=102220,ou=User,dc=example,dc=com uid: 102220 username: test1 cn: Test Account objectClass: inetOrgPerson objectClass: posixAccount objectClass: top objectClass: shadowAccount objectClass: sambaSamAccount mail: test1 at cdac.in shadowLastChange: 15587 loginShell: /bin/bash uidNumber: 5345

Okay guys, Im trying to get samba 3.0.23a to join a Windows Domain (no suprise right) Anyways, i ran "net rpc join -U [adminaccount]", it asked for the password to [adminaccount] and said the domain was joined. Then i ran "net ads join -U [adminaccount]", it asked for the passsword to [adminaccount] and after typing it in, it says [2006/08/07 10:35:56, 0]

We have a Linux user and group with the same name (username prox, group name prox) and a Samba share with "force user = prox" set. Since upgrading from Samba 3.0.21b to Samba 3.0.23a, that share no longer works. smbclient gives the following error when connecting to the share: tree connect failed: NT_STATUS_NO_SUCH_USER The Samba server logs the following error: [2006/08/07 09:38:26,

I have to assume much, I'll try. So... - No AD, that's some NT4 domain. - No Winbind because Winbind is using samacccountname as user login and not UID. - Issue happens on Linux or UNIX clients. The question is what tool (SSSD, pam_ldap / nss_ldap, nslcd...) are you using to retrieve information from LDAP to forge users on system side. Once you get an answer to this previous question

hello when I try to connect to a share from my windows xp client, it does not work. In linux via smbclient, there's no problem. see below for the error log version = 3.0.21a security = server (the problem only seems to occur on servers that rely on another samba server for authentication). any ideas? werner [2006/01/27 09:30:32, 2] auth/auth.c:check_ntlm_password(307)