similar to: 2.0.2 servers with 1.9.18p10 DMB?

I'm currently investigating the appearance of this error message for a significant number of our users' password change attempts. It would seem from my research that this error occurs when the data coming from the SamOEMhash function is not of the expected format/value. I do not know if this would be due to incorrect data being sent into the SamOEMhash function from the client or something

I posted my original question below to the samba-ntdom list but it seems to be the wrong place to be discussing this problem so I'm moving my follow-up to these lists. Background...I used to be using smbpasswd and the "unix password sync", "password chat", and "password program" settings to keep my smb passwords and unix passwords in sync. This was working well

In 2.0.4b using a 16-bit client (in this case Lanman for DOS), disk space reporting for partitions greater than 2GB always reports 0 space free. I've tracked this down to the disk_norm routine in the smbd/dfree.c file. In the code for adjusting block size and disk size/free values for 16-bit reporting, WORDMAX was incorrectly being multiplied by 512 before being compared with bsize. This

skeet@Bridgewater.EDU wrote: > > > Basically what it looks like to me is that an smbd process is spawning a > child which goes defunct for some reason I have yet to determine and the > smbd process hangs out there waiting for the child. Of course the child is > never going to answer being defunct, so the parent smbd process sticks > around and keeps its oplocks. > That

I saw a little discussion about this a few weeks ago but nothing concrete. We're running samba-1.9.18p8 under Solaris 2.6x86. I am periodically getting the following in the logfiles, usually _many_ at a time: 1998/11/03 14:42:00 request_oplock_break: no response received to oplock break request to pid 5411 on port 40884 for dev = 1980040, inode = 33c4d When I look up the PID (in this case

Pam_SMB allows Linux clients to validate their passwords against an NT PDC, so the only thing you have to do is set up the accounts on the Linux side with an '*' in the /etc/passwd entry. This can be done using a list of users: #!/bin/bash for i in `cat myuserlist`; do /usr/sbin/adduser -p '*' $i with various other command line options, such as "-s

I was running 1.9.18p10 on a test DEC Unix 4.0d box here and I decided to give 2.0beta3 a try. For some reason, I cannot connect to any of the server's shares or even get a list of it's services (via Start->Run->\\server) from Win95 clients. It asks for a password and no matter what I put in there I get "The password is not correct. Try again." I configured Beta3 a la:

There is Windows 2008R2 actng as DC and Samba4 4.5.2 acting as standalone server in the same network. Samba4 is set up to be DMB: domain master = yes local maser= yes browse list = yes os level = 254 preferred master = yes enhanced browsing = yes Windows 2008R2 includes also DMB role in itself. As following, if Windows boots first, before Samba starts, it becomes DMB and has workgroup<1b>

Note: LMB = Local Master Browser DMB = Domain Master Browser Have Samba 2.2.7A running embedded in a variant of ucLinux. My interest was only to use Samba as a WINS server. I've set up the SMB.CONF with this config. for one test: wins support = yes local master = no domain master = yes preferred master = no os level = 0 I've set up the SMB.CONF with this config. for the other

My network looks like this: internet 192.168.0.0/24 router ----+----+----+----- internal 192.168.5.0/24 | | | router ----+-----+------+- LNB--->mswin | | (also a | | | client | | samba | | .... | | server) | | samba | | samba

1: is it possible to use ioemu:sda instead of ioemu:hda ? 2: is ioemu keyword optionnal ? conf seems to work without 3: why d i need to put vfb = [ "type=vnc,vncunused=1,keymap=fr" ] line ? seperate vnc = 1 + vncunused = 1 look identical to me, but are ignored. have the conf parser changed ? 4: during dom0 startup: > * Starting Xen control daemon ... > * Error: either

Hi, I got an optimization problem (O1, O2) regarding memory barrier “dmb ishld” I find in the test/CodeGen/AArch64/intrinsics-memory-barrier.ll , it’s stated that memory access around DMB should not be reordered, but when compiling the Linux kernel, I found load/store in static inline void hlist_add_before_rcu(struct hlist_node *n, struct hlist_node *next) { n->pprev

Hi Tim, > That barrier should be treated the same as any other dmb by LLVM. What > I'm most confused about is why it's there in the first place. From > what I can tell, the rcu_assign_pointer function should map to a > native store-release operation (stlr). I guess it's because we disabled the integrated-asm, so it won't complain when compiling the kernel. > Also,

Hello ! I have a problem of syncing browse lists between DMB and LMB. The topology of ours network is as follows: Linux Network comma(Linux, DMB, WINS) vol(Linux) door(Linux, LMB) | | | | | | | | | --------------(195.226.226.16/28)------ | | | | | | | --(local net

I'm using r223407. Switching to a clean built on r223853, it still gives me: ldr x8, [x21,#8] stp x21, x8, [x19] dmb ishst ldr x8, [x19,#8] str x19, [x8] str x19, [x21,#8] Thanks, Chengyu > On Dec 9, 2014, at 6:32 PM, Tim Northover <t.p.northover at gmail.com> wrote: > > On 9 December 2014 at 15:14, Chengyu Song <csong84 at gatech.edu> wrote:

If I have a client that wants to enumerate and access shares on a subnet, and that client knows the IP of the WINS server, is there any need for the client to use the "browsing" services of a DMB or LMB? What is the order of operations of the client? Here is what I imagine to be the case: 1. client asks LMB for a list of all available shares 2. LMB sends client the list of all known

SunOS pop01.unix 5.10 Generic_118844-26 i86pc i386 i86pc dovecot-1.0.beta3 It is most likely something I am doing wrong, but could someone take a look at why I can not get LDAP prefetch to work? If I define things like this: dovecot.conf: ---------------------------------------------- passdb ldap { args = /usr/local/etc/dovecot-ldap.conf } userdb ldap { args =

I figure out that samba PDC did not advertised itself as <domain>#1b (DMB), is this normal? smb.conf : os level = 65 preferred master = yes domain master = yes local master = yes domain logons = yes [root@jeruk root]# nmblookup -A 10.200.100.3 Looking up status of 10.200.100.3 LIN3PWK <00> - H <ACTIVE> LIN3PWK <03> -

> On Dec 9, 2014, at 3:45 PM, Tim Northover <t.p.northover at gmail.com> wrote: > >> I guess it's because we disabled the integrated-asm, so it won't complain when compiling the kernel. > > No, it's something different. The inline assembly (for whatever > reason) says to use a "dmb ishst" rather than an "stlr". I don't > actually

>> Switching to a clean built on r223853, it still gives me: >> >> ldr x8, [x21,#8] >> stp x21, x8, [x19] >> dmb ishst >> ldr x8, [x19,#8] >> str x19, [x8] >> str x19, [x21,#8] > > Isn't that correct though? The problematic "str" has been folded into > the "stp" instruction, so "x19 + 8"