similar to: WinbinD no longer available in Samba 4.7.6

On Tue, 4 Dec 2018 09:59:14 +0100 "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > Hai, > > > -----Oorspronkelijk bericht----- > > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > > Konstantin Boyandin via samba > > Verzonden: dinsdag 4 december 2018 6:35 > > Aan: samba at lists.samba.org > > Onderwerp:

On Tue, 04 Dec 2018 16:44:55 +0700 Konstantin Boyandin via samba <samba at lists.samba.org> wrote: > Rowland Penny via samba писал 2018-12-04 16:28: > > On Tue, 4 Dec 2018 09:59:14 +0100 > > "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > > > >> Hai, > >> > >> > -----Oorspronkelijk bericht----- >

L.P.H. van Belle via samba писал 2018-12-04 15:59: > Hai, > >> -----Oorspronkelijk bericht----- >> Van: samba [mailto:samba-bounces at lists.samba.org] Namens >> Konstantin Boyandin via samba >> Verzonden: dinsdag 4 december 2018 6:35 >> Aan: samba at lists.samba.org >> Onderwerp: [Samba] WinbinD no longer available in Samba 4.7.6 >> >>

Hai, > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Konstantin Boyandin via samba > Verzonden: dinsdag 4 december 2018 6:35 > Aan: samba at lists.samba.org > Onderwerp: [Samba] WinbinD no longer available in Samba 4.7.6 > > Hello, > > Using Samba 4.7.6 (from standard repository) on Ubuntu 18.04. > > After

Rowland Penny via samba писал 2018-12-04 16:28: > On Tue, 4 Dec 2018 09:59:14 +0100 > "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > >> Hai, >> >> > -----Oorspronkelijk bericht----- >> > Van: samba [mailto:samba-bounces at lists.samba.org] Namens >> > Konstantin Boyandin via samba >> > Verzonden: dinsdag 4

Rowland Penny via samba писал 2018-12-04 17:17: > On Tue, 04 Dec 2018 16:45:43 +0700 > Konstantin Boyandin via samba <samba at lists.samba.org> wrote: > >> >> Are there possibly missing some winbind settings (the smb.conf has >> been generated by domain upgrade process). >> > > Sorry, but I do not believe that is true: True. The configuration

Hello, After joining Windows 7 to a Samba 4 (AD), when logging on I experience 'Access denied' error accessing user profile. As a result, Windows creates temporary profile for the domain user (the profile is deleted upon logoff). The roaming profiles directory has been created according to instructions in https://wiki.samba.org/index.php/Roaming_Windows_User_Profiles Note: the home

Hi Team, On running make quicktest. I am stuck as wbinfo --ping-dc is from selftest/target/Samba3.pm is failing. Below is the code snipped from logs. *Socket opened.* *parse_nmb: packet id = 14795* *nmb packet from 127.0.0.3(137) header: id=14795 opcode=Query(0) response=Yes* * header: flags: bcast=No rec_avail=Yes rec_des=Yes trunc=No auth=Yes* * header: rcode=0 qdcount=0 ancount=1

I have an NT domain on Debian Stretch. It's been upgraded numerous times, but has been running for almost a decade. Since upgrading from 4.1.17 to 4.3.3 (huge Debian jump), then to 4.3.6, clients cannot connect to shares. Prior to upgrading, I found the changes mentioned for 4.2 regarding NT domains and applied them. Even so, I still cannot connect to network shares nor print to

You may have included this in another email however I will ask anyway, did you set DNS to your server in the Linux and Windows clients? Can you check if a Windows Server can join? Can you use DNS management to check the DNS on you samba server? On Mar 28, 2016 2:15 PM, "Dale Schroeder" <dale at briannassaladdressing.com> wrote: > No takers thus far. These are the Samba 4.2

Have a Linux Mint 19.1 with Samba 4.7.6 installed. Plan is to use this as a file server. Cannot connect from Windows 10. Win 10 sees the share but says group name could not be found. Everything worked on the previous Ubuntu machine. Any thoughts on where I should look? Tom Thomas Rieff GreenCare 1717 3rd Avenue Mankato, MN 56001

Hello, On 05.12.2018 15:36, Rowland Penny via samba wrote: >>>> Are there possibly missing some winbind settings (the smb.conf has >>>> been generated by domain upgrade process). >>>> >>> >>> Sorry, but I do not believe that is true: >> >> True. The configuration works. I assume that parameters that aren't >> applicable

I have a small home network with server and 5 clients all on an internal LAN with private IPs. Samba, Version 4.7.6-Ubuntu, file sharing is not working on the server for any of the 5 clients. I have tried both mount.cifs and smbclient. The same errors are thrown in the server's samba logs for all connection attempts, regardless of how the client tries to connect: getpwuid(1000) failed,

On Wed, 05 Dec 2018 09:57:56 +0700 Konstantin Boyandin via samba <samba at lists.samba.org> wrote: > Rowland Penny via samba писал 2018-12-04 17:17: > > On Tue, 04 Dec 2018 16:45:43 +0700 > > Konstantin Boyandin via samba <samba at lists.samba.org> wrote: > > > >> > >> Are there possibly missing some winbind settings (the smb.conf has >

Hello, In short: there's a Windows Server 2003 system, which worked without many problems with NT domain (Samba 3). The NT domain is being shut down, and I noticed I have hard time trying to befriend the mentioned system with AD run under Samba 4.7.6 (default on Ubuntu 18.04). Is the mentioned AD incompatible with Windows Server 2003? When trying to join, I get cryptic message about

On Tue, 04 Dec 2018 16:45:43 +0700 Konstantin Boyandin via samba <samba at lists.samba.org> wrote: > > Are there possibly missing some winbind settings (the smb.conf has > been generated by domain upgrade process). > Sorry, but I do not believe that is true: winbind enum users = yes winbind enum groups = yes The lines above should only be used for testing

Hello experts/users, We have a samba server in ubuntu 18.04 LTS with version. apt-cache policy samba samba: Installed: 2:4.7.6+dfsg~ubuntu-0ubuntu2.16 Candidate: 2:4.7.6+dfsg~ubuntu-0ubuntu2.16 All is fine and great. Except one (internet disabled) windows 7 professional PC (sorry we still need to run it for a scientific tool) cannot connect unless I put "ntlm auth = yes" in

Hello Marc, Thanks for your documentation. Well I followed what you wrote, perhaps my wbinfo command fails when I try to test the connectivity. # wbinfo --ping-dc checking the NETLOGON dc connection failed failed to call wbcPingDc: WBC_ERR_WINBIND_NOT_AVAILABLE Could not ping our DC My smb.conf is now this: # Global parameters [global] netbios name = DEVLUCAS1 realm =

Samba 4.7.6-ubuntu Using Ubuntu 18.04.1 LTS logging in, in AD Domain Hi, would like to know where or how i can define the TTL for the cached winbind offline logon. Actually it´s around a day, afterwards i can´t login in my AD-User when i´m still offline but would like to extend the time. Thanks. My smb.conf looks like this: [global] winbind enum users = yes winbind enum groups = yes winbind

I have a server which we use for backing up files. Noticed there was an upgrade available to 18.04.1. Now I cannot connect to from my win7 machine to the Ubuntu share. Any thoughts on what would have changed??? Tom