similar to: getent not working after installing firewall

Displaying 20 results from an estimated 20000 matches similar to: "getent not working after installing firewall"

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
2019 Mar 04
2
getent not working after installing firewall
On Mon, 4 Mar 2019 17:18:31 +0000 Rowland Penny wrote: > > On Mon, 04 Mar 2019 11:48:00 -0500 > Mark Foley via samba <samba at lists.samba.org> wrote: > > > 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: > > > >
2019 Mar 04
4
getent not working after installing firewall
On Mon, 4 Mar 2019 18:31:07 +0000 From: Rowland Penny wrote: > > On Mon, 04 Mar 2019 12:58:17 -0500 > Mark Foley via samba <samba at lists.samba.org> wrote: > > > On Mon, 4 Mar 2019 17:18:31 +0000 Rowland Penny wrote: > > > > > > On Mon, 04 Mar 2019 11:48:00 -0500 > > > Mark Foley via samba <samba at lists.samba.org> wrote: > > >
2019 Mar 04
2
getent not working after installing firewall
On Mon, 4 Mar 2019 20:43:17 +0000 Rowland Penny wrote: > > On Mon, 04 Mar 2019 15:18:31 -0500 > Mark Foley via samba <samba at lists.samba.org> wrote: > > > On Mon, 4 Mar 2019 18:31:07 +0000 From: Rowland Penny wrote: > > > > > > On Mon, 04 Mar 2019 12:58:17 -0500 > > > Mark Foley via samba <samba at lists.samba.org> wrote: > > >
2019 Mar 04
1
getent not working after installing firewall
On Mon, 4 Mar 2019 21:28:19 +0100 Reindl Harald <h.reindl at thelounge.net> wrote: > > Am 04.03.19 um 21:18 schrieb Mark Foley via samba: > >> It shouldn't, you normally only have one gateway, it is by definition > >> the 'gateway' to the WAN & internet, so I would use the same one on all > >> your machines. > > > > The LAN host
2019 Mar 04
3
getent not working after installing firewall
On Mon, 4 Mar 2019 21:18:36 +0000 Rowland Penny wrote: > > On Mon, 04 Mar 2019 15:57:16 -0500 > Mark Foley via samba <samba at lists.samba.org> wrote: > > > On Mon, 4 Mar 2019 20:43:17 +0000 Rowland Penny wrote: > > > > > > On Mon, 04 Mar 2019 15:18:31 -0500 > > > Mark Foley via samba <samba at lists.samba.org> wrote: > > > >
2019 Mar 04
0
getent not working after installing firewall
On Mon, 04 Mar 2019 12:58:17 -0500 Mark Foley via samba <samba at lists.samba.org> wrote: > On Mon, 4 Mar 2019 17:18:31 +0000 Rowland Penny wrote: > > > > On Mon, 04 Mar 2019 11:48:00 -0500 > > Mark Foley via samba <samba at lists.samba.org> wrote: > > > > > On Mon, 4 Mar 2019 14:50:38 +0000 Rowland Penny wrote: > > > > > > >
2019 Mar 04
0
getent not working after installing firewall
On Mon, 04 Mar 2019 11:48:00 -0500 Mark Foley via samba <samba at lists.samba.org> wrote: > 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
2024 Jan 19
2
Provisioning new AD Domain Controller
I'm trying to figure out the user.group of my domain administrator account. getent gives me: # getent passwd Administrator HPRS\administrator:*:0:100::/home/HPRS/administrator:/bin/false If I chown a file: chown HPRS\\administrator.100 thisfile I get: # ls -l thisfile -rwxrwx---+ 1 root users 68973 2022-08-08 09:12 thisfile If I do the same for normal domain users: # chown
2019 Mar 05
2
getent not working after installing firewall
Am 05.03.19 um 00:22 schrieb Mark Foley via samba: > /etc/resolv.conf: > nameserver 192.168.0.2 > nameserver 209.18.47.62 > > /etc/hosts: > 127.0.0.1 localhost > 192.168.0.60 ccarter > > So, the gateway is the Sonicwall firewall, 192.168.0.1. Nameservers are the DC (192.168.0.2) > and one of the ISP name servers. The IP is static and is set
2019 Mar 04
0
getent not working after installing firewall
On Mon, 04 Mar 2019 15:18:31 -0500 Mark Foley via samba <samba at lists.samba.org> wrote: > On Mon, 4 Mar 2019 18:31:07 +0000 From: Rowland Penny wrote: > > > > On Mon, 04 Mar 2019 12:58:17 -0500 > > Mark Foley via samba <samba at lists.samba.org> wrote: > > > > > On Mon, 4 Mar 2019 17:18:31 +0000 Rowland Penny wrote: > > > > > >
2024 Jan 20
2
Provisioning new AD Domain Controller
On Sat, 20 Jan 2024 15:44:18 -0500 Mark Foley via samba <samba at lists.samba.org> wrote: > After provisioning and testing my new DC offline, I now want to move > it into production. This means changing IPs. > > DC FQDN: mail.hprs.local > > IPs for setup/testing: > > DC: 192.168.1.60 > Gateway: 192.168.1.1 (Netgear router) > DNS: 192.168.1.60
2024 Jan 21
1
Provisioning new AD Domain Controller
On Sat Jan 20 16:28:14 2024 Rowland Penny via samba <samba at lists.samba.org> wrote: > > On Sat, 20 Jan 2024 15:44:18 -0500 > Mark Foley via samba <samba at lists.samba.org> wrote: > > > After provisioning and testing my new DC offline, I now want to move > > it into production. This means changing IPs. > > > > DC FQDN: mail.hprs.local > >
2019 Mar 04
0
getent not working after installing firewall
On Mon, 04 Mar 2019 15:57:16 -0500 Mark Foley via samba <samba at lists.samba.org> wrote: > On Mon, 4 Mar 2019 20:43:17 +0000 Rowland Penny wrote: > > > > On Mon, 04 Mar 2019 15:18:31 -0500 > > Mark Foley via samba <samba at lists.samba.org> wrote: > > > > > On Mon, 4 Mar 2019 18:31:07 +0000 From: Rowland Penny wrote: > > > > > >
2019 Mar 05
5
getent not working after installing firewall
On 05.03.2019 7:14, Mark Foley via samba wrote: > On Tue, 5 Mar 2019 06:17:59 +0100 Reindl Harald <h.reindl at thelounge.net> wrote: >> Am 05.03.19 um 00:22 schrieb Mark Foley via samba: >>> /etc/resolv.conf: >>> nameserver 192.168.0.2 >>> nameserver 209.18.47.62 >>> >>> /etc/hosts: >>> 127.0.0.1 localhost
2024 Jan 20
1
Provisioning new AD Domain Controller
After provisioning and testing my new DC offline, I now want to move it into production. This means changing IPs. DC FQDN: mail.hprs.local IPs for setup/testing: DC: 192.168.1.60 Gateway: 192.168.1.1 (Netgear router) DNS: 192.168.1.60 (/etc/resolv.conf) /etc/hosts: 192.168.1.60 mail.hprs.local mail smb.conf, dns forwarder: 192.168.1.1 Production IPs: DC: 192.168.0.2 Gateway:
2017 Jan 25
2
getent problems with new Samba version
I have been running Samba4 as AD/DC for a mixed Windows/Linux office domain for a little over 2 1/2 years now. I've needed a few tweaks from Roland, but basically it has run flawless during that time. 10 days ago, I upgrade to Slackware 14.2 from 14.1. Samba was likewise upgraded from version 4.2.14 to 4.4.8. I'm having a serious problem ... before the upgrade getent gave me: $
2017 Dec 01
2
getent passwd does not show correct UID.GID
On Fri, 1 Dec 2017 08:11:04 +0000 Rowland Penny via samba <samba at lists.samba.org> wrote: > On Fri, 01 Dec 2017 02:33:45 -0500 > Mark Foley via samba <samba at lists.samba.org> wrote: > > > I've moved a user from being in /etc/passwd to being a proper domain > > user. I've added the user with RSAT with UID.GID 10005.10000. I've > > removed the
2017 Jan 25
2
getent problems with new Samba version
Sorry for the serial posting, but ... anxious ... I think there must be a bug in Samba 4.4.8, this all worked with 4.2.14. To summarize (details in attached messages), since upgrading from Samba 4.2.14 to 4.4.8, getent returns the wrong UID:GID. This is causing permission errors in programs like dovecot who try to read/write to Maildir files having the correct UID:GID. With 4.4.8 I now have
2019 Aug 28
2
Authenticating Samba Share with Domain Administrator
On Thu, 22 Aug 2019 08:04:10 +0100 Rowland penny <rpenny at samba.org> wrote: > > On 21/08/2019 22:47, Mark Foley via samba wrote: > > I have a NAS (Linux/Slackware 14.2) that is a domain member. "Normal" AD Windows users can map > > shared directories just fine without having to enter Credentials. If I try doing that with the > > domain Administrator it