similar to: Providing Home Dirs

Can someone verify that I am having the same problem with Mac OS X Panther (10.3.3) using Samba 3.0.2 based on my log below? I get this trying to connect from my WinXP machine to my Mac which is configured with ADS. If so, can you point me to a set of instructions on upgrading from 3.0.2 to 3.0.4 with this patch? I don't have control over the server I authenticate with...it is about 300

Hey, all. I've got some irksome issues, and would love it if someone could show me where I'm going wrong. First and foremost, I can access the folders, create new ones, etc. But copying stuff from an existing Windows share (with ACLs), not so much. Likewise when I try to assign permissions. I wind up with stuff like [2010/12/01 02:56:34, 0]

When a password must be changed during logon (pdbedit <user> --pwd-must-change-time=0) then this is impossible on NT4 SP6a machines; we always get this error: "Unable to change the password on this account (C00000BE). Please consult your system administrator.". At that time we get these messages in log.smbd: <<<< log.smbd <<<< [Tue May 9 10:46:17 2006 ,

I'm using Samba v3.5.4-62 on Fedora 13 PDC Using LDAP passdb backend and do the following... 1. Login as user on Windows system using domain user name and password - Login successful 2. Press Ctrl-Alt-Del 3. Press Change Password 4. Enter old and new password as prompted 5. Receive response "You do not have permission to change your password." I receive the following

Sorry to post again, but this doesn't seem to be showing on the news server. "Jon Fanti" <jon.fanti@stoopid.me.uk> wrote in message news:... > Hi, > > I have a samba PDC running at home as the domain "WONDERLAND". I have a > Windows 2000 SP4 machine and a Windows XP SP1 machine. The Windows 2000 > machine will join and allow user logins to the domain

logins Reply-To: I've sourced the groups, but haven't had any success with solving this problem. Here are the details: I have a debian/testing system running samba 3.0.0beta2-1. It was working fine with the 2.x series, until I upgraded to 3.0. The debian server (al) is a PDC for a small NT domain (isabela) with three workstations, all running win2k pro. All but one work fine

Greetings list. I've been trolling the archives and google searches all morning and cannot seem to come up with an answer to this, though I'm not the first to experience the problem. I'm running samba on FreeBSD 5.2.1-p4, installed from the ports collection. When a user other than root attempts to change an smb password (either through SWAT or with smbpasswd) I get the following

I am a Mac user and am only using Samba to the extent that it is installed with Mac OS X. I am simply trying to share files between a Windows PC and my Mac laptop. I'm hoping that the error message below concerning the secrets.tdb file may be meaningful to someone on this list. I haven't had any luck yet with a similar post on Apple's forum. Before I upgraded to Leopard, I

My job, rsync -auv --exclude ".snapshot" --delete --safe-links /NFSvol/bam1/vg1/home1 /Volumes/xraid3/bam1/vol1/ >/var/local/log/bam1home1.log 2>&1 is several times with the following message, Invalid checksum length 1913126912 rsync error: protocol incompatibility (code 2) at /SourceCache/rsync/rsync-20/rsync/sender.c(59) rsync: writefd_unbuffered failed to write 103

OK - I finally am able to join machines to the domain, but I cant log in to them (at least not my test client anyway). If anyone can help I would be really really appreciative! Platform: Solaris 9, Samba 3.0.5, Sun One Directory Server 5.1 error is: The system could not log you on. Make sure your User name and domain are correct, then type your password again. Letters in passwords must be

hi list, i try since weeks to authenticate my linux-clients against my samba-server. This works very fine with 2 windoze-cliens. but i still cannot authenticate with my linux-clients. i am @office now, thats wy i ask instead to test: i heard, winbind is used to authenticate linux-clients against the samba-server. the wbinfo -u gives me back: DOMAIN-user (i use the minus as separator) so i

I am running Slackware 10 samba-3.0.5-i486-2 I get the following errors in my syslog, over and over and over... Jul 27 17:05:51 Olympus smbd[11471]: [2004/07/27 17:05:51, 0] rpc_server/srv_pipe.c:api_pipe_netsec_process(1397) Jul 27 17:05:51 Olympus smbd[11471]: failed to decode PDU Jul 27 17:05:51 Olympus smbd[11471]: [2004/07/27 17:05:51, 0]

Hi, We have a Samba3.0Beta1-LDAP acting as PDC for about 170 computers, since 2 weeks everything works perfectly but since yesterday every computers are unable to connect to the PDC. The following message appears on client side : The session setup from the computer CJEREV01 failed to authenticate. The name(s) of the account(s) referenced in the security database is CJEREV01$. The following

Feb 9 07:08:10 fileserver smbd[2025]: [2004/02/09 07:08:10, 0] rpc_server/srv_pipe.c:api_pipe_netsec_process(1371) Feb 9 07:08:10 fileserver smbd[2025]: failed to decode PDU Feb 9 07:08:10 fileserver smbd[2025]: [2004/02/09 07:08:10, 0] rpc_server/srv_pipe_hnd.c:process_request_pdu(605) Feb 9 07:08:10 fileserver smbd[2025]: process_request_pdu: failed to do schannel processing. I

We recently converted our Redhat9 Samba server to Debian Sarge/testing. We are running (3.0.2a-Debian). After installing Debian, I itegrated the old configuration files (smb.conf, smbpasswd, smbusers, secrets.tdb) making changes where I thought it was necessary. When I tried to login to our Windows 2000 server using rdesktopl, windows tells me that I've specified the incorrect username or

Greetings- I am working through coming up with a Linux client integration to Samba PDC's. I mount several shares with this sort of syntax: /bin/mount -t cifs -o credentials=/home/userid/.smbcredentials,uid=userid,gid=userid,dmask=0777,fmask=0666 //ldslnx01/data /mnt/ldslnx01/data/ However when I create new files/dirs on the Samba share from the Linux workstation, the perms are not 0666/0777

Hi, we have Samba 2.2.8a+LDAP 2.0.27 domain controllers running on our Debian servers and I'm preparing the update to Samba 3.0.0. Everything seems to work fine so far, except that I get some error messages that I don't understand. Could someone please explain them to me? Should I wait for the next Samba release before switching to 3.x? The error messages: When a user logs into the

Can someone please explain what these messages mean. I am running 3.0.2a with no issues at all. I just happened to be looking through the logs and notice the messages. [2004/05/10 03:53:23, 0] rpc_server/srv_pipe.c:api_pipe_netsec_process(1371) failed to decode PDU [2004/05/10 03:53:23, 0] rpc_server/srv_pipe_hnd.c:process_request_pdu(605) process_request_pdu: failed to do schannel

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Here is a description of what I am trying to do (with Samba 3.0.2a & openldap 2.1.27): I have all my users populated into the LDAP with all the applicable attributes; Users can map drives to a server using LDAP as the authentication backend without issue. Where I am running into problems is bringing up a PDC using Samba w/LDAP. * I added

I extracted the following weird error from the sys-log regarding pdu and schannel (have the same PID): Feb 24 10:40:37 s-svr01 smbd[31833]: [2004/02/24 10:40:37, 0, pid=31833, effective(65534, 65533), real(65534, 0)] rpc_server/srv_pipe.c:api_pipe_netsec_process(1371) Feb 24 10:40:37 s-svr01 smbd[31833]: failed to decode PDU Feb 24 10:40:37 s-svr01 smbd[31833]: [2004/02/24 10:40:37, 0,