I've given up trying to troubleshoot this issue myself.  The problem I am having is being unable to browse shares after the share directory has not been 'browsed' for some time. 

 

System background:

 

-Running Vista & Unraid 4.4 Beta 2 (though I was running 4.3 and had the same issue).

-Boxes are connected through a Netgear gigabit switch at Cat6 cable all verified working perfectly.

-Running the unlicensed version of Unraid while I evaluate with no root password set.  Running Vista with a password protected username that is not 'root'.

-Running on a MSI P43 Neo3-F with the latest BIOS. 

 

 

There are two levels of issues I am see:

 

 

If I do not browse the shares for ~2 hours, for example I am watching a movie; if I attempt to browse to another folder in the share or to another share after watching the movie I will not be able to access them though windows explorer.  Also in the same situation if I stay within the same folder in the share I am able to access the files in the share, but I still be unable to change directories.  However if I type \\Tower in one of the address bars I instantly gain back access to all of the shares in both situations. 

 

In the above situation during the period of being unable to browse the shares I am able to access the web interface fine, ping the Unraid box by IP address and PC name from Vista and vice versa from the Unraid box.  I can also see the Unraid box listed in the Vista network folder but cannot access it.

 

 

The second issue is if leave the system idle overnight.  In this situation I am completely unable to browse the shares and typing \\Tower in the address bar does not allow me to gain access to the shares.  As above I am still able to ping, access the web interface and see the Tower listed in the Vista network folder.  I have to restart the SMB daemon before I am able to access the shares again but then the cycle continues.

 

 

I've taken some steps to try and resolve this myself which includes:

 

-Verifying this is not a layer 1 issue.  All hardware and cables are in working order.

-Disabled the Windows firewall and any other potential software that could affect network ports on the Vista machine.

-Enabled NTLM on Vista for the hell of it even though I understand this version of Samba handles NTLMv2 fine.

-Added echo 192.168.1.3 tower >> /etc/hosts to the go config.

-Syslog and ifconfig look clean.

 

Other than this problem the software has been performing great when I actually have access to the shares.  I would really like to step up to a licensed version if I can get this problem resolved so any help in troubleshooting would be appreciated.

So I think I've actually isolated the problem and it seems to be related to Media Portal of all things.  If I browse around the shared folders within Media Portal for a while then attempt to access \\Tower with Media Portal running the server is unreachable until the moment I kill the Media Portal process.

 

Is anyone successfully running Unraid with Media Portal without issue? 

I have a similar problem.  But I'm accessing the box from a network, (XP machines).  I have to re-boot the lime box in order to view the shares.  After a few hours, the shares are no longer available, and I have to reboot again.  I am not using media portal.