similar to: ACLs, NT_STATUS_ACCESS_DENIED, etc.

Displaying 20 results from an estimated 1000 matches similar to: "ACLs, NT_STATUS_ACCESS_DENIED, etc."

2006 May 09
1
NT4 user can't change password during logon (but XP can)
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 ,
2010 Aug 18
1
Error: You do not have permission to change your password
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
2010 Oct 20
0
No subject
samba fails to allow this operation. 4.11. documentation ... ----------------------- In [8] there is very helpful tip to take migration using temporal root acco= unt. These two sentences was that break point... 4.12. Searching for root ------------------------ As stated in [7] net command operates on two servers, both of them is conne= cted using same account name. On other side DST account
2010 Dec 11
3
Keeping Windows ACL's when migrating to SAMBA Server
We setup a Ubuntu SAMBA 3.5 server and would like it to replace our current Windows 2003 file server. I can manually copy the files over but need to keep all the Windows UID's and GID's but am having trouble copying the files over. Does anyone have any idea what im doing wrong or have any ideas for me to do this? I have pasted the contents of my smb.conf below my name. George
2012 Dec 17
1
S4 AD Domain Up; but lots of NTLMSSP NTLM2 errors
samba-4.0.0 x86_64, CentOS6.3 My Samba4 / AD is up and running after migrating this weekend. Testing looked good and the domain *is working* but there are some issues. My log.samba file is full of the following; I'm not certain of the significance of these. [2012/12/17 05:59:09, 0] ../auth/ntlmssp/ntlmssp_sign.c:236(ntlmssp_check_packet) NTLMSSP NTLM2 packet check failed due to invalid
2003 Aug 08
0
Reposted: Please help! Samba 3 beta3 and windows XP - SP1 client!
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
2003 Aug 26
1
Invalid auth info 68 or level 5 on schannel only prior to
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
2004 Jun 16
0
Password change problem, Samba 3.0.4
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
2004 Aug 16
1
PDC/LDAP domain login problems
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
2003 Dec 08
0
is the domain-name in smb.conf case-sensitive?
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
2004 Jul 28
1
failed to decode PDU - failed to do schannel processing
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]
2003 Jun 26
1
Urgent : Connection problem to a Samba PDC
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
2004 Feb 09
1
error messages -- what does it mean?
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
2004 Jul 11
1
Cannot login to PDC after upgrade
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
2003 Oct 17
1
Updating 2.2.8a to 3.0.0 (LDAP)
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
2004 May 11
2
smbd log meesages
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
2004 Mar 31
2
Problem w/ Samba 3 & LDAP
-----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
2004 Feb 24
3
PDU & schannel errors
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,
2004 Jan 12
1
Another problem with Win2k logins...
Hi all, After recovering the former SID that I hadn't had in mind while changing the Linux distro (thanks to Thomas for his help), now I still have some problems. I can't still get any user to login but the ones that must be in cache in the clients (thanks again Thomas). So, I'll give you the logs to see if anybody detects something strange... The users can perform a 'smbclient -L
2016 Feb 05
3
Samba 4 Domain Members stop autenticate with Samba 3 PDC after seven (7) days
On a server Centos 7 with samba-4.2.3-11.el7_2.x86_64, joined to a server samba-3.6.23-24.el6_7.x86_64 PDC on Centos 6.7 up to date, after 7 days I want restart winbind service because the users are not autenticate anymore. This is the error into log file: > Feb  4 10:15:26 s-graph smbd[28960]: [2016/02/04 10:15:26.529467,  0] > ../auth/ntlmssp/ntlmssp_sign.c:236(ntlmssp_check_packet) >