similar to: Apparent bug remains in v4.0.7 - Hosts allow parameter causing errors and vey slow MS Office document access

I wanted to bring attention to some odd behavior which I don't believe is intentional. With Samba running, I can go to a Windows machine on the network (10.0.0.0/24) and see all of the Samba shares by pulling up an Explorer window and going to \\Server1 Everything appears to work as expected. However, if I populate the 'hosts allow' parameter within smb.conf as follows: hosts allow

I've been trying to join Samba 4.05 stable to an existing Windows 2000 domain but keep getting an LDAP error 50 - LDAP_INSUFFICIENT_ACCESS_RIGHTS despite attempting to joining with the Windows administrator account. I did a capture of the network traffic generated by the failure for more information on what's going on and discovered the following: First Samba does an LDAP ROOT bind

I'm trying to join an existing domain as an additional domain controller but I keep getting errors. Existing domain controller is an old Win2K server named 'Server'. [root at Server1 samba4]# samba-tool domain join HERSCHLAUREN DC -U administrator --realm=HERSCHLAUREN.COM Finding a writeable DC for domain 'HERSCHLAUREN' Found DC SERVER.HERSCHLAUREN Failed to connect to

Hi guys I have setup a NT4 Domain, using Freeipa as a ipasam backend... Normal user authentication and shares seems to work, but i'm getting an error when trying to join a Windows 7 machine to the domain (see below)... To me it seems to be the same error as here: https://bugzilla.samba.org/show_bug.cgi?id=11245.... Does anyone know if this patch have been implemented in the samba in

Hello, Running Samba 3.3.10 on FreeBSD 7.3. Cannot copy a folder with a subfolder and 10 files in the subfolder from an OSX 10.6.4 client to a folder on the Samba server. What happens is that the folder gets copied but not the subfolder and its files. root at aries:/usr/local/etc# testparm Load smb config files from /usr/local/etc/smb.conf Processing section "[homes]" Processing

Hi! I'm using Samba in an AD setup, (version 4.2.0) and I'm looking for a way to change the password of a user from the command line, as a non-root user. I know I can use 'smbpasswd', 'samba-tool user setpassword', or 'samba-tool user password', but these all seem to require root privileges. When I run them as root, they work, but when I run them as non-root

Since version 3.0.23b, I have been having trouble getting Windows & OSX users to access an NT domain member server running FreeBSD 5.4. It is now at 3.0.23c (installed this morning the 5th). root@aries:/usr/local/lib# net rpc user Password: Could not connect to server 127.0.0.1 Connection failed: NT_STATUS_NO_LOGON_SERVERS root@aries:/usr/local/lib# net rpc user Password: Could not connect

Hi Roel, > I'm using Samba in an AD setup, (version 4.2.0) and I'm looking for a > way to change the password of a user from the command line, as a > non-root user. > > I know I can use 'smbpasswd', 'samba-tool user setpassword', or > 'samba-tool user password', but these all seem to require root > privileges. When I run them as root, they

>> >> This is my nsswitch file: >> >> >> passwd: files ldap compat winbind >> group: files ldap compat winbind >> shadow: files ldap compat > > Do you have anything that needs to connect via LDAP ? > If you have what it is it ? > I would remove 'ldap' > > 'files' and 'compat' basically

Hi folks, Can anyone shed light on this issue? I haven't heard from you guys. Is there anything else I could do to expedite resolution of this issue? I've read the WHATSNEW.txt and reviewed the release notes. I am not sure if I've fully grasped what needs to be done. Can someone point me in the right direction? ~Doug -----Original Message----- From: Doug Sampson

I'm trying to get a FreeBSD 5.4 server to join a NT4 domain as a member domain server using winbindd. I've compiled Samba with WinBIND support, ACL Support, Syslog support, UTMP support, SMB PAM module, and with installed POPT library. I've reviewed Chapter 20 of TOSHARG and implemented a good portion of it into our smb.conf file but am having trouble making the 'getent'

Hi, I have a shorewall v4.0.7 installation on an older version of fedora. What is the proper way to add another network to the DMZ interface? Is it through virtual networks? If so, how is that done, given I''ve already designed the system around a single network on the DMZ? I have two physical interfaces on the firewall, with eth0 for external (192.168.1.0) and eth1 for the DMZ

I posted my original post to FreeBSD-questions@freebsd.org and since then have had a running dialog with another poster. It now seems I am having trouble with the NSSWITCH function. I am now reporting back to the Samba list in hopes someone can help me out at this point. Can anyone help me out here? ~Doug -----Original Message----- Sent: Friday, September 16, 2005 12:48 PM To: 'Dan

Hi , We have configured and run SAMBA-4.5 AD DC on Itanium HP UX 11iv3. We have tried to join the windows server 2008 DC to samba AD with the steps mentioned in the below link https://wiki.samba.org/index.php/Joining_a_Windows_Server_ 2008_/_2008_R2_DC_to_a_Samba_AD While i am trying to execute the steps mentioned in section "Joining the Windows Server to the Domain" 1.

Hello We are trying to implement SSO with mod_auth_ntlm_winbind. We followed the instructions on [1], but have the issue that users can not authenticate with web browsers. In addition to that document we did the following extra steps: - chown root:winbind /var/lib/samba/winbindd_privileged/ - apache user (vagrant) is in group winbind - net setauthuser -U vagrant - smb.conf has: winbind use

Our domain controllers have run samba 4.4.3 since it was released. We didn't upgrade because it was so stable :) I recently decided that release was too old and upgraded to 4.8.2 (then current). Our domain controllers were crashing on 4.8.2 so I upgraded to 4.8.3 as soon as it was released but this has not resolved the issue. When the issue occurs the DC becomes unresponsive and needs to be

I'm workign to setup Samba4 and my current centos server deployment uses TinyDNS/DNSCache for the DNS. Understanding that it is best to use Sambas internal DNS for AD, I'm wondering how others are doing DNS? I really don't want to use BIND. Should my DHCP server send ddns updates to Samba's internal DNS for client leases? Thanks, -- Greg J. Zartman Board Member Koozali

Release Announcements --------------------- This is the fourth release candidate of Samba 4.0. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.0 will be the next version of the Samba suite and incorporates all the technology found in both the Samba4

Release Announcements --------------------- This is the fourth release candidate of Samba 4.0. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.0 will be the next version of the Samba suite and incorporates all the technology found in both the Samba4

Am 26.02.19 um 12:26 schrieb Ralph Böhme: > On Tue, Feb 26, 2019 at 11:19:45AM +0100, Alexander Spannagel via samba > wrote: >> The huge delays are seen, when user isn't known to sssd and winbind >> tries to look that user without explicitly a domain given and the >> option "winbind use default domain" is on it's default of "No" in >>