Odd samba entries in the FreeNAS log

[Skyfox]

For quite a while now I have noticed the following entries in the FreeNAS log, seems to be entered every few minutes.

Code:

Oct 15 15:03:26 freenas smbd[1304]:   STATUS=daemon 'smbd' finished starting up and ready to serve connectionsoptimus (ipv4:192.168.50.100:55272) closed connection to service Share
Oct 15 15:04:08 freenas smbd[3959]:   STATUS=daemon 'smbd' finished starting up and ready to serve connectionsoptimus (ipv4:192.168.50.100:57003) closed connection to service Private
Oct 15 15:11:08 freenas smbd[4232]:   STATUS=daemon 'smbd' finished starting up and ready to serve connectionsoptimus (ipv4:192.168.50.100:57261) closed connection to service Share
Oct 15 15:11:52 freenas smbd[4269]:   STATUS=daemon 'smbd' finished starting up and ready to serve connectionscreate_connection_session_info failed: NT_STATUS_ACCESS_DENIED

'optimus' being the name of my main PC. (Running Windows 7) FreeNAS version is 9.2.1.8 64bit.

Having read through some posts on the forum it appeared to be down to the SMB version used. It seemed to suggest that knocking the samba version down from SMB3 to SMB2 in the CIFS settings would do the trick.

Sadly it hasn't. Any other suggestions would be great.

Cheers!

 

[SweetAndLow]

Just looks like the user trying to log-in doesn't have access to the shares. Fix the permissions on the dataset or folder being shared might make the errors go away.

 

[Skyfox]

Thanks for the reply. (Was on holiday, sorry for leaving it so long)

I have gone through all the permissions on the dataset and the windows permissions. All seems to be correct and function correctly. The machine in question can access the shares correctly. Interestingly, I recently had reason to access the shares remotely via the built in viewer on my ASUS router, and that threw up the same message in the log. So it's not just my main Windows 7 machine.

I will keep fiddling, but there doesn't appear to be any major issues as everything works perfectly, it just likes filling up my FreeNAS logs :)

Thanks again.

 

[shackrock]

This is happening to me too - starting yesterday randomly, also all permissions are proper and haven't changed in a year - and all computers seem to have the proper access without any issues...

Code:

Nov 8 09:00:00 freenas newsyslog[7095]: logfile turned over due to size>100K
Nov 8 09:33:49 freenas smbd[8412]: STATUS=daemon 'smbd' finished starting up and ready to serve connectionssolotop (ipv4:192.168.1.182:55453) closed connection to service DEC2010
Nov 8 11:44:13 freenas smbd[15999]: STATUS=daemon 'smbd' finished starting up and ready to serve connectionssolobox (ipv4:192.168.1.179:63221) closed connection to service DEC2010
Nov 8 13:06:55 freenas smbd[20773]: STATUS=daemon 'smbd' finished starting up and ready to serve connectionssolotop (ipv4:192.168.1.182:59579) closed connection to service DEC2010
Nov 9 01:00:20 freenas smbd[27662]: STATUS=daemon 'smbd' finished starting up and ready to serve connectionssolobox (ipv4:192.168.1.179:64911) closed connection to service DEC2010
Nov 9 08:44:22 freenas smbd[33192]: STATUS=daemon 'smbd' finished starting up and ready to serve connectionsFailed to fetch record!
Nov 9 08:46:38 freenas smbd[33213]: STATUS=daemon 'smbd' finished starting up and ready to serve connectionssolotop (ipv4:192.168.1.182:50221) closed connection to service DEC2010

 

[Skyfox]

Sorry to hear you are having the same issue, however I am relieved to hear it's not just me!

I have messed about with many settings and permissions, but still it remains. I'm hoping one of the next updates will just fix it :)

 

[anodos]

Are you using guest access? Try increasing logging verbosity and recreating the problem.

 

[Skyfox]

Hi, yes, I am using Guest access on one of the shares.

I upped the CIFS 'log level' up to FULL. It was on minimum. Did you expect this to fix the problem? Because it's now been 5 hours without a single error appearing.

Will keep an eye on it over the next few days.

Thanks!

 

[anodos]

Hi, yes, I am using Guest access on one of the shares.

I upped the CIFS 'log level' up to FULL. It was on minimum. Did you expect this to fix the problem? Because it's now been 5 hours without a single error appearing.

Will keep an eye on it over the next few days.

Thanks!

Increasing logging verbosity will not eliminate the problem. Instead it should give you an idea of what exactly is going on when the log entry is generated. You should review the log under /var/log/samba4/log.smbd
My best guess is that it is related to using guest access.