Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Keep losing access to server until reboot {SOLVED}

Featured Replies

I have to keep powering down and rebooting my server in order to get access to it and its getting annoying. I just recently reinstalled my OS windows 8.1 because of some issues I was having but even before that I would have this problem. I can access my server via webgui 5.0.5. I dont want to have to power down and reboot every time I want access to my server. Anyone have any ideas? I know im not giving you much to go on but I dont know where to start...I have attached a syslog...

 

 

***as Im typing this I randomly got access to my server again. I can always see the server via File Explorer in Windows. But when I try to access it it often says cannot and gives me option to diagnose which does nothing. Thanks. Sorry for lack of info..........

Syslog.zip

that sounds like a network problem...not an unRAID problem.

Check your cables...powerdown and restart your routers, and switches.

 

  • Author

the reason i was thinking unraid problem (or some combo between that and my network) is that it always works after I reboot the server... :-\

try accessing it by IP address. After updating to unraid 6 beta, sometimes I can get into my shares via unc path and then right after it wont let me in and I have to use ip of the server and its fine. I am on windows 8.1 update 1 and it could be the operating system or router as well.

  • Author

try accessing it by IP address. After updating to unraid 6 beta, sometimes I can get into my shares via unc path and then right after it wont let me in and I have to use ip of the server and its fine. I am on windows 8.1 update 1 and it could be the operating system or router as well.

 

How can I access the server through IP address? Or do you mean the webgui? I never seem to have problems accessing it via webgui...But perhaps ill give 6.0 beta a try..thanks

  • Author

thanks but I have no problem accessing via webgui only when i try to access it through windows do I have the problem

Is it perhaps stored passwords on your windows machine that are incorrect?

 

THere's a number of threads here about that. On a Mac they are filed in the 'Keychain' file...sorry I can't help you with Windows 8.1 other than to say I think its in the 'Windows Control Panel' somewhere.

 

Perhaps someone else can point you at the right file.  In the file, just find the pointers to unRAID shares and delete them. The next time you login to unRAID you'll be prompted for the password and it will be saved (automatically) into the

 

  • Author

I tried adding root & my password to windows credentials...but didnt work. again restarted server from the webgui and i got access to my shares again....? :o

I tried adding root & my password to windows credentials...but didnt work. again restarted server from the webgui and i got access to my shares again....? :o

Just worth mentioning that for security reasons, from v5 onwards 'root' is no longer a valid user for accessing shares.
  • Author
Just worth mentioning that for security reasons, from v5 onwards 'root' is no longer a valid user for accessing shares.

Interseting i still use it for webgui login and telnet...ill look into that tho. Thanks

Just worth mentioning that for security reasons, from v5 onwards 'root' is no longer a valid user for accessing shares.

Interseting i still use it for webgui login and telnet...ill look into that tho. Thanks

Web GUI and telnet are fine (and root would be the normal default) - just not shares.
  • Author
Web GUI and telnet are fine (and root would be the normal default) - just not shares.

 

is there a default username and password then? Would this effect windows credentials? Im looking at the unraind manual wiki and it shows how to change the password but i must be overlooking the default? but bringing it back to my original problem if its a password thing then why does it always work after i reboot my server?  :'( thanks again for all your input.

Web GUI and telnet are fine (and root would be the normal default) - just not shares.

 

is there a default username and password then? Would this effect windows credentials? Im looking at the unraind manual wiki and it shows how to change the password but i must be overlooking the default? but bringing it back to my original problem if its a password thing then why does it always work after i reboot my server?  :'( thanks again for all your input.

The default  is to allow public access to shares which means that username/password are irrelevant.  It is when you try to restrict access to specific users that the restriction of not allowing root comes into play.
  • Author
The default  is to allow public access to shares which means that username/password are irrelevant.  It is when you try to restrict access to specific users that the restriction of not allowing root comes into play.

 

good to know...to the best of my knowledge i have not added any type of password to any of my shares :-X

Did you set up the SMB setting to allow your unRAID server to become the "Local Master'?  You often have to restart every device that uses SMB on your network to allow your Server to become the local master for the SMB network.  (The local master is a SMB DNS server.)  One other thing is that your server has to be available 24x7 for it to remain the local master.  (No putting it to sleep and/or turning it off when other devices using SMB are still on.  You should note that most small media servers that use SMB can become the local master and they often have old, old, old versions of samba!)

  • Author

