Re: [Samba] SAmba 4.9 and Win XP Clients
- Date: Sun, 17 Feb 2019 15:17:16 +0000
- From: Rowland Penny via samba <samba@xxxxxxxxxxxxxxx>
- Subject: Re: [Samba] SAmba 4.9 and Win XP Clients
On Sun, 17 Feb 2019 09:53:56 -0500
Marco Shmerykowsky <marco@xxxxxxxxxxxxxxxxx> wrote:
> I tried the NTLM setting. No change.
> When I try to browse the network, I get the following error:
> "internal is not accessible. You might not have permission to
> use this network resource. The list of servers for this workgroup
> is not currently available."
> Here is the smb.conf from the AD machine.
> netbios name = MACHINE251
> realm = INTERNAL.DOMAIN.COM
> workgroup = INTERNAL
> dns forwarder = 184.108.40.206
> server role = active directory domain controller
> idmap_ldb:use rfc2307 = yes
> path = /var/lib/samba/sysvol/internal.domain.com/scripts
> read only = No
> path = /var/lib/samba/sysvol
> read only = No
> read only = no
> On 2019-02-17 9:15 am, Rowland Penny via samba wrote:
> > On Sun, 17 Feb 2019 09:06:21 -0500
> > Marco J Shmerykowsky PE <marco@xxxxxxxxxxxxxxxxx> wrote:
> >> Thanks. Will check.
> >> I should have added that everything was working fine on the old
> >> winNT style samba domain setup. Its something related to the new
> >> samba AD setup
> > It might be and it probably is something to do with NTLMv1, but I am
> > still guessing, because you still haven't posted your smb.conf
> > Rowland
OK, there doesn't seem to be anything wrong with your DC smb.conf, have
you set up the libnss-winbind links ?
You said 'but they can't see any of the machines on the network'. This
is normal, there is no network browsing in a Samba AD domain.
You also said 'I created a stand alone member server', this is a
contradiction in terms (it is either a standalone server or a Unix
domain member). You haven't posted the smb.conf for this, can you do so.
To unsubscribe from this list go to the following URL and read the