Jump to content

33 posts in this topic Last Reply

Recommended Posts

I had the similar issue.  Hoping this might help someone else.

 

Steps that caused the problem:

 

1.  Create a new user in unraid

2.  All shares are configured with public access (meaning no username / password is required)

3.  Attempt to access the share via windows explorer.

4.  I mistakenly entered the username and password that I had created earlier.

5.  I clicked the option to remember credentials.

 

This caused windows to store the unnecessary username and password.

For some reason, unraid will prompt for credentials if you try to access a public share using a username and password.

 

Steps to resolve (Windows 10):

 

1.  Go to Control Panel

2.  Click on user accounts

3.  Click manage your credentials

4.  Click windows credentials

5.  Remove any instance of the credentials

6.  Close all windows attempting to access the unraid server

7.  Type in the location of your server.  Mine was \\tower.

8.  Click enter.

 

Hopefully the issue is resolved and you can get to your data.

Share this post


Link to post

I having a similar issue:

From my Windows 10 PC (I have also tried accees from a Windows Server 2012 R2 machine as well) I enter the username and password to the share that I have specified restricted access to in unRAID.  The password dialogue box keeps coming back up but there is no error.  I have tried machinename/username and machinename\username.  I have also tried with IP address.

 

I tried the net user * /delete option that was listed in this thread as well with no luck.

 

I have run file system check/repair and restarted array/server.

 

I retried resetting the user pws and creating new accounts.  I have also tried multiple shares.

 

Basically it just continuously prompts me over and over for username and password.

 

Am I missing something here?  "I FEEL LIKE I'M TAKING CRAZY PILLS!".

 

Any suggestions would be awesome!

 

PS - Not a huge deal not having share security on a media server but I would like to be able to lock down a backup share.

Share this post


Link to post
On 29/10/2016 at 8:35 PM, durdyness said:

I having a similar issue:

From my Windows 10 PC (I have also tried accees from a Windows Server 2012 R2 machine as well) I enter the username and password to the share that I have specified restricted access to in unRAID.  The password dialogue box keeps coming back up but there is no error.  I have tried machinename/username and machinename\username.  I have also tried with IP address.

 

I tried the net user * /delete option that was listed in this thread as well with no luck.

 

I have run file system check/repair and restarted array/server.

 

I retried resetting the user pws and creating new accounts.  I have also tried multiple shares.

 

Basically it just continuously prompts me over and over for username and password.

 

Am I missing something here?  "I FEEL LIKE I'M TAKING CRAZY PILLS!".

 

Any suggestions would be awesome!

 

PS - Not a huge deal not having share security on a media server but I would like to be able to lock down a backup share.

 

On 16/11/2016 at 10:16 PM, HAVOC said:

Same problem with no luck

 

Did any of you guys figure it out? I feel lige I've tried everything, but I just can't access private shares with any users.

Share this post


Link to post
1 hour ago, larsfeldbech said:

I feel lige I've tried everything, but I just can't access private shares with any users.

You have replied to a thread that is nearly 1 year old and is for unRAID 5 and older. What version of unRAID are you using?

Share this post


Link to post

 

On 2/9/2017 at 3:32 PM, trurl said:

You have replied to a thread that is nearly 1 year old and is for unRAID 5 and older. What version of unRAID are you using?

Yeah I know the thread is old. I'm using the latest 6.3.5, but as it looked like a Windows related problem I figured it didn't make much of a difference.

After hours of getting the private folders to work, it suddenly just happened. In the beginning, cmd and "net use" didn't show me anything but all of a sudden it did and things started working after a "net use * /del".

Now I just hate that I don't know what made the difference but at least it works.

Share this post


Link to post
2 hours ago, larsfeldbech said:

 

Yeah I know the thread is old. I'm using the latest 6.3.5, but as it looked like a Windows related problem I figured it didn't make much of a difference.

After hours of getting the private folders to work, it suddenly just happened. In the beginning, cmd and "net use" didn't show me anything but all of a sudden it did and things started working after a "net use * /del".

Now I just hate that I don't know what made the difference but at least it works.

 

Probably something to do with the user you are letting windows connect with. See here:

 

Share this post


Link to post

Hi, I've read through the thread and realize what the limitation in Windows is... that being said, when one has one of their public shares from unRAID set up as a network drive that connects at boot up of their Windows machine, can one use the solution here where you flush credentials via windows cmd prompt to get access to your private share with seperate creds while keeping the connection to the network drive that was established at boot up? Or is your credential flush going to kick the public share network drive off.  Thanks!

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.