News:

RAID is not a replacement for a backup! Here's why.

Main Menu

Cannot create files/folder inside my authenticated folders

Started by askme, May 12, 2009, 07:43:36 AM

Previous topic - Next topic

askme

   

I am using LinkStationQuad LS-QL238 Model is LS-QL F/W1.02

 

Here is my setup, what I have done.

 

I have Domain setup on Windows Server 2003 named MyCompany.local I have around 30 Windows Vista client using this Domain to authenticate. All computers are in same LAN (IP 192.168.10.x/24). I have DNS and Active Directory and all IP addresses are assigned manually. I have connected and configured LS-QL238 and it is working fine without any folder restriction.

I have also created Host(A) record in DNS for LS-QL238 named ls-ql238.mycompany.local and it can resolve and ping with this name. I have also created Computer name (since LS-QL238 did not registered autometically like my other domain users computer did) LS-QL238 in active directory computer list and configured it as Pre_windows 2000 client machine (as I read somewhere in this forum)

 

Problem 

 

When I tried to assign users restriction authenticate to my active directory, by supplying domain name (mycompany.local) and Active Directory IP in WINS and authentication server also as Active Directory PC IP. I cannot access even non-restricted folder. It seems that when I supplied (in pop up authentication windows) I cannot even access any folder (open or restricted) even with valid Active Directory user name and password. And also LinkStation web admin folder accress username and group don't populate with my Active directory users and group.

 

When I restrict folder with LinkStation created users and group through webadmin, I can authenticate and open restricted folder but cannot create files or folder inside it. But I can create files and folder inside the non-resticted folder. 

 

Please advice me how to solve Ative Directory Users and Group restriction to folder other LinkStation created User and group I mentioned above.

Jason

The LS Quad does not have any ability to communicate or join an Active Directory domain. To have one of our NAS boxes join an AD domain it would need to have those options available in the web interface, asking for domain controller name, dns hostname of domain, net bios name of domain, etc. This model does not have this. I suggest you just set the workgroup settings back to default and attempt to use the users and groups created in the web interface to set restrictions.

Browser ID: smf (is_webkit)
Templates: 4: index (default), Display (default), GenericControls (default), GenericControls (default).
Sub templates: 6: init, html_above, body_above, main, body_below, html_below.
Language files: 5: index+Modifications.english (default), Post.english (default), Editor.english (default), Drafts.english (default), StopForumSpam.english (default).
Style sheets: 4: index.css, attachments.css, jquery.sceditor.css, responsive.css.
Hooks called: 135 (show)
Files included: 35 - 1354KB. (show)
Memory used: 975KB.
Tokens: post-login.
Queries used: 19.

[Show Queries]