Yesterday i purchased WD Sharespace 4TB. Firmware version 2.3.01. the above has been sucessfully joined in our win 2003 domain. I have created a share folders. As long as the public access is enabled, the shared folders are visible and accessable. Once i assigned AD group and user access to the above folders, it is not visible in user computers. Can any one help me in solving this issue?
are you using 2003 server for small business? because if you join to a domain it won’t work. also, are you on the same workgroup as your computer? did you set the share to a user? did you correctly set permissions. if you don’t know any of these, then I recommend you contact wd’s support for help setting it up.
Why get the ShareSpace instead of the Sentinel?
1.We’re using 2003 R2 Enterprise Edition.
- Computer also in the same domain
3.From the user computer, when i m trying to map the WD, I can able to see the share folders that are public access option enabled. whereas, share folders that are assigned for domain users, not visible.
that’s because you have to associate a user to the share to be able to see it. public is for everyone. anything that is not in public domain is not for everyone. you must figure who you want to have access to the share and then assign that user, with whatever permissions you want, to that share.
[edit]
actually, are you sure that you’ve properly joined the domain, and that you are not having compatibility conflicts? I would check out this article from wd to make sure.
ganeshraju wrote:
Yesterday i purchased WD Sharespace 4TB. Firmware version 2.3.01. the above has been sucessfully joined in our win 2003 domain. I have created a share folders. As long as the public access is enabled, the shared folders are visible and accessable. Once i assigned AD group and user access to the above folders, it is not visible in user computers. Can any one help me in solving this issue?
Where did you assign the access, on the Sharespace or in AD? The SS is obviously not going to sync with your AD settings, so you need to enter each user/password in the SS user config, right?
Also, are you expecting the folder to show up as a share in Explorer by default, or have you tried to map a network drive to that folder from the user’s computer?
I’ve had similar problems using SMB under OS X, and had to initially force the connection from the individual computer.
OttoW wrote:
ganeshraju wrote:
Yesterday i purchased WD Sharespace 4TB. Firmware version 2.3.01. the above has been sucessfully joined in our win 2003 domain. I have created a share folders. As long as the public access is enabled, the shared folders are visible and accessable. Once i assigned AD group and user access to the above folders, it is not visible in user computers. Can any one help me in solving this issue?
Where did you assign the access, on the Sharespace or in AD? The SS is obviously not going to sync with your AD settings, so you need to enter each user/password in the SS user config, right?
Also, are you expecting the folder to show up as a share in Explorer by default, or have you tried to map a network drive to that folder from the user’s computer?
I’ve had similar problems using SMB under OS X, and had to initially force the connection from the individual computer.
OSX has known issues with SMB. Thats likely not related.
Ardvark wrote:
OttoW wrote:
ganeshraju wrote:
Yesterday i purchased WD Sharespace 4TB. Firmware version 2.3.01. the above has been sucessfully joined in our win 2003 domain. I have created a share folders. As long as the public access is enabled, the shared folders are visible and accessable. Once i assigned AD group and user access to the above folders, it is not visible in user computers. Can any one help me in solving this issue?
Where did you assign the access, on the Sharespace or in AD? The SS is obviously not going to sync with your AD settings, so you need to enter each user/password in the SS user config, right?
Also, are you expecting the folder to show up as a share in Explorer by default, or have you tried to map a network drive to that folder from the user’s computer?
I’ve had similar problems using SMB under OS X, and had to initially force the connection from the individual computer.
OSX has known issues with SMB. Thats likely not related.
Uh, yeah, you’re right about those known problems. Under OS X, mainly browsing and transfer speed. Far as I can see on this forum, that’s an issue across the board with this **bleep** RAID. However: The thrust of my questions is whether the OP assigned user rights to the shares through AD, expecting those permissions to transfer to the SS shares as they would for OS native shares, or whether he assigned the user permissions through the SS control panel, which is what he will need to do in order for his AD users to gain access to the shares.
