Windows 10 did it again: Windows cannot access \\freenas

[esamett]

It was working 2 days ago. I presume some background windows update screwed it up again. I played around with this with my other computer and got some other message about freenas found but no connection accepted or some such. I have no problem logging into freenas web interface.

!!!!!!!!!

 

[esamett]

perhaps this is the culprit:


freenas.domain kernel log messages:
> Failed to write core file for process smbd (error 14)
> pid 52219 (smbd), uid 0: exited on signal 6
-- End of security output --

I rebooted and I see network again. Does this mean anything?

 

[anodos]

What version of freenas?

 

[BBarker]

perhaps this is the culprit:


freenas.domain kernel log messages:
> Failed to write core file for process smbd (error 14)
> pid 52219 (smbd), uid 0: exited on signal 6
-- End of security output --

I rebooted and I see network again. Does this mean anything?

Windows 10?

I kept getting errors when trying to log into certain shares after making changes as it would keep asking for the previous set of credentials. This included me not being able to access shares from \\freenas in windows explorer.

My solution was to go into the "Credential Manager" and delete all the old instances of FreeNAS that were showing up under the Windows Credentials tab

You can find it by typing "Credential Manager" in the search box in the task bar. You'll find it will load much faster as well.

 

[esamett]

Win 10
Freenas 9.x. Newest update.