similar to: check_oem_password: Incorrect password length

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

Have there been any problems reported with running 2.0.2 on servers using security=server with a 1.9.18p10 DMB? We've run into a situation where I've upgraded 4 of our servers to 2.0.2 but the DMB is still running 1.9.18p10. We have had sporatic trouble with the upgraded servers rejecting correct passwords because the DMB seemingly would not properly validate them. Today, we ran into a

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 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

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

Hi everybody, I'm an italian system administration (newbie about Samba). I have installed on Mandrake 9.1 the rpm samba3-*-3.0.2a downloaded from a Samba.org's mirror. I have configured a PDC based on ldapsam (OpenLDAP 2.1.29) that works fine, i use smbldap tools to manage sincronization account. Now the problem, when I try from my W2000 Workstation to change my domain password I reach

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:

On Tue, Apr 11, 2017 at 1:32 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > On Tue, Apr 11, 2017 at 1:11 PM, Alastair Bridgewater > <alastair.bridgewater at gmail.com> wrote: > > + /* HDMI 3D support */ > > + if ((disp->disp.oclass >= NV50_DISP) > > You probably meant G82_DISP. Although I don't know if there were any > G80's

On Tue, Apr 11, 2017 at 1:11 PM, Alastair Bridgewater <alastair.bridgewater at gmail.com> wrote: > Enable stereoscopic output for HDMI and DisplayPort connectors on > NV50+ (G80+) hardware. We do not enable stereoscopy on older > hardware in case there is some older board that still has HDMI > output but for which we have no logic for setting the Vendor > InfoFrame. > >

On Tue, Jan 17, 2017 at 5:42 PM, Alastair Bridgewater <alastair.bridgewater at gmail.com> wrote: > HDMI specification 1.4a, table 8-15 is very explicitly a "must > support at least one of" table, not a "must support all of" table. > It is not hard to find hardware that does not support some of the > so-called "mandatory" modes. > > More

Store the ELD correctly, not just enough copies of the first byte to pad out the given ELD size. Signed-off-by: Alastair Bridgewater <alastair.bridgewater at gmail.com> --- drivers/gpu/drm/nouveau/nvkm/engine/disp/hdagt215.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/nouveau/nvkm/engine/disp/hdagt215.c

Enable stereoscopic output for HDMI and DisplayPort connectors on NV50+ (G80+) hardware. We do not enable stereoscopy on older hardware in case there is some older board that still has HDMI output but for which we have no logic for setting the Vendor InfoFrame. With this, I get an obvious 3D output when using the "testdisplay" program from intel-gpu-tools with the "-3"

i ran into a link error trying to compile the linux vorbis-tools-1.0rc3 using gcc 2.95.3 gcc -O20 -ffast-math -fsigned-char -o oggenc oggenc.o audio.o encode.o platform.o /usr/lib/libvorbisenc.so -L/lib /usr/lib/libvorbis.so -lm /usr/lib/libogg.so ../share/libutf8.a ../share/libgetopt.a encode.o: In function `oe_encode': encode.o(.text+0x87): undefined reference to

('binary' encoding is not supported, stored as-is) http://www.kiss-technology.com/support/dp-450_FAQ.asp Scroll all the way down. There is a changelog for the Firmwareupdate and a link to a zip file containing the update. -- Daniel <p>Monty wrote: Interesting bit of news this. Anyone able to independently confirm it? Monty ----- Forwarded message from "Jesse S. A.

Interesting bit of news this. Anyone able to independently confirm it? Monty <p>----- Forwarded message from "Jesse S. A. Bridgewater" <jsab@member.fsf.org> ----- Delivery-Date: Sun Dec 29 02:11:47 2002 From: "Jesse S. A. Bridgewater" <jsab@member.fsf.org> To: webmaster@xiph.org Subject: KISS DVD player with Vorbis Support Hi There, You probably know

On Mon, Mar 27, 2017 at 05:57:57PM -0400, Alastair Bridgewater wrote: > HDMI 3D mode support, round two. Revisions include no longer dealing > with audio InfoFrames, passing infoframe data to NVKM as bags of bytes > rather than as data pre-packed for the hardware, more-normal return > value checking for drm_hdmi_*_infoframe_from_display_mode() results, > Frame-Packing mode support,

HDMI specification 1.4a, table 8-15 is very explicitly a "must support at least one of" table, not a "must support all of" table. It is not hard to find hardware that does not support some of the so-called "mandatory" modes. More seriously, this code generates invalid display modes for both of the 3D-capable panels that I have (a 42-inch LG TV and a Sony PlayStation

On Wed, Mar 29, 2017 at 8:02 AM, Ville Syrjälä < ville.syrjala at linux.intel.com> wrote: > > On Mon, Mar 27, 2017 at 05:57:57PM -0400, Alastair Bridgewater wrote: > > And the tenth patch enables stereo mode support... on HDMI and DPort > > connectors on nv50+ hardware. HDMI connectors because obvious. DPort > > connectors because of DPort to HDMI adaptors. >

On Wed, Jan 18, 2017 at 12:10:56AM -0500, Ilia Mirkin wrote: > On Tue, Jan 17, 2017 at 5:42 PM, Alastair Bridgewater > <alastair.bridgewater at gmail.com> wrote: > > HDMI specification 1.4a, table 8-15 is very explicitly a "must > > support at least one of" table, not a "must support all of" table. > > It is not hard to find hardware that does not