May 6, 201412 yr I recently upgraded from 4.7 to 5.05 in order to add a new 3TB drive. Upgrading went pretty well, everything was back up and running after a few days. However, later I noticed every time I re-booted my windows 8 PC, I would lose connection to the SAMBA shares. After trying several things (including making sure the UPNP and TCP services are running), I found that by going into the tower SMB settings page and hitting "apply" on the local master option, the shares would become re-accessible again. This is rather frustrating since I run a plex server on that windows 8 PC (my unraid processor is pretty lame and can't do any transcoding on the fly, so I can't run plex server on that machine), and having to go into the unraid settings every time that machine re-boots is annoying. I never had to do any of this with 4.7, is this a bug? Why would I have to do this on the unraid box every time my windows box re-boots? I've attached a syslog in case any of the gurus would like to take a peek. Over all I love unraid I've had mine running for 3 years without issues, until I decided to upgrade last month . syslog-2014-05-05.zip
May 6, 201412 yr Author As far as I can tell it's stays checked. I just have to re "apply" the setting for the windows machine to regain access to the shares.
May 7, 201412 yr Doesn't sound like an unRAID problem... Sounds like something in the Windows 8 boot sequence has decided IT wants to be the local master.
Archived
This topic is now archived and is closed to further replies.