NT_STATUS_NO_LOGON_SERVERS

[jpp123]

I have a ReadyNAS running RAIDiator 3.01c1-p4 it's a member of a domain "CLOUDVIEW". The PDC is a FreeBSD box running samba 3.0.23c.

It used to work. However I updated my samba build on the PDC and I now get this

jeeves# /usr/local/bin/smbclient \\\\filestore\\ -U jpp
Password:
session setup failed: NT_STATUS_NO_LOGON_SERVERS
jeeves#

and syslog on the PDC show this

Dec 6 00:24:37 jeeves smbd[31622]: [2006/12/06 00:24:37, 2] auth/auth.c:check_ntlm_password(309)
Dec 6 00:24:37 jeeves smbd[31622]: check_ntlm_password: authentication for user [jpp] -> [jpp] -> [jpp] succeeded
Dec 6 00:24:37 jeeves smbd[31622]: [2006/12/06 00:24:37, 2] auth/auth.c:check_ntlm_password(309)
Dec 6 00:24:37 jeeves smbd[31622]: check_ntlm_password: authentication for user [jpp] -> [jpp] -> [jpp] succeeded

What changed and how to I get access to my data again?

[yoh-dah]

3.0.23c is probably broken.

[jpp123]

it works for my macs and winxp boxes they can all authenticate and see each other - but none (FreeBSD, Win XP or OSX) can connect to the readynas

[Skywalker]

Have you tried having the NAS re-join the domain? Also, can you make sure nmbd is running on the PDC?

[jpp123]

Have you tried having the NAS re-join the domain? Also, can you make sure nmbd is running on the PDC?

Yes and Yes - I can get ethereal dumps if that will help

[Skywalker]

Let's hold off on the ethereal dumps for now at least. When you try to rejoin the domain from the NAS, does it say it's successful, or unsuccessful? Have you tried specifying an IP address for the domain controller, instead of having the NAS auto-detect?

[jpp123]

Let's hold off on the ethereal dumps for now at least. When you try to rejoin the domain from the NAS, does it say it's successful, or unsuccessful? Have you tried specifying an IP address for the domain controller, instead of having the NAS auto-detect?

It says it worked and specifying an IP doesn't change anything.

[jpp123]

After a lot of digging around I fixed it. During the upgrade of samba to .23c (now d) my PDC somehow "lost" the group mappings - this effectively left my network with no "Domain Admins" "Domain Users" or "Domain Guests" groups.

Re-creating those group mapping with the correct RID's fixed the issue.

[stevela]

I'm seeing exactly the same problem after upgrading to 3.0.23 on debian.

I tried 3.0.26a, even went so far as to recreate the domain completely - XP clients work fine; ReadyNAS can join the domain, but any attempt to connect to it from XP or smbclient on debian results in the NT_STATUS_NO_LOGON_SERVERS error.

Upping the debug level shows that the account used is being verified, yet I still see the problem...

Could you provide the solution you used in detail?

[stevela]

The following fixed the problem:

net groupmap add ntgroup="Domain Admins" unixgroup=ntadmins rid=512 type=d
net groupmap add ntgroup="Domain Users" unixgroup=users rid=513 type=d
net groupmap add ntgroup="Domain Guests" unixgroup=nogroup rid=514 type=d