[Samba] That domain could not be found

Jason Waters jason at geeknocity.com
Sat Jul 30 21:06:21 UTC 2016


Is the primary DNS on the windows machine set to the AD domain controller?

On Jul 30, 2016 4:42 PM, "Jeff Sadowski" <jeff.sadowski at gmail.com> wrote:

> following here
> https://www.samba.org/samba/docs/using_samba/ch12.html
> I decided to use explorer to test getting to it and I notice I can connect
> to the server using the Administrator user and password and see the
> netlogon and sysvol shares but can not go into either.
>
>
> On Sat, Jul 30, 2016 at 11:33 AM, Jeff Sadowski <jeff.sadowski at gmail.com>
> wrote:
>
> > I had a working domain and then I realized I was spelling it wrong all
> > this time.
> > So I created a VM and installed samba with ad support on it
> >
> > I used the instructions from
> >
> https://wiki.samba.org/index.php/Setup_a_Samba_Active_Directory_Domain_Controller
> > all the tests for the DNS entries checked out
> >
> > kinit checked out
> > klist shows my key
> > On other computers even
> >
> > When I went to join my window 10 machine that I can still connect to my
> > original machine I get the message in the subject
> >
> > I don't remember  doing anything different originally for my working
> > domain.
> > I turned off the firewall and selinux on my VM
> >
> > Windows 10 nslookup sees all the DNS entries I checked on walk trough
> > nltest /dsgetdc:<domainname>
> > returns
> > Getting DC name failed: Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN
> >
> > I'm not sure what else to check.
> >
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
>


More information about the samba mailing list