I can not connect to a password protected share from my Mac

Yes. It is off.

I have a few more questions:

First:
I do not understand this statement:

"Do you have CIFS enabled for each share?"

What is the difference between "enable CIFS" and "enable the correct Read Write permissions for a user or group"?

ie, how do I "enable" a protocol? What makes the icon in the share listing go from greyed out to either black or red? Here is what I've observed:
If the share permissions are set to disabled, and there are no exceptions, the icon appears greyed out
If the share permissions are set to read/write, the icon appears black
If the share permissions are set to disabled, and there are user/group/hostname exceptions, the icon appears red

I'm going to assume that in order to "enable" a protocol, I only have to give some form of access, whether it's restricted or not.

From reading the document you referred to:
http://sphardy.com/web/readynas/how-to- ... rmissions/
The menu that says "Default Access" is not used for turning a share on or off. It's for setting the share permissions.

The doc says that: "this only controls whether a user or host can, or cannot, access the share." It doesn't say anything like "this controls whether a share is available over a specific protocol."

Please tell me if my understanding of how to "enable" a protocol is correct.

Second:
About share permissions.
According to the same document, if I want the following configuration:

Group rt: R/W
Other (guest, nogroup, etc): NO ACCESS. NOT EVEN READ

I should choose:

Default Access: Disabled
Write-enabled users/groups: rt
(I assume this also allows Read access for this group)

According to what the document says, this should disable the default access for any user. Users in group rt should have read/write on the share. (For file permissions, I've just kept them all at 666/777)

When I apply these settings, The icon on the share listing turns from black to red. I'm not sure what this means. Does this mean there is an error in my configuration? Or does it mean simply that this share has restricted access?


I would like someone to please answer these questions:

1. How do I enable a protocol on a share? (is it different from setting the share permissions? Is my understanding correct?)
2. When I restrict share permissions, the icons in the share listings turn from black to red. Red generally means "error". Is this telling me I have an error in my configuration? Or is this simply telling me I have restricted permissions?
3. If I want group:rt R/W, other:NO access (not even read). Can you confirm that the share should be set up as I specified above.

traceypowers wrote:
I created a brand new share with default permissions. CIFS and AFP are both enabled. I cannot connect to it from windows. Same error as before.

Before trying to address any of your more recent questions - the above issue *must* be fixed first. If you create a new share, with default CIFS settings (ie Default Access = Read/Write) and cannot access the share from windows, then you have a fundamental setup issue and proceeding with access restrictions is pointless

Going back to default settings is key. So try creating a new account on your NAS with default settings to ensure your issues are not related to NAS account settings. Also try testing with a new account on your PC to ensure your standard account is not contributing the problem

Okay. Here is exactly what I have done, per your request:

1. Create a new user called testuser. Group is users. No password is set for this user
2. Create a new share called testshare. Default configuration - Read/Write. Enabled for CIFS and AFP

On windows machine:

Map Network drive:
Attempt 1:
share: \\powers-nas\testshare
user: testuser@powers-nas

Attempt 2:
share: \\192.168.1.2\testshare
user: testuser@powers-nas

Both resulted in the same error:

Error code: 0x80070035
The network path was not found.

Clicking "Diagnose" returns this error message:
"powers-nas" is not set up to establish a connection on port "File and printer sharing (SMB)" with this computer.

Attempt 3:
Allow guest access on the new share
Again, tried Map Network Drive:
share: \\powers-nas\testshare
<no user>
<no password>

Same error message as before.

Also tried connecting by IP.

Also tried to map the drive by choosing Network > Add Network Location > Custom Location:
\\powers-nas\testshare
Also tried by IP:
\\192.168.1.2\testshare

Both resulted in the error message:
The folder you entered does not appear to be valid. Please choose another.

Have I done this test case correctly? Or have I missed something?

The correct syntax for the user is powers-nas\testuser

Okay. That has changed. I always used to log in with the syntax I posted.

I just tried it with the syntax you suggested.

No connection. Same error.

Okay. That has changed. I always used to log in with the syntax I posted.

I just tried it with the syntax you suggested.

No connection. Same error.

It also doesn't explain why I can't connect with no user. In order to connect as guest, I never used to have to enter a username.

I tried connecting with no username, with powers-nas\guest, and also with powers-nas\testuser.

Same error.

I see a thread from someone who had the same exception here: http://social.technet.microsoft.com/For ... 61fb92082/

For what it's worth department. I tried ALL the above suggestions to no avail but in my case the following worked for my situation. Go to Control Panel Go to Credential Manager on each Windows 7 machine on the network Under Windows Credentials, type in the name of each machine, username and password It sounds too simple but it worked for me. The shared files and folders popped right up after this!

I've seen weird behaviour too due to the Credential Manager. I tried using it for a short while but it just caused access issues and instead I went the other way and deleted all entries from it.