similar to: Large file (over 4Gb) transfer problem from Windows to Samba 4.7 on CentOS 7.5

>>> Installed Samba version [root at server ~]# rpm -qa | grep samba samba-client-libs-4.7.1-9.el7_5.x86_64 samba-winbind-modules-4.7.1-9.el7_5.x86_64 samba-dc-libs-4.7.1-9.el7_5.x86_64 samba-winbind-krb5-locator-4.7.1-9.el7_5.x86_64 samba-common-tools-4.7.1-9.el7_5.x86_64 samba-4.7.1-9.el7_5.x86_64 samba-devel-4.7.1-9.el7_5.x86_64 samba-winbind-4.7.1-9.el7_5.x86_64

Hi Rowland, I am testing lanman auth option as I cannot login to Samba server with correct samba user name & password I created Unix user & samba user .. but cannot login to Samba .. This is why I use this option to find a way to login to Samba Best Regards, Mr Linux CZ On Sun, Oct 7, 2018 at 9:30 PM Rowland Penny via samba <samba at lists.samba.org> wrote: > > On Sun, 7 Oct

On Sun, 7 Oct 2018 19:31:46 +0630 Mr Crack <mrcrack007 at gmail.com> wrote: > >>> Installed Samba version > [root at server ~]# rpm -qa | grep samba > samba-client-libs-4.7.1-9.el7_5.x86_64 > samba-winbind-modules-4.7.1-9.el7_5.x86_64 > samba-dc-libs-4.7.1-9.el7_5.x86_64 > samba-winbind-krb5-locator-4.7.1-9.el7_5.x86_64 > samba-common-tools-4.7.1-9.el7_5.x86_64

On Sun, 7 Oct 2018 22:48:29 +0630 Mr Crack <mrcrack007 at gmail.com> wrote: > Hi Rowland, > I am testing lanman auth option as I cannot login to Samba server with > correct samba user name & password > I created Unix user & samba user .. but cannot login to Samba .. > This is why I use this option to find a way to login to Samba > OK, lets look at your smb.conf

I am having trouble using the realtek wifi chip in my new tp-link usb wifi dongle. Upon plugging it, the device gets registered by the kernel (in /var/log/messages), but that's about it, no network device is being created (iwconfig does not see it, nothing else works). A few google searches later I found out that this realtek chip is not supported by the kernel and requires a driver, and that

when I do yum update, elrepo offers kmod-nvifdia, but yum does this: --> Processing Dependency: kernel(sme_me_mask) = 0x17fbce60 for package: kmod-nvidia-390.48-2.el7_5.elrepo.x86_64 --> Processing Dependency: kernel(reservation_object_add_excl_fence) = 0xea98efc0 for package: kmod-nvidia-390.48-2.el7_5.elrepo.x86_64 --> Processing Dependency: kernel(drm_vblank_init) = 0xdcd50a49 for

The server is using centos-release-7-6.1810.2.el7.centos.x86_64. After an automatic yum update on the morning of 4th December 2018 from samba-4.7.1-9.el7_5.x86_64 to samba-4.8.3-4.el7.x86_64 we can no longer scan from a Canon Aficio MP 301 to a network share (guest allowed). Scanning to windows machines works fine.

I've got a user with a legacy NVidia card. I've got kmod-nvidia. Last time I did an update, all I did was yum update --disableexcludes. This time, it fails, with Error: Package: nvidia-x11-drv-304xx-304.135-1.el7.elrepo.x86_64 (@elrepo) Requires: xorg-x11-server-Xorg <= 1.19.99 Removing: xorg-x11-server-Xorg-1.19.5-5.el7.x86_64 (@base)

C7, and I did a yum update --disableexcludes=all, and yet it's telling me [nvidia]: excluding kmod-nvidia-410.66-1.el7_5.elrepo.x86_64 [nvidia]: excluding kmod-nvidia-410.73-1.el7_5.elrepo.x86_64 [nvidia]: excluding kmod-nvidia-410.73-2.el7_6.elrepo.x86_64 [nvidia]: excluding kmod-nvidia-410.78-1.el7_6.elrepo.x86_64 [nvidia]: excluding kmod-nvidia-410.93-1.el7_6.elrepo.x86_64 [nvidia]:

Originally I posted this question at CentOS forum 20.12.2018. https://www.centos.org/forums/viewtopic.php?f=48&t=69193 Hi all, I am not able to mount samba shares after upgrading CentOS 7.5 to 7.6. I have been searching and trying to configure samba and winbind but no success. I find a lot of manuals and help pages about setting samba and winbind for machine acting as AD DC member but