Did you set up the SMB setting to allow your unRAID server to become the "Local Master'?  You often have to restart every device that uses SMB on your network to allow your Server to become the local master for the SMB network.  (The local master is a SMB DNS server.)  One other thing is that your server has to be available 24x7 for it to remain the local master.  (No putting it to sleep and/or turning it off when other devices using SMB are still on.  You should note that most small media servers that use SMB can become the local master and they often have old, old, old versions of samba!)

I have not gone out of my way to setup the SMB unless it was something I wasnt aware was SMB  :-[ Ill have to search it and see what its about. Thanks for the info

  • Author

im pretty sure i didnt do anything with smb because i dont know what it is really haha but maybe i did in an attempt to fix something. is there some way to check. again im sure i didnt do anything with it. but not be able to access my shares until i reboot my server is driving me nuts  :o

 

oh i see it right there in the webgui settings. It says enable SMB: Yes (Workgroup)

local master: no

 

should i adjust any of these settings?

 

oh i see it right there in the webgui settings. It says enable SMB: Yes (Workgroup)

local master: no

 

should i adjust any of these settings?

 

Yes, you should set the 'local master' to 'Yes'!  That allows your server to become the local master on the SMB network.  The local master converts the server names to the IP addresses for use in all SMB transactions.  If the local master should moved to another computer because the current local master is no longer available, it can take up to an hour to the change to propagate through the network. Until that occurs, it is possible that a computer may be unable to may not being able to get the IP address of  the server when you attempt to establish connection to the server.  If your server is on 24x7, it will become (and remain) the local master.  The end result is that your entire network will be much more stable and reliable.

 

You have to realize that the basic SMB protocol was defined in the 8086 (and Windows 3.1 for Workgroups) days and the polling interval was set at about fifteen minutes.  (Those CPU's didn't have any spare cycles to waste!)  As a result, it takes a long time for an SMB network to become completely stable and for all computers have checked into the local master to be come registered!

  • Author

thanks @Frank1940 all that is well over my head...haha but ill change the settings and continue to monitor everything. Thanks again!

Since you are (apparently) not familiar with SMB (and Windows networking in general), it is also necessary that all of the computers be assigned to the same Workgroup.  This setting is done in the same SMB setting page on unRAID as where you turned on the 'local master' setting.  On Windows 7, go the 'Control Panel', find the 'System' icon and open that icon. (You can also get to this point by opening Windows Explorer find the 'Computer' icon, left click on the icon and select properties.)  Now scroll down the page until you find the section called 'Computer Name, Domain and workgroup settings'. Click on the 'Change Settings' link.  Under the 'Computer Name' Tab, you will find a 'Change' button.  Click on it.  (For other Windows versions, one of these two methods should get you this screen.  If you have a problem, google with the windows version and the words 'change Workgroup'.)

 

What you want to to have all of the computers on your network to be in the same Workgroup.  Usually, it is easier to change the workgroup name of your server to match whatever your Windows machines are using.  (I can't remember what the Windows default name is since I changed mine to a unusual workgroup name back in the days when Windows 3.1 for Workgroups gave unrestricted file access to the Internet connection--- Talk about your security leaks!!!)

  • Author

Hey Frank thanks again for the info. I already do have the server and my computers on the same workgroup. It is not the default workgroup name but a unique one. I just had to restart my server again however. I was able to access it this morning but not this evening.... :'(

 

Update: So just restarted server as just mentioned above and everything was fine. I went back to access something on my server and for the first time ever i got this message "\\Server\ is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. The parameter is incorrect."

 

Normally it says "Windows cannot access \\Server Check the spelling of the name. Otherwise, there might be a problem with your network. To try to identify and resolve network problems, click Diagnose"

Hey Frank thanks again for the info. I already do have the server and my computers on the same workgroup. It is not the default workgroup name but a unique one. I just had to restart my server again however. I was able to access it this morning but not this evening.... :'(

 

Update: So just restarted server as just mentioned above and everything was fine. I went back to access something on my server and for the first time ever i got this message "\\Server\ is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. The parameter is incorrect."

 

Normally it says "Windows cannot access \\Server Check the spelling of the name. Otherwise, there might be a problem with your network. To try to identify and resolve network problems, click Diagnose"

 

You might have a couple of issues. 

 

First one.  Moving Local Master computer.  If your network has a situation where computers are constantly turnoff and on, the local master may be constantly moving from one computer to the other.  Unfortunately, SMB is not robust enough to always deal gracefully with this.  That is why I recommended enabling the Local Master  option in unRAID and leaving that server on all the time.  (By the way, constant rebooting is the same as turn the server off!) 

 

To find out which computer is the local master is pain-in-the-neck.  Read this post which I found with google:

 

    http://scottiestech.info/2009/02/14/how-to-determine-the-master-browser-in-a-windows-workgroup/

 

If your server is not the master browser, You may have to power down (or pull the plug) on EVERY device that is attached to your network except for your server.  (Any non-computer device that can connect to the network is probably running Linux, possibly has SMB installed and can become the local master!)  Leave everything off for (at least) a half hour.  Turn back on one computer and check that your server is now the master browser.  Then slowly plug things back in.  After everything is plugged back in, recheck to see that it is still the Local Master.  Try and leave the server on for at least a week without turning it off or rebooting. 

 

Second one:  You might have an add-in which is writing files to your server with the wrong permission for version 5.0.x.  (Tom changed the array permissions during the beta phase for increased security.)  If one of your add-ins has not been updated to reflect this change, you will get this type of message.  Another possibility is that you have a credential issue on your windows machine.  (Search for 'credentials' and you should be able to locate the control panel page that has any credentials that have been set on that computer.)

 

PS -----  It is not real clear in the link how to get to a DOS window.  On my Win7 machine, you open the 'Start menu" and type 'cmd' (not quotes) on the search line. 

  • Author

Hey Frank thanks again for the info. I already do have the server and my computers on the same workgroup. It is not the default workgroup name but a unique one. I just had to restart my server again however. I was able to access it this morning but not this evening.... :'(

 

Update: So just restarted server as just mentioned above and everything was fine. I went back to access something on my server and for the first time ever i got this message "\\Server\ is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. The parameter is incorrect."

 

Normally it says "Windows cannot access \\Server Check the spelling of the name. Otherwise, there might be a problem with your network. To try to identify and resolve network problems, click Diagnose"

 

You might have a couple of issues. 

 

First one.  Moving Local Master computer.  If your network has a situation where computers are constantly turnoff and on, the local master may be constantly moving from one computer to the other.  Unfortunately, SMB is not robust enough to always deal gracefully with this.  That is why I recommended enabling the Local Master  option in unRAID and leaving that server on all the time.  (By the way, constant rebooting is the same as turn the server off!) 

 

To find out which computer is the local master is pain-in-the-neck.  Read this post which I found with google:

 

    http://scottiestech.info/2009/02/14/how-to-determine-the-master-browser-in-a-windows-workgroup/

 

If your server is not the master browser, You may have to power down (or pull the plug) on EVERY device that is attached to your network except for your server.  (Any non-computer device that can connect to the network is probably running Linux, possibly has SMB installed and can become the local master!)  Leave everything off for (at least) a half hour.  Turn back on one computer and check that your server is now the master browser.  Then slowly plug things back in.  After everything is plugged back in, recheck to see that it is still the Local Master.  Try and leave the server on for at least a week without turning it off or rebooting. 

 

Second one:  You might have an add-in which is writing files to your server with the wrong permission for version 5.0.x.  (Tom changed the array permissions during the beta phase for increased security.)  If one of your add-ins has not been updated to reflect this change, you will get this type of message.  Another possibility is that you have a credential issue on your windows machine.  (Search for 'credentials' and you should be able to locate the control panel page that has any credentials that have been set on that computer.)

 

PS -----  It is not real clear in the link how to get to a DOS window.  On my Win7 machine, you open the 'Start menu" and type 'cmd' (not quotes) on the search line.

 

THanks again Frank. My server is the Local Master. I removed all add ons through unMenu so maybe that will help. Ill keep you posted. Thanks

 

Update: I meant to send that this morning. after getting home from work I cant access the server again. Maybe it is a windows credentials thing. I dont see one has been created for my server. What should i type in to create one? I need to enter my internet or network address....Then a user name and password

I've had this happen to me a few times since upgrading from 5.04 to 5.05....

 

Restarting Windows machine does not change things.  Nor does using NET USE commands to attempt to re-establish Windows' network info.

Restarting server DOES fix things.

 

Looking into the log, shows the server IS having troubles during this time, with NUMEROUS (dozens/hundreds) entries stacking up like this... (affecting multiple shares movie/tv/etc)

 

 

May 27 19:27:14 tower emhttp: get_filesystem_status: statfs: /mnt/user/MOVIE Transport endpoint is not connected

 

I've emailed Tom directly (twice), posting more complete copies of my logs to pastebin....but received no response.  (shrug)

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.