similar to: Q: Samba AD, Pfsense, Windows 10, vpn

Your pfSense firewall has OpenVPN built into it already, and you can point pfSense authentication back to your samba AD. We support over 400 users in this model. The configuration file for OpenVPN is common to all users, and they authenticate with their AD credentials. > On Mar 14, 2020, at 7:21 AM, Michael Howard via samba <samba at lists.samba.org> wrote: > > On 14/03/2020

On 14/03/2020 13:53, Marco Shmerykowsky via samba wrote: > > Probably not the best place to ask, but hopefully > someone can point me in the right direction. > > I have a tiny business.? We use Samba for file sharing > and authentication in an AD setup.? I'm running a > pfsense appliance firewall.? NAT on the internal > network. > > Is there a way to allow

On 17/09/2020 21:33, Marco Shmerykowsky via samba wrote: > On 2020-09-16 1:49 pm, Rowland penny via samba wrote: >> On 16/09/2020 17:34, Marco Shmerykowsky via samba wrote: >>> I followed the instructions on the OpenVPN site for creating >>> the bind user: >>> >>>

> Am 15.03.2020 um 08:21 schrieb S?rgio Basto via samba <samba at lists.samba.org>: > > ?On Sat, 2020-03-14 at 07:43 -0700, gabben via samba wrote: >> Your pfSense firewall has OpenVPN built into it already, and you can >> point pfSense authentication back to your samba AD. We support over >> 400 users in this model. The configuration file for OpenVPN is common

> This is just another user like anyone else in the office. No, its offcourse not .. Why do you think you binding user is failing ;-) So, on the bind fail. Did you set on the "binding" user, : account is trusted and cant not be delegated? Password can be changed and never expire need to be ticked also. Whats set on the Pfsence server in ldap.conf ? Is BASE and URI defined? As

I only have some experience with OPNsense but maybe you can relate: - In my case it was always the certificate.? - I had to add the cert to the system certs using CLI. Adding them in the WebGUI was not enough. - Port 636 did not work for me, only 389 using STARTTLS Hope that helps... On 16. March 2020 at 08:13:50, Stefan G. Weichinger via samba (samba at lists.samba.org) wrote: Am 15.03.20 um

A little off topic, but this does revolve around Samaba. I'm hoping someone can help me get to a working aolution. I haven't been able to find a clear quide, but it must have been done by others. I'm trying to use setup a VPN using OpenVPN on Pfsense with authentication via my Samba AD (Version 4.9.4-Debian) I keep getting a "Could not connect to LDAP server" error when

On 16/09/2020 17:34, Marco Shmerykowsky via samba wrote: > I followed the instructions on the OpenVPN site for creating > the bind user: > > https://openvpn.net/vpn-server-resources/openvpn-access-server-on-active-directory-via-ldap/#Create_and_configure_a_bind_user > OK after reading the supplied link, I think I see where the miss-understanding is coming from. Under the heading

I've been trying to setup OPENVPN on a Netgate appliance running pfsense. Initially, the authentication server I created appears to function. A connection is made, the "bind" is completed and the organizational units are fetched from the server and returned. A few minutes later - without making any changes - the same test returns the following errors: php-fpm 67757

On 2020-09-01 1:36 pm, Stefan G. Weichinger via samba wrote: > Am 01.09.20 um 19:07 schrieb Marco Shmerykowsky via samba: >> A little off topic, but this does revolve around >> Samaba. >> >> I'm hoping someone can help me get to a working aolution. >> I haven't been able to find a clear quide, but it must >> have been done by others. >>

In lieu of virtualization, I wouldn't be opposed to some small, inexpensive appliance type device (sort of like the Netgate firewalls that run pfsense). I came across the MintBox Mini Pro (http://www.fit-pc.com/web/products/mintbox/mintbox-mini-pro/) Any experience or alternate suggestions? On Fri, May 25, 2018 2:27 pm, Robert Marcano via samba wrote: > On 05/25/2018 12:54 PM, Marco

Yes, went thru that page a few times and don't see an obvious error. If I leave require strong auth as the default, then nothing works. Setting it to no allows diagnostics->authentication to return a positive result. That is also the configuration that would succeed in querying the containers. Without the 'no' setting it fails to bind. What am i missing? On September 1, 2020

On 2020-09-15 1:13 pm, miguel medalha wrote: >> I've tried restarting PHP-FPM and webconfigurator, >> but that doesn't seem to solve the problem. > > This must be done each time after you edit the configuration using the > LDAP > authentication setup page. Otherwise the changes won't stick. Before I > knew > this, I did suffer a lot trying to make it

Am 15.03.20 um 10:46 schrieb Christian Naumer via samba: > > >> Am 15.03.2020 um 08:21 schrieb S?rgio Basto via samba <samba at lists.samba.org>: >> >> ?On Sat, 2020-03-14 at 07:43 -0700, gabben via samba wrote: >>> Your pfSense firewall has OpenVPN built into it already, and you can >>> point pfSense authentication back to your samba AD. We

On Sat, May 26, 2018 at 02:47:24PM +0100, Rowland Penny via samba wrote: > On Sat, 26 May 2018 09:21:01 -0400 > Marco Shmerykowsky via samba <samba at lists.samba.org> wrote: > > > > > In lieu of virtualization, I wouldn't be opposed to some > > small, inexpensive appliance type device (sort of like > > the Netgate firewalls that run pfsense). > >

Is it possible to connect networks with different masks together? For example a 10.26.0.0/16 subnet with a 192.168.117.0/24 subnet. See this thread for more details... https://forum.netgate.com/topic/134218/tinc-initial-setup

On 2020-09-15 4:19 pm, Rowland penny via samba wrote: > On 15/09/2020 20:53, Marco Shmerykowsky via samba wrote: >> On 2020-09-15 1:13 pm, miguel medalha wrote: >>>> I've tried restarting PHP-FPM and webconfigurator, >>>> but that doesn't seem to solve the problem. >>> >>> This must be done each time after you edit the configuration using

I'm setting up a VPN using Samba's AD for user authentication. Everything seems to check out on the PFsense side. Authentication is reported as successful, but when I try to connect to the actual network, I get: "Certificate does not have key usage extension." "certificate verify failed" Is this an issue with samba's self generated certificates or I should I be

Am 16.03.20 um 09:02 schrieb Alexander Harm via samba: > > I only have some experience with OPNsense but maybe you can relate: > > - In my case it was always the certificate.? > - I had to add the cert to the system certs using CLI. Adding them in the WebGUI was not enough. > - Port 636 did not work for me, only 389 using STARTTLS > > Hope that helps... Ah, yes, thanks.

I just realized that some of my Windows 10 clients do not appear to be syncing the time correctly. I setup NTP to run on my Netgate PFSense server. It is using pfsense.pool.ntp.org Time Servers. I configured NTP on my Samba servers to point to back to the PFSense Server. NTP on the samba servers have the following ntp.conf files: # /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for