Displaying 20 results from an estimated 2000 matches similar to: "How to set account lockout policy"
2018 Sep 03
4
Samba AD and DNS stopped on RSAT
Hi All,
I have live Samba AD DC running. Suddenly it stopped on RSAT. Both AD and
DNS not accessible. Please attached screen shots and help me out as it is
my live.
--
Vivek Patil
Assistant Manager - IT
Forgeahead Solutions
vivek.patil at forgeahead.io
*O* +91 (0) 20 66 44 5900 | *M *+91 9579 216 049
601 Zero One, Level 6, Mundhwa, Pune 411036, Maharashtra, India
*W* forgeahead.io *IN
2018 Sep 04
2
Samba AD and DNS stopped on RSAT
Hi Andrew,
Yes samba process still running. I can access my domain users on client
machine. I can add DNS record too using samba-tool. But I can not access
it's UI on RSAT.
-Vivek
On Tuesday, September 4, 2018, Andrew Bartlett <abartlet at samba.org> wrote:
> On Mon, 2018-09-03 at 12:33 +0530, Vivek Patil via samba wrote:
>> Hi All,
>>
>> I have live Samba AD DC
2018 Sep 07
2
An invalid directory pathname was passed
Hi,
No, I have nothing install or update anything on the server. I want to
fixed it first. I also not able to see the domain users using samba-tool
user list. I can see it using pdbedit -L.
On Fri, Sep 7, 2018 at 1:47 PM Rowland Penny via samba <
samba at lists.samba.org> wrote:
> On Fri, 7 Sep 2018 06:02:37 +0530
> Vivek Patil via samba <samba at lists.samba.org> wrote:
>
2018 Sep 11
2
Replace old AD to new
Hi All,
I have samba AD domain (mydomain.com). And my 60 windows clients are joined
to it. Now I have setup a AD DC with the same name (mydomain.com). New
domain has same IP, name as old.
Now I want to remove old server and put new server to network. How my
windows clients can authenticate with new domain without changing user
profile?
--
Vivek Patil
Assistant Manager - IT
Forgeahead Solutions
2018 Sep 03
2
Samba AD and DNS stopped on RSAT
No, this is my server conf. Please suggest how I can fixed this.
On Monday, September 3, 2018, Rowland Penny via samba <samba at lists.samba.org>
wrote:
> On Mon, 3 Sep 2018 23:44:49 +0530
> Vivek Patil <vivek.patil at forgeahead.io> wrote:
>
>> /usr/local/samba/etc/smb.conf
>>
>> # Global parameters
>> [global]
>> netbios name = UBUNTU
2018 Sep 03
2
Samba AD and DNS stopped on RSAT
Hi,
I have uploaded error images on following URL. Please check and guide me. M
stuck on my live env.
https://postimg.cc/image/5srwk7tud/
https://postimg.cc/image/oxv5tzg85/
I have my Samba on Ubuntu 14, and accessing it through RSAT.
On Mon, Sep 3, 2018 at 7:26 PM Rowland Penny via samba <
samba at lists.samba.org> wrote:
> On Mon, 3 Sep 2018 12:33:36 +0530
> Vivek Patil via
2018 Sep 07
2
An invalid directory pathname was passed
Suddenly the MMC snap-in "Active Directory Users and
Groups" stopped working. Attempting to access it fails with
The directory schema is not accessible because:
An invalid directory pathname was passed.
For this reason, the New menu may be inaccurate, and extension
snap-ins may not work properly.
- followed by -
Data from Active Directory Users and Computers is not available from
2018 Sep 04
2
Samba AD and DNS stopped on RSAT
Yes, i mixed up two thing that is confusing you. Well., I did nothing
change on the server. And the smb.conf file is shared here is only from
server. Do you need any more file output here.
On Tuesday, September 4, 2018, Rowland Penny via samba <
samba at lists.samba.org> wrote:
> On Tue, 4 Sep 2018 00:21:19 +0530
> Vivek Patil <vivek.patil at forgeahead.io> wrote:
>
>>
2018 Sep 03
2
Samba AD and DNS stopped on RSAT
/usr/local/samba/etc/smb.conf
# Global parameters
[global]
netbios name = UBUNTU
realm = MYDOMAIN.IO
workgroup = MYDOMAIN
dns forwarder = 8.8.8.8
allow dns updates = nonsecure and secure
server role = active directory domain controller
[netlogon]
path = /usr/local/samba/var/locks/sysvol/mydomain.io/scripts
read only = No
[sysvol]
2018 Sep 07
2
An invalid directory pathname was passed
No, windows automatically update is also disable. I even cant join my widows client to my domain. It says username or password invalid. I have 3 domain admin users, all got the same error. It's really very complicated for me, it is my live AD.
--Vivek P
________________________________
From: samba <samba-bounces at lists.samba.org> on behalf of Rowland Penny via samba <samba at
2018 Sep 04
1
Samba AD and DNS stopped on RSAT
On Tue, 4 Sep 2018 07:04:37 +0530
Vivek Patil via samba <samba at lists.samba.org> wrote:
> Windows join to Samba AD fails, says
>
> The following error occurred attempting to join the domain "domain.io"
> Logon failure: unknown user name or bad password.
>
> I test on Samba server:
> $sudo kinit administrator at MYDOMAIN.IO
>
> $klist
> Ticket
2018 Sep 07
2
An invalid directory pathname was passed
ubuntu at Ubunut:~$ sudo samba-tool dbcheck
Checking 264 objects
Checked 264 objects (0 errors)
On Fri, Sep 7, 2018 at 2:33 PM Rowland Penny via samba <
samba at lists.samba.org> wrote:
> On Fri, 7 Sep 2018 08:41:27 +0530
> Vivek Patil <vivek.patil at forgeahead.io> wrote:
>
> > Hi,
> >
> > No, I have nothing install or update anything on the server. I
2018 Sep 04
0
Samba AD and DNS stopped on RSAT
Windows join to Samba AD fails, says
The following error occurred attempting to join the domain "domain.io"
Logon failure: unknown user name or bad password.
I test on Samba server:
$sudo kinit administrator at MYDOMAIN.IO
$klist
Ticket cache: FILE:/tmp/krb5cc_1000
Default principal: administrator at MYDOMAIN.IO
Valid starting Expires Service principal
2018 Sep 11
2
Replace old AD to new
Hi,
In my case, there are lot off issue with my old server. not able to join my
windows clients to domain using old server. Thats why I have setup new
server with same domain, manually create all the users in it.
And now I wanna put new to network and remove old.
On Tue, Sep 11, 2018 at 12:47 PM Oliver Rath via samba <
samba at lists.samba.org> wrote:
> Hi Vivek,
>
> the
2018 Sep 09
0
An invalid directory pathname was passed
Hi,
Can you please suggest me to fixed this issue. I even not able to join my
windows client to Samba AD. It says username unknown or bad password. I
tried it with 3 domain admin user accounts.
Please please help me, its my live environment. All new clients are getting
affected.
On Fri, Sep 7, 2018 at 9:50 PM Vivek Patil <vivek.patil at forgeahead.io>
wrote:
> No, windows
2018 Sep 07
2
An invalid directory pathname was passed
No, we didn't change on the ADUC. Actually now I am not able to manage users through ADUC. It says access denied. I checked my admin user with kinit and found no issue.
--Vivek P
________________________________
From: samba <samba-bounces at lists.samba.org> on behalf of Rowland Penny via samba <samba at lists.samba.org>
Sent: Friday, September 7, 2018 4:02:05 PM
To: samba at
2014 Aug 01
2
Account lockout feature
First of all, I want to say I have been using Samba AD for two years now (since just before 4.0 went stable), and it is an amazing product. We've implemented Active Directory & Group Policy for almost 50 computers and 100 users.
Unfortunately, we are now being forced into switching to Windows DCs because Samba does not have an account lockout feature.
Citrix (stupidly) does not have
2013 Jan 12
3
Samba4 Domain Account Lockout
First off, I apologize if this is a duplicate - I had some issues with the first email I tried to join this list with!
I'm currently using samba4 as an AD DC (domain and forest are both configured with the samba-tool command to be at the 2008_R2 functional level) for both Windows and Linux systems. I've got the default password settings set using the "samba-tool domain
2014 Mar 20
1
Account Lockout policies are not working in samba 4.1.5
Hello,
I have a samba 4.1.5. I have created OUs and linked GPO to OU for account
lockout policies.
Account Lockout Duration: 15min
Account Lockout Threshold: 5 invalid attempts
Reset Account lockout counter after: 15min
I have created a test account and logged in with an incorrect password more
than 5 times to a machine. but the test account never locks and the computer
never prompts me that
2007 Sep 12
1
Clearing account lockout
I recently am migrating my PDC from NT4 to Samba 3.025. Apparently due to a
mismatch between the capitalization of the Windows account and the Unix
account (Administrator vs administrator) I managed to lock the account
before catching the discrepenacy.
# pdbedit -v administrator
Unix username: Administrator
NT username: Administrator
Account Flags: [ULX
Bad password count