similar to: Passwords and NT 4

Has anyone tried DFS Client SW on a Win 95 machine and then tried to mount the usual samba drives? All I get is a login request that gets refused even with known, correct, credentials. Its appears just the same as the problem we got after installing SP3 on an NT4 machine before changing the registry. The only way to fix it is, on the 95 machine, to remove the DFS client, remove ALL the network

> I've disassembled the failing MultiSource/Benchmarks/tramp3d-v4/tramp3d-v4 and compared it to > the one from the LLVM 3.6.0 test runs. There's nothing obvious. We've removed some useless > 'addiu $sp,$sp,0', eliminated two (seemingly redundant) sign extends, and the addresses of > functions+data has changed slightly. I've investigated further and I'm

Hello, Perhaps this post is not directly connected with Samba itself but after I saw that Samba uses EXOP for LDAP password changing I decided to write it to this list as well. Here is what I'd like to do: 1) I use openldap-2.3.35 for Samba auth mechanism 2) additionally I use openldap for any other auths I have in my subnet - exim, imap, svn, linux-login, etc... In case of Samba the

Hi, I have referred to the archive and some of you were having the oplock_break problem. Does anyone have any solution for this? Will reboot fix the problem? Please advise. regards, Bridget

On Oct 15, 2008, at 5:29 AM, sanjiv gupta wrote: > On Tue, 2008-10-14 at 10:19 -0700, Evan Cheng wrote: >> You need to specify sub-register == super-register, idx relationship. >> See X86RegisterInfo.td: >> >> def x86_subreg_8bit : PatLeaf<(i32 1)>; >> def x86_subreg_16bit : PatLeaf<(i32 2)>; >> def x86_subreg_32bit : PatLeaf<(i32

Good evening, On the bottom of page 53, section 4.1.2.2 in the SNIA spec (http://www.snia.org/tech_activities/CIFS/CIFS-TR-1p00_FINAL.pdf), it states if the dialect is NT LM 0.12 and extended security is off (I.e., use "traditional" NTLMv2/NTLMv2 authentication w/o SecurityBlobs), the SessionSetupAndX response is as shown in section 4.1.2.2 with a word count = 4. However, what I have

Hi, I've been handed the administration of our Solaris 2.5.1 Server and have recently upgraded to Samba 2.0.5a. As the server is in a predominantly NTsp3 environment it was requested that when the NT passwords change (each month) the Unix Passwords should also change. All the NT and Win95 Clients are currently authenticating using Plain Text Passwords. Also the current security level is

On Tue, 2008-10-14 at 10:19 -0700, Evan Cheng wrote: > You need to specify sub-register == super-register, idx relationship. > See X86RegisterInfo.td: > > def x86_subreg_8bit : PatLeaf<(i32 1)>; > def x86_subreg_16bit : PatLeaf<(i32 2)>; > def x86_subreg_32bit : PatLeaf<(i32 3)>; > > def : SubRegSet<1, [AX, CX, DX, BX, SP, BP, SI, DI, >

You need to specify sub-register == super-register, idx relationship. See X86RegisterInfo.td: def x86_subreg_8bit : PatLeaf<(i32 1)>; def x86_subreg_16bit : PatLeaf<(i32 2)>; def x86_subreg_32bit : PatLeaf<(i32 3)>; def : SubRegSet<1, [AX, CX, DX, BX, SP, BP, SI, DI, R8W, R9W, R10W, R11W, R12W, R13W, R14W, R15W], [AL, CL,

Sorry to bother, but I posted this before with no responses. I am having several problems getting samba compiled with winbind to join a NT4 domain. Using smbpasswd I get the error cli_pipe:return critical error. error code was 0 and Unable to join domain DOM. On the PDC I get a Dr. Watson error C0000037, not even the administrator password is accepted on the console, and all clients connected to

I have installed Samba 2.0.4a on SGIs running IRIX 6.5. My PC is running NT Workstation SP 3. I have a problem saving documents from MS Word 97 SP 1. If I create a new document and attempt to save it to a Samba share I get the following error message: Word cannot complete the save due to a file permission error. (G:\XX\TEST.DOC). A listing of the directory from Unix shows the following:

Hello, I'd be very grateful if anyone could share their ideas on this problem. The situation is this: I have a Solaris 8 machine running Samba 2.2.1a. The global configuration has "security = USER" and originally had "encrypt passwords = NO". I was able to map drives to shares on this machine from my WinNT 4 SP 5 workstation when I set the registry key advised by the

Hi, I have make an analise with presence and absence, y=(1 e 0). I have a area continuous data and a sp data with 25 levels. I have 300 points. When I make glm((presenca/peso)~area,weights=peso,family=binomial,maxit=1000) where presenca is 0 or 1. peso is the unit = 1. area is the continuous data. The analysis is OK. When I put the sp and interactions in analysis this warning appear.

On Wed, 2008-10-15 at 10:08 -0700, Evan Cheng wrote: > On Oct 15, 2008, at 5:29 AM, sanjiv gupta wrote: > > > On Tue, 2008-10-14 at 10:19 -0700, Evan Cheng wrote: > >> You need to specify sub-register == super-register, idx relationship. > >> See X86RegisterInfo.td: > >> > >> def x86_subreg_8bit : PatLeaf<(i32 1)>; > >> def

smbstatus reports the following...that my NT users on this one samba server are connected as the guest user "nobody". All Win95 users are connected under their proper name. Anything I need to change? Samba version 1.9.16p11 Service uid gid pid machine ---------------------------------------------- gdl nobody nogroup 1555 gdl-dt (137.202.211.8) Wed

The VNET_LE flag was introduced to fix accesses to virtio 1.0 headers that are always little-endian. It can also be used to handle the special case of a legacy little-endian device implemented by a big-endian host. Let's add a flag and ioctls for big-endian devices as well. If both flags are set, little-endian wins. Since this is isn't a common usecase, the feature is controlled by a

On Tue, Jul 14, 2020 at 02:08:47PM +0200, Joerg Roedel wrote: > @@ -489,6 +490,9 @@ DEFINE_IDTENTRY_RAW(exc_nmi) > this_cpu_write(nmi_cr2, read_cr2()); > nmi_restart: > > + /* Needs to happen before DR7 is accessed */ > + sev_es_ist_enter(regs); > + > this_cpu_write(nmi_dr7, local_db_save()); > > nmi_enter(); > @@ -502,6 +506,8 @@

On Tue, Jul 14, 2020 at 02:08:47PM +0200, Joerg Roedel wrote: > @@ -489,6 +490,9 @@ DEFINE_IDTENTRY_RAW(exc_nmi) > this_cpu_write(nmi_cr2, read_cr2()); > nmi_restart: > > + /* Needs to happen before DR7 is accessed */ > + sev_es_ist_enter(regs); > + > this_cpu_write(nmi_dr7, local_db_save()); > > nmi_enter(); > @@ -502,6 +506,8 @@

On Tue, 21 Apr 2015 16:06:33 +0200 "Michael S. Tsirkin" <mst at redhat.com> wrote: > On Fri, Apr 10, 2015 at 12:20:21PM +0200, Greg Kurz wrote: > > The VNET_LE flag was introduced to fix accesses to virtio 1.0 headers > > that are always little-endian. It can also be used to handle the special > > case of a legacy little-endian device implemented by a

From: Joerg Roedel <jroedel at suse.de> When an NMI hits in the #VC handler entry code before it switched to another stack, any subsequent #VC exception in the NMI code-path will overwrite the interrupted #VC handlers stack. Make sure this doesn't happen by explicitly adjusting the #VC IST entry in the NMI handler for the time in can cause #VC exceptions. Signed-off-by: Joerg Roedel