After an hour of inactivity no access throught network

Oxnas 810 based
Post Reply
tolis664
Posts: 2
Joined: Sat Jan 26, 2013 3:31 pm

After an hour of inactivity no access throught network

Post by tolis664 » Sat Jan 26, 2013 4:01 pm

After an hour of inactivity no access throught network. I have to restart the nsa201 to have access to the shares of the Nas. Is it broken or is there a solution ??

Mijzelf
Posts: 6194
Joined: Mon Jun 16, 2008 10:45 am

Re: After an hour of inactivity no access throught network

Post by Mijzelf » Sat Jan 26, 2013 10:44 pm

What do you exactly mean with 'no access throught network'?
  • The box is not pingable
  • The samba shares are not accessible on the NAS' ip address
  • The NAS is not accessible by name
  • The NAS is not visible in 'Network Neighbourhood' or an equivalent
  • Something else

tolis664
Posts: 2
Joined: Sat Jan 26, 2013 3:31 pm

Re: After an hour of inactivity no access throught network

Post by tolis664 » Sun Jan 27, 2013 5:15 am

Mijzelf wrote:What do you exactly mean with 'no access throught network'?
  • The box is not pingable
  • The samba shares are not accessible on the NAS' ip address
  • The NAS is not accessible by name
  • The NAS is not visible in 'Network Neighbourhood' or an equivalent
  • Something else
The samba shares are not accessible on the NAS' ip address
The NAS is visible in 'Network Neighbourhood' but the shares are not operating.
The box is pingable and i can login to it, there are no shares (they are market with ?) and i have to restart it, through its webinterface

Mijzelf
Posts: 6194
Joined: Mon Jun 16, 2008 10:45 am

Re: After an hour of inactivity no access throught network

Post by Mijzelf » Sun Jan 27, 2013 12:00 pm

This sounds as if the samba server is crashed, but the question marks in the webinterface are strange. AFAIK the firmware just generates a smb.conf, and starts samba, but doesn't check if the shares are actually available.

Anything in the logs?
Can you change something small in the shares (make a share readonly, or something like that), and apply it. If the shares are accessible then, the restarting of samba solved the problem.

Post Reply