Trouble with access restrictions with LS-WS LinkStation

[helpdesk]

   
I've enabled 'access restrictions'  on shared folder and granted the users and groups read/write permissions.


When I go to access the shared folder I get the login prompt and I receive an error stating that either my password or username is incorrect OR that 2 connections to the same folder at the same time isn't allowed (which isn't the case). And I know the password is correct because I'm able to log into the web admin console. The default 'admin' account doesn't work either.


I've tried enter *buffalo station name*\username and that does't work either.

Please help!

Thanks!

Message Edited by helpdesk on 06-01-2009 05:24 PM

Message Edited by helpdesk on 06-01-2009 05:24 PM

[tanjl]

   

You need to log out from the current "user" you are using now.

 

You can try these steps.

 

1) Goto My Computer and see if you have already mapped any network drives that are linked to the Terastation and right-click to disconnect it.

See if you can log in to the access-restricted share folder.

 

2) Goto Command Prompt and type "net use".

See if there are any mapped drives. Delete them by typing "net use //path & folder \DELETE"

 

3) Log out from your current Windows User and re-login again.

 

I've tried all these 3 methods at various times and so far it has work for me.

 

Let me know if you still face any problems.

 

 

[helpdesk]

   

Thanks!

 

I'll give that a shot and let you know.

[PCPiranha]

Make sure that when you are mapping shares that you map the most restricted shares first.  Windows has a limitation where it only allows you to sign in as 1 user at a time, so if you map a non restricted share first you will automatically be logged in as anonymous.

 

Other than that follow the last posters reply.

[helpdesk]

   

I'm not quite understanding the "most restricted shares first" part.

 

There are 2 ways I'm able to map to the 'share' folder - one, through the NASNavigator2 (menu>map remote default share to drive letter) and two, using Windows' normal mapping (tools>map network drive). I don't see any options on mapping restrictive or no restrictive shares.

 

In any case, I'm still having issues enabling the access restrictions on the shared folder.

 

Under shared folder I've enabled access restrictions, added every group and specific users to access folder. I do receive a prompt to enter my  username/password, but it doesn't work....even with the admin acct...which I know is correct because how else would I be able to log into the admin console. And this is after disconnecting the drives and logging out of the admin console.

 

Without the access restrictions, we can access w/o any problems.

 

 

Message Edited by helpdesk on 06-03-2009 12:52 PM

[PCPiranha]

"There are 2 ways I'm able to map to the 'share' folder - one, throughthe NASNavigator2 (menu>map remote default share to drive letter)and two, using Windows' normal mapping (tools>map network drive). Idon't see any options on mapping restrictive or no restrictive shares."

 

You can also map drives by typing in \\IP of linkstation in the run command.  This will bring up your shares and you can right click on them and go to "map network drive".

 

What I mean by mapping the most restricted share first is map the folder that has the most strict access restrictions first.  Just disconnect from all of the drives and restart the computer.  This will log your user out.  Then go back in and re map them.

 

"Under shared folder I've enabled access restrictions, added every group and specific users to access folder"

 

Also FYI if you have a user in a group and you have the user in "read only" and his group in "read/write" then he will have "read only" privelages.  It will use his most restricted permissions.

 

"I do receive a prompt to enter my  username/password, but it doesn'twork....even with the admin acct...which I know is correct because howelse would I be able to log into the admin console."

 

We generally recommend that you do not use the admin account.  If you want create a user named admin1 and give him full permissions on every folder.

 

"Without the access restrictions, we can access w/o any problems"

 

This is the reason I believe that you did not map the restricted shares first.