similar to: [PATCH] Unreliable network connections with 3.0.1 - need advice

A lot of people have complained about unreliable connections to W2K and XP machines. The folowing patch solved the problems for us. I have no idea why it works, but after this patch we had no more problems connecting to workstations in the domain. --- samba-3.0.2pre1/source/rpc_parse/parse_net.c 2004-01-06 22:08:41.000000000 +0100 +++ samba-3.0.2pre1/source/rpc_parse/parse_net.c 2004-01-07

Hello all. AIX 4.3.3 / Samba 2.0.6 / Production NT4.0 domain Security = DOMAIN encrypt passwords = yes update encrypted = yes Action: Moving from NT4.0 domain called nt40 to AD 2000 Domain called ad-domain Problem: Users that have been migrated to ad-domain cannot authenticate to AIX SAMBA shares . . . the AIX SAMBA server is still part of the nt40 domain. Explanation: I can however, map /

On Wed, 2019-02-13 at 23:58 -0600, shivappa Sangapur via samba wrote: > Hi, > > I'm using samba-4.7.x > I have some confusions over "map to guest=" options with setting SMB > Signing >  > > I want to understand why in case of *#2 and #5* it is not opening > shares of > my smb-4.7.x shares, > This is probably a case we haven't really

I just noticed that smbclient from Samba 4.9.4 /built by myself) on FreeBSD 11.2 coredumps when called like this: smbclient -L <hostname> > % /liu/pkg/samba/4.9.4-liu/bin/smbclient -L filur00 > Enter username at AD.LIU.SE's password: > Abort (core dumped) … if it is linked against /usr/local/lib/libmd5.so (which is part of “libwww”). If I remove libmd5.so and recompile

> hi all, > > my working samba-4.1.7 member of a samba3 domain (samba-3.5.3) failed > while updating to samba-4.2.0. Users were no longer able to access > shares because the trust account was broken. > > According to release notes (Winbindd/Netlogon improvements): > > For the client side we have the following new options: > "require strong key" (yes by

Hi, I'm using samba-4.7.x I have some confusions over "map to guest=" options with setting SMB Signing 1. Set "*Server signing =auto*", "*map to guest=bad uid*" and set "client signing in windows 2k12 server group policy" to "Microsoft network client: Digitally sign communications (Always)” = *Disable*" SMB_Server is joined to Windows 2k12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Some people might find this discussion about upcoming changes in 3.0.22 interesting. It might also be helpful to get some feedback from the field on the ramifications of the changes. cheers, jerry ===================================================================== I live in a Reply-to-All world ----------------------- Samba

I'm running Centos 4.3 and Samba 3.0.24. I have an OpenLDAP backend. I have successfully got a Windows Domain to work, Windows XP -> Samba -> OpenLDAP. I can add machines to the domain and I can login and change passwords. The trouble is that I'm using NTLM and have been told that I must upgrade to NTLMv2, but I'm having great difficulty doing so. I have existing NTLM users. I

Fixup patch, addressing Andrew's review feedback: Signed-off-by: Kent Overstreet <kmo at daterainc.com> --- include/linux/idr.h | 2 +- lib/idr.c | 38 +++++++++++++++++++++----------------- 2 files changed, 22 insertions(+), 18 deletions(-) diff --git a/include/linux/idr.h b/include/linux/idr.h index f0db12b..cdf39be 100644 --- a/include/linux/idr.h +++

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've a machine, and users if granted permission work, but if I grant a group permissions, the user can't get access, even though both winbind and getent report that he is in that group. Examples: [CAD_BU2] ~ comment = CAD_BU ~ path = /mnt/H05/CAD_BU ~ valid users = @THG+mis_group ~ admin users = @THG+mis_group ~

Parse the output disk as URI, and use all its attributes just like it is done for the input disk. The only change is that the fsync of the output disk is limited now for local URIs only, since it will not work with remote protocols. --- resize/resize.ml | 56 ++++++++++++++++++++++++++++++++++---------------- resize/virt-resize.pod | 6 +++--- 2 files changed, 41 insertions(+), 21

When structured replies are negotiated, the server may advertise support for the DF flag (the server promises to return at most one data/hole chunk, or to fail with NBD_EOVERFLOW if the chunk would be too large). As both nbdkit and qemu-nbd support this flag (the former only trivially, but the latter by not compressing holes over the wire), it is worth exposing to clients, if only for testing

On Fri, 16 Aug 2013 23:09:06 +0000 "Nicholas A. Bellinger" <nab at linux-iscsi.org> wrote: > From: Kent Overstreet <kmo at daterainc.com> > > Percpu frontend for allocating ids. With percpu allocation (that works), > it's impossible to guarantee it will always be possible to allocate all > nr_tags - typically, some will be stuck on a remote percpu

On Fri, 16 Aug 2013 23:09:06 +0000 "Nicholas A. Bellinger" <nab at linux-iscsi.org> wrote: > From: Kent Overstreet <kmo at daterainc.com> > > Percpu frontend for allocating ids. With percpu allocation (that works), > it's impossible to guarantee it will always be possible to allocate all > nr_tags - typically, some will be stuck on a remote percpu

PLEASE!! can somebody help me? I need much these! ----- Original Message ----- From: "Henrique" <henrique@astuto.com.br> To: "Samba Samba" <samba@lists.samba.org> Sent: Monday, June 21, 2004 3:35 PM Subject: Error C000019B > Hi everyone! im having problems with Samba 3.0.4 > > My PDC is samba+openldap+nss+pam+smbldaptools > > All work fine (posix

Hi, I'm attempting to get my server set up to share out files using Active Directory authentication. I also have winbind set up for shell logins to the server. That part works fine, but when I attempt to connect to a samba share with smbclient, I get rejected with "session setup failed: NT_STATUS_LOGON_FAILURE". I did some searching and found others with similar issues, and I

Hi, First off, I apologize if this email goes through twice. I sent it about an hour ago, but it appears to have never made it to the list, so I'm sending again. I'm attempting to get my server set up to share out files using Active Directory authentication. I also have winbind set up for shell logins to the server. That part works fine, but when I attempt to connect to a samba

From: Ville Syrjälä <ville.syrjala at linux.intel.com> Make life easier for drivers by simply passing the connector to drm_hdmi_avi_infoframe_from_display_mode() and drm_hdmi_avi_infoframe_quant_range(). That way drivers don't need to worry about is_hdmi2_sink mess. v2: Make is_hdmi2_sink() return true for sil-sii8620 Adapt to omap/vc4 changes Cc: Alex Deucher

On Tue, 20 Nov 2018, Ville Syrjala <ville.syrjala at linux.intel.com> wrote: > From: Ville Syrjälä <ville.syrjala at linux.intel.com> > > Make life easier for drivers by simply passing the connector > to drm_hdmi_avi_infoframe_from_display_mode() and > drm_hdmi_avi_infoframe_quant_range(). That way drivers don't > need to worry about is_hdmi2_sink mess. Overall

From: Ville Syrjälä <ville.syrjala at linux.intel.com> Make life easier for drivers by simply passing the connector to drm_hdmi_avi_infoframe_from_display_mode() and drm_hdmi_avi_infoframe_quant_range(). That way drivers don't need to worry about is_hdmi2_sink mess. Cc: Alex Deucher <alexander.deucher at amd.com> Cc: "Christian König" <christian.koenig at amd.com>