similar to: PDC upgraded from 2.2.7 to 3.0.0beta1, now XP clients can't logon

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,

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 ,

Dear samba-users We are experiencing some rather long logon times using SAMBA 3.5.6 on Debian Squeeze + Windows 7 and while trying to find out why we raised the loglevel to 5 resulting in a rather large logfile. But this did give us a hint as to why we experience so long logon times. It seems that samba is going through the whole user-database with all usernames and machine-accounts. Eventually

I'm having problems accessing Samba shares from my XP Pro machine. Samba 2.2.7 is installed on two Redhat 8.0 machines and configured using SWAT. I have user level security and encrypted passwords setup. I have a printer shared on both servers as well as home directories and one restricted access share. My printers are setup for guest access so all machines will always be able to print.

Hi, I just tried an upgrade from Samba 3.0.2a to 3.0.11 to fix a known bug (1147), but now I get a different problem. Users cannot login. Here's what the log looks like in 3.0.2a ............. [2005/02/22 16:57:49, 2] param/loadparm.c:do_section(3339) Processing section "[shares]" [2005/02/22 16:57:49, 2] lib/interface.c:add_interface(79) added interface ip=192.168.4.10

Dear Listmembers, apparently my attachement was not distributed via the list, therefore I add it once again to this email; plain text following my question. Many thanks for any suggestion in advance: I am using a SPARC ULTRA 60 / running SuSE sparc linux 7.3 as server for our M$-Network. I recently installed samba-2.2.8a from SuSE (compiled src-rpm), since then I am facing problems when attaching

Hi ... I am desperate now to solve this problem ... this is my absolute last resort attempt! I have read of the problem on a number of posts/newsgroups/webpages - but there a very little solutions - or causes - none of the solutions have worked for me! Basically my samba is happily running and I can connect to it fine from 9x clients and from 2k client as a workgroup. However..... If I try to

Hello. usrmgr gives me this error, if I try to create or modify a user: The group name could not be found. I can create and modify groups with no errors!. This is my smb.conf: [global] addsharecommand = /etc/samba/scripts/modify_samba_config.pl netbiosname = Spider-Man deletesharecommand = /etc/samba/scripts/modify_samba_config.pl usernamemap = /etc/samba/smbusers maxlogsize = 50

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]

I know it is a moderated list - just do not know how to get to the moderator. Was just reinstalling suse 9.1 on top of an existing 9.1 (with samba) (it solved another issue with the monitor but created a samba problem) applied all patches reinstallation remembered all settings correctly, even the smb.conf file, but smbd does not start anymore. , I get a

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

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