search for: machine251

...ry 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. [global] netbios name = MACHINE251 realm = INTERNAL.DOMAIN.COM workgroup = INTERNAL dns forwarder = 4.2.2.2 server role = active directory domain controller idmap_ldb:use rfc2307 = yes [netlogon] path = /var/lib/samba/sysvol/internal.domain.com/scripts read only = No [...

...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. > > [global] > netbios name = MACHINE251 > realm = INTERNAL.DOMAIN.COM > workgroup = INTERNAL > dns forwarder = 4.2.2.2 > server role = active directory domain controller > idmap_ldb:use rfc2307 = yes > > [netlogon] > path = /var/lib/samba/sysvol/internal.domai...

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 On February 17, 2019 8:17:03 AM EST, Rowland Penny via samba <samba at lists.samba.org> wrote: >On Sun, 17 Feb 2019 07:51:24 -0500 >Marco Shmerykowsky via samba <samba at lists.samba.org> wrote: > >> In

...ernal 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. >> >> [global] >> netbios name = MACHINE251 >> realm = INTERNAL.DOMAIN.COM >> workgroup = INTERNAL >> dns forwarder = 4.2.2.2 >> server role = active directory domain controller >> idmap_ldb:use rfc2307 = yes >> >> [netlogon] >> path = /var...