I am install C7.5 on a nvidia unit and nvidia-detect tells me to use kmod-nvidia-390xx so I do the yum install and and after a long time I see this -> Processing Dependency: kernel(__drm_atomic_helper_crtc_duplicate_state) = 0xa5f3a170 for package: kmod-nvidia-390xx-390.87-2.el7_6.elrepo.x86_64 --> Processing Dependency: kernel(__drm_atomic_helper_crtc_destroy_state) = 0x00a9c70b for

Stephen Berg (Code 7309) wrote: > On 1/11/19 10:41 AM, mark wrote: > >> C7, and I did a yum update --disableexcludes=all, and yet it's telling >> me [nvidia]: excluding kmod-nvidia-410.66-1.el7_5.elrepo.x86_64 >> [nvidia]: excluding kmod-nvidia-410.73-1.el7_5.elrepo.x86_64 >> [nvidia]: excluding kmod-nvidia-410.73-2.el7_6.elrepo.x86_64 >> [nvidia]: excluding

I have setup a ADDC Samba server and a winbind member server I have see that same user have UID/GID different from ADDC and member server # Addc (Fedora 29)[root at s-addc ~]# id d.lescauid=3000023(DOM\d.lesca) gid=100(users) gruppi=100(users),3000023(DOM\d.lesca),3000009(BUILTIN\users)[ root at s-addc ~]# rpm -q sambasamba-4.9.2-0.fc29.x86_64 # Member (Centos7)[root at s-dati ~]# id

Hello Gentlemen. OK, Tests were made. I got some errors only when using Samba48 (samba47 is still fine) IMPORTANT: I forgot to mention... This is being used with SQUID Proxy for SSO authentication. Got NTLMSSP neg_flags=0xa2088207 Got user=[user01] domain=[MYDOMAIN] workstation=[ADCONTROL01] len1=24 len2=338 Login for user [MYDOMAIN]\[user01]@[ ADCONTROL01] failed due to [{Access Denied} A

Hello Everyone, Good evening! Here a Background: I am moving from samba47 to samba48 - I am keeping my existing scripts and config files. The messages below are now appearing while executing some tasks in samba48 only - samba47 is not showing it: #Unknown parameter encountered: "use spnego" #Ignoring unknown parameter "use spnego" #Unknown parameter encountered:

Hi: I have one samba 4.7/4.8 DC, one samba member file server (rhel 7.5 with samba 4.7.1), and one windows 7 member PC. if I create an account (my-account) in samba DC, I can not see it in the member server with "id my-account" or "getent passwd my-account". but if I use windows member PC to access the file server with my-account, then immediately "id

I have tried to upgrade our samba server from 3.6.18 to 3.6.22 but found that our DOS clients could no longer connect (using DOS 6.22 and Microsoft LAN Manager 2.1). With 3.6.18 we use smb.conf setting 'min protocol = LANMAN2' and it works great, with 3.6.22 although clients can connect ok, they cannot obtain a directory listing. Instead the first file (sometimes misnamed) just

Hi Rowland, Thanks Much for the help, as usual! About Kerberos: Yes, I have implemented Kerberos and NTLM. I need both working. About winbindd_privileged: Not sure what you mean with " I think you might want to check that again, the 'winbindd_privileged' dir went away quite some time ago." Shouldn't that folder be there anymore? Everytime I install Samba47 or 48 it creates

just checked the logs and i get this [root at localhost ~]# tail /var/log/samba/log.rnp00267380a647 [2018/12/05 11:27:36.333627,  0] ../lib/param/loadparm.c:1844(lpcfg_do_service_parameter)   Ignoring unknown parameter "profile acls" [2018/12/05 11:51:20.390991,  0] ../lib/param/loadparm.c:784(lpcfg_map_parameter)   Unknown parameter encountered: "profile acls" [2018/12/05

2018-07-19 23:59 GMT+08:00 Rowland Penny via samba <samba at lists.samba.org>: > > Please see inline comments. > > On Thu, 19 Jul 2018 23:44:48 +0800 > d tbsky <tbskyd at gmail.com> wrote: > >> thanks a lot for the quick help. I remember in old days it happened >> sometimes. but after upgrade rhel 7.5 (from samba 4.6.x to 4.7.1) and >> samba DC