[RESOLVED] CIFS/SMB with AD suddenly stopped Authenticating

[mbze430]

Ok I was going through the forum and searching can't really find anything that is related to my issue.. so here goes.

I have NAS4Free originally *working* with my AD Windows 2012 r2. Everything was fine. Domain and Non-Domain(using AD username) workstation was able to to connect to the NAS4Free SMB's share. Even the MacOS works.

Now, for whatever reason... last night after a reboot on the NAS4Free.. SMB is semi-broken. The Mac can still get the shares. But NONE of the Windows machines can. Domain machines or Non-Domain. using [domainname]\[usename] or [username]@[domainname] all failed.

NOTE: All SMB share created on Windows File server machine works just fine.

Code: Select all

MS Active Directory informations
Results for net rpc testjoin:
Environment LOGNAME is not defined. Trying anonymous access.
Join to '[domainname]' is OK
Ping winbindd to see if it is alive:
Ping to winbindd succeeded
Check shared secret:
checking the trust secret for domain HOME via RPC calls succeeded

I haven't changed the CIFS/SMB tab... so I am lost. No errors containing "smb" in the log either. But then again, my log is really iffy... when I clear it, it never comes back. (but that's another topic).

If anyone can help, please do. TIA

[mbze430]

So I turned off AD in NAS4Free and use Local, and that is fine. Now I am really at a lost.

[crowi]

if you have saved your configuration file, install a new USB stick with N4F, load the config and check if it is working again.

[mbze430]

Ok, I turned off all my CIFS/SMB and AD stuff in NAS4FRee... deleted the smb.conf rebooted the NAS4Free box.

Came back, and re-enabled everything it works.

There is some serious issues with NAS4Free and the AD implementation.

(NOW I AM JUST SCARED TO REBOOT THE BOX BECAUSE ALL OF THAT MIGHT BREAK AGAIN FOR NO REASON)