Displaying 20 results from an estimated 38 matches for "labrat".
2019 Mar 04
4
getent not working after installing firewall
...8.0.0
> > * 255.255.255.0 U 202 0 0 eth0
> >
> > > hostname -s
> > > hostname -d
> > > hostname -i
> > > hostname -I
> > >
> > > Do they show what you expect ?
> >
> > On the domain member (labrat):
> >
> > $ hostname -s
> > labrat
> >
> > $ hostname -d
> > hprs.local
> >
> > $ hostname -i
> > 127.0.0.1
> >
> > $ hostname -I
> > hostname: invalid option -- 'I'
> >
> > I believe these show as exp...
2016 Sep 09
2
Not authentication on Slackware domain member
...d PAM and followed the instructions in
https://wiki.samba.org/index.php/Setup_Samba_as_an_AD_Domain_Member.
I can successfully do `wbinfo -u` and `getent passwd userID`. But, when I try to log I get:
$ su - mark
Password:
su: Authentication failure
In my /var/log/secure I have:
Sep 8 22:59:34 labrat su[1396]: Authentication failed for mark
Sep 8 22:59:34 labrat su[1396]: FAILED su for mark by mfoley
Sep 8 22:59:34 labrat su[1396]: - /dev/pts/0 mfoley:mark
I'm suspecting PAM. The Slackware PAM did not ship with a /etc/pam.d directory so I used the
one from the wiki website. That one did...
2019 Mar 04
2
getent not working after installing firewall
...; >
> > > > > hostname -s
> > > > > hostname -d
> > > > > hostname -i
> > > > > hostname -I
> > > > >
> > > > > Do they show what you expect ?
> > > >
> > > > On the domain member (labrat):
> > > >
> > > > $ hostname -s
> > > > labrat
> > > >
> > > > $ hostname -d
> > > > hprs.local
> > > >
> > > > $ hostname -i
> > > > 127.0.0.1
> > > >
> > > > $...
2019 Mar 04
2
getent not working after installing firewall
...0 eth0
loopback * 255.0.0.0 U 0 0 0 lo
192.168.0.0 * 255.255.255.0 U 202 0 0 eth0
> hostname -s
> hostname -d
> hostname -i
> hostname -I
>
> Do they show what you expect ?
On the domain member (labrat):
$ hostname -s
labrat
$ hostname -d
hprs.local
$ hostname -i
127.0.0.1
$ hostname -I
hostname: invalid option -- 'I'
I believe these show as expected (except for -I). Agreed?
> What is in /etc/resolv.conf
On AD/DC (MAIL 192.168.0.2, is the LAN DNS server):
domain hprs.local
sea...
2019 Mar 04
0
getent not working after installing firewall
...U 202 0 0 eth0
> > >
> > > > hostname -s
> > > > hostname -d
> > > > hostname -i
> > > > hostname -I
> > > >
> > > > Do they show what you expect ?
> > >
> > > On the domain member (labrat):
> > >
> > > $ hostname -s
> > > labrat
> > >
> > > $ hostname -d
> > > hprs.local
> > >
> > > $ hostname -i
> > > 127.0.0.1
> > >
> > > $ hostname -I
> > > hostname: invalid option --...
2019 Mar 04
0
getent not working after installing firewall
...stname -s
> > > > > > hostname -d
> > > > > > hostname -i
> > > > > > hostname -I
> > > > > >
> > > > > > Do they show what you expect ?
> > > > >
> > > > > On the domain member (labrat):
> > > > >
> > > > > $ hostname -s
> > > > > labrat
> > > > >
> > > > > $ hostname -d
> > > > > hprs.local
> > > > >
> > > > > $ hostname -i
> > > > > 127.0.0.1...
2018 Jun 06
2
Why am I getting login failures for domain members?
...09:27:36 -0400
Organization: Ohio Highway Patrol Retirement System
To: samba at lists.samba.org
Subject: [Samba] Why am I getting login failures for domain members?
Every so often I get a message in /var/log/samba/log.samba as follows:
2018/05/26 13:44:25.172415, 2] authentication for user [HPRS/LABRAT$] FAILED with error NT_STATUS_WRONG_PASSWORD
Normally, I get this when a user types in the wrong password. However, in this case LABRAT$ is
not a user but rather a Linux domain member computer. This happens periodically on every Linux
domain member on the domain.
Why? Is it a problem? Is there...
2018 May 29
3
Error IIS
HI!
The strange thing is that the problem (error in the logs) only runs when
the authentication trigger comes from IIS ....
Not the problem in DC, authentication via Windows machines or Winbind
(other servers) all working.
What procedures do you want to help? Do we procdir some data loss or
something?
Which procedure to open the bug?
Thank you.
On 29-05-2018 01:08, Andrew Bartlett wrote:
2016 Apr 12
2
Slow reading of large dovecot-uidlist files
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, 12 Apr 2016, Bostjan Skufca wrote:
> On 12 April 2016 at 10:23, A.L.E.C <alec at alec.pl> wrote:
>
>> I don't know dovecot's code, but I suppose it uses uidlist file to get
>> mailbox statistics that it returns as EXISTS, RECENT, UNSEEN, UIDNEXT,
>> UIDVALIDITY, etc, which are required by IMAP standard. I
2019 Mar 04
3
getent not working after installing firewall
...> > hostname -d
> > > > > > > hostname -i
> > > > > > > hostname -I
> > > > > > >
> > > > > > > Do they show what you expect ?
> > > > > >
> > > > > > On the domain member (labrat):
> > > > > >
> > > > > > $ hostname -s
> > > > > > labrat
> > > > > >
> > > > > > $ hostname -d
> > > > > > hprs.local
> > > > > >
> > > > > > $ hostna...
2016 Sep 09
0
Not authenticating on Slackware domain member
...d PAM and followed the instructions in
https://wiki.samba.org/index.php/Setup_Samba_as_an_AD_Domain_Member.
I can successfully do `wbinfo -u` and `getent passwd userID`. But, when I try to log I get:
$ su - mark
Password:
su: Authentication failure
In my /var/log/secure I have:
Sep 8 22:59:34 labrat su[1396]: Authentication failed for mark
Sep 8 22:59:34 labrat su[1396]: FAILED su for mark by mfoley
Sep 8 22:59:34 labrat su[1396]: - /dev/pts/0 mfoley:mark
I'm suspecting PAM. The Slackware PAM did not ship with a /etc/pam.d directory so I used the
one from the wiki website. That one did...
2019 May 27
4
samba-tool group removemembers, not working
...sues using ADUC, I tried to remove a domain member using:
> samba-tool group removemembers "Domain Computers" MARKA\$
Removed members from group Domain Computers
As shown, it say it "Removed members", but ...
> samba-tool group listmembers "Domain Computers"
:
LABRAT$
:
OHPRSSTORAGE$
MARKA$
:
COMMON$
:
listmembers still shows the computer as a member of "Domain Computers". What's up with this?
Samba Version 4.8.2
THX --Mark
2016 Jan 19
0
Samba AD/DC, Single-Sign-On, domain users cannot change password
...adow: compat
hosts: files dns
networks: files
protocols: db files
services: db files
ethers: db files
rpc: db files
netgroup: nis
With common-passwords as shown, if I try changing a domain user's password using `passwd` I get:
mark at labrat:~$ passwd
Current Kerberos password: (correct domain pw)
Current Kerberos password: (correct domain pw)
passwd: Authentication token manipulation error
passwd: password unchanged
I get this if I type the correct domain password each time at the "Current Kerberos password"
prompt. However...
2019 Mar 04
0
getent not working after installing firewall
...255.0.0.0 U 0 0 0 lo 192.168.0.0
> * 255.255.255.0 U 202 0 0 eth0
>
> > hostname -s
> > hostname -d
> > hostname -i
> > hostname -I
> >
> > Do they show what you expect ?
>
> On the domain member (labrat):
>
> $ hostname -s
> labrat
>
> $ hostname -d
> hprs.local
>
> $ hostname -i
> 127.0.0.1
>
> $ hostname -I
> hostname: invalid option -- 'I'
>
> I believe these show as expected (except for -I). Agreed?
Sorry, but no, '127.0.0.1' is...
2018 May 29
0
Why am I getting login failures for domain members?
Every so often I get a message in /var/log/samba/log.samba as follows:
2018/05/26 13:44:25.172415, 2] authentication for user [HPRS/LABRAT$] FAILED with error NT_STATUS_WRONG_PASSWORD
Normally, I get this when a user types in the wrong password. However, in this case LABRAT$ is
not a user but rather a Linux domain member computer. This happens periodically on every Linux
domain member on the domain.
Why? Is it a problem? Is there...
2018 Jun 06
0
Why am I getting login failures for domain members?
...: Ohio Highway Patrol Retirement System
> To: samba at lists.samba.org
> Subject: [Samba] Why am I getting login failures for domain members?
>
> Every so often I get a message in /var/log/samba/log.samba as follows:
>
> 2018/05/26 13:44:25.172415, 2] authentication for user [HPRS/LABRAT$] FAILED with error NT_STATUS_WRONG_PASSWORD
>
> Normally, I get this when a user types in the wrong password. However, in this case LABRAT$ is
> not a user but rather a Linux domain member computer. This happens periodically on every Linux
> domain member on the domain.
>
> Why...
2016 Jan 15
4
Samba AD/DC, Single-Sign-On, domain users cannot change password
On January 14, 2016 at 12:16 Rowland Penny wrote:
> Using 'passwd' does work, but pam has to be setup correctly and you
> cannot change the password on the first day unless you change the
> minimum password age to '0'
You answer piles of questions on this list, so you may not remember, but you helped me set this
whole domain-member/single logon thing last October. The
2019 Mar 04
2
getent not working after installing firewall
On Mon, 4 Mar 2019 14:50:38 +0000 Rowland Penny wrote:
>
> On Mon, 04 Mar 2019 09:15:12 -0500
> Mark Foley via samba <samba at lists.samba.org> wrote:
>
> > I have a rather strange and urgent problem. Last evening I installed
> > a Sonicwall firewall between the Internet and office LAN. The only
> > change that I know of for the LAN workstations was that the
2018 Jun 07
2
Why am I getting login failures for domain members?
...nt System
> > To: samba at lists.samba.org
> > Subject: [Samba] Why am I getting login failures for domain members?
> >
> > Every so often I get a message in /var/log/samba/log.samba as follows:
> >
> > 2018/05/26 13:44:25.172415, 2] authentication for user [HPRS/LABRAT$] FAILED with error NT_STATUS_WRONG_PASSWORD
> >
> > Normally, I get this when a user types in the wrong password. However, in this case LABRAT$ is
> > not a user but rather a Linux domain member computer. This happens periodically on every Linux
> > domain member on the d...
2019 Mar 04
1
getent not working after installing firewall
...Genmask Flags Metric Ref Use Iface
default mail.hprs.local 0.0.0.0 UG 202 0 0 eth0
loopback * 255.0.0.0 U 0 0 0 lo
192.168.0.0 * 255.255.255.0 U 202 0 0 eth0
1 15:45:31 root at labrat:~
# host mail.hprs.local
mail.hprs.local has address 192.168.0.2
> the AD/DC *is not your gateway* - it's the "Sonicwall firewall"
> connecting your LAN to the internet and nothing else
Now, I could configure the Linux domain members to hard-code 192.168.0.1 (Sonicwall) as th...