Lost CIFS after upgrade to 9.2.1.7

[Harrison]

Just upgraded from9.2.1.5 to 9.2.1.7 and have lost all file access under our domain.

Aug 16 12:07:24 WEINIGNAS notifier: Performing sanity check on Samba configuration: OK
Aug 16 12:07:24 WEINIGNAS notifier: Starting nmbd.
Aug 16 12:07:24 WEINIGNAS notifier: Starting smbd.
Aug 16 12:07:24 WEINIGNAS nmbd[32142]: [2014/08/16 12:07:24.891142, 0] ../lib/util/become_daemon.c:136(daemon_ready)
Aug 16 12:07:24 WEINIGNAS notifier: Starting winbindd.
Aug 16 12:07:25 WEINIGNAS smbd[32146]: [2014/08/16 12:07:25.002069, 0] ../lib/util/become_daemon.c:136(daemon_ready)
Aug 16 12:07:25 WEINIGNAS winbindd[32150]: [2014/08/16 12:07:25.167953, 0] ../lib/util/become_daemon.c:136(daemon_ready)

- Terminal is continually printing:
Aug 16 12:07:37 WEINIGNAS smbd[32158]: STATUS=daemon 'smbd' finished starting up and ready to serve connectionsgss_accept_sec_context failed with [ Miscellaneous failure (see text): Failed to find cifs/WEINIGNAS@WEINIGASIA.LOCAL(kvno 35) in keytab MEMORY:cifs_srv_keytab (arcfour-hmac-md5)]

I'm going to be in shit come Monday morning.
Grateful for any help.

 

[warri]

Can't help with the original problem, but you can always revert to 9.2.1.5 as a temporary measure.

 

[Dudleydogg]

This boggled me for days and even multiple installations.
Failed to find cifs/fs4.mydomain.us@mydomain.US(kvno 16) in keytab MEMORY:cifs_srv_keytab (arcfour-hmac-md5)]

I have Discovered THAT!!!! If your running samba and lets say in my case i named netbios "\\san\ but it used to be at one time \\fs4
I had clients on the network that were still connected to the old \\fs4 and because of dns and it was same IP each time they tried you get on console
Failed to find cifs/fs4.mydomain.us@mydomain.US(kvno 16) in keytab MEMORY:cifs_srv_keytab (arcfour-hmac-md5)]
on freenas login root and "tail -f /var/log/messages" then go to a windows client and type in a name \\fs4 that does not match your netbios name but resolves to same IP
each time you hit enter you will see the kerbos Cifs error I got the messages because I had GPO mapping drives to the OLD name with same IP address
make sure NO other name except the BOUND netbios name have same IP as your freenas. This is my problem I hope this helps some one else.