XP vs Win7 public share issue

[TheFax]

Another detail: using my girlfriend's PC all works perfectly*... (same OS, same workgroup, same network settings, same NAS)...
It's very strange. I'm sure that something in my PC is going wrong.
When I will find the issue, I will inform you.
I have a suspect: the username of my windows account and the name of the user I created in the NAS are the same word... I think this can be the cause.



*all works perfectly means that:
-I can browse the root of the NAS (\\QNAP) without any password;
-I can read and write on Public Share without any password;
-If I try to enter into a private share, Windows ask me for the password.

[TheFax]

Issue found...

As I said in my last message, if the username of Windows account and the username of the QNAP are the same word, something strange happens .
In order to solve my problem, I deleted the username I created some days ago in the NAS and I added a new user, called with another word.
Now all works perfectly.

[doktornotor]

I do not understand what this "new user, called with another word" means, but if you mean that having the usernames identical on Windows and QNAP causes the issue, then no, absolutely not - in fact it avoids them! What might be causing your issue - you again set one password on Windows and and a different one on QNAP.

[TheFax]

doktornotor, sorry for my english...
What you are saying is correct: if your username is the same on the NAS and on Windows, and you are using windows without a password... can be a problem. (This was my situation). I don't know if the problem is present also if you have different passwords.

So, if you use windows without a password, everytime you try to browse your NAS (or you try to browse into the Public Share), Windows ask you for the NAS username/password.
The problem is that I don't want to write username/password to access to the Public Share and I don't want to write user/pass for browse the main directory of the NAS (\\QNAP\).

The solutions that I tried are 3:
1) add a password on windows account (but, everytime you turn on your computer, it ask you for the password)
2) add a credential using control panel
3) use different usernames

I'm not saying that these solutions are the safest. But I think in a home environment are acceptable.

Please correct me if I'm wrong. I'm not here to make confusion, but to help others who may have the same problem.

I also will wait the feedback of atakacs...

[doktornotor]

1) add a password on windows account (but, everytime you turn on your computer, it ask you for the password)

Yes, that is indeed a "huge" problem. Not to mention - Auto-Login Your Windows 7 User Account.

[atakacs]

Just wondering what's the point of the NAS "public" share if it is not public ?

[doktornotor]

The share is public just fine (if they called it Default instead of Public, would you be happy?) I thought I has been already explained in quite some detail that the whole "problem" is with client configuration here, not with QNAP.

[atakacs]

-I can browse the root of the NAS (\\QNAP) without any password;
-I can read and write on Public Share without any password;
-If I try to enter into a private share, Windows ask me for the password.

Consider yourself as lucky.

this is exactly what I would like and being told is not possible...

Are you using a AD domain ? If so is your QNAP joined ?
If not did you create users on the QNAP that match the user / pass of the locally loged in users on the Windows stations ?

[TheFax]

-I can browse the root of the NAS (\\QNAP) without any password;
-I can read and write on Public Share without any password;
-If I try to enter into a private share, Windows ask me for the password.

Consider yourself as lucky.

I'm lucky if i can browse the public share of my QNAP without a password?

Are you using a AD domain ? If so is your QNAP joined ?
If not did you create users on the QNAP that match the user / pass of the locally loged in users on the Windows stations ?

I'm not using an AD domain.
At this moment I don't have user or pass matching between Windows and QNAP.

What you suggest? I'm here to learn. I'm interested.


doktornotor » Tue May 15, 2012 8:57 pm...
schumaku » Tue May 15, 2012 5:01 pm...
your ironic answers do not help me at all.

[schumaku]

I'm lucky if i can browse the public share of my QNAP without a password?

No - it's standard.

Windows Users will get a username/password prompt shown on accessing a share when

- The Windows desktop login credentials don't match, but credential are required
- Stored credentials exist specifically for the Public share, which are not known, password does not match, ...
- Access is denied somehow, for a user, for a usser group, but you are retrying the access

A whatever user from a windows (any) sytem, with or without a password for the desktop login, will be able to get public (non-authenticated) access to a share configured accordingly in a workgroup.

[atakacs]

Hi

- The Windows desktop login credentials don't match, but credential are required

ok what can I change on the QNAP side to make credentials not required ?

- Stored credentials exist specifically for the Public share, which are not known, password does not match, ...

none are set client side

- Access is denied somehow, for a user, for a usser group, but you are retrying the access

anything in the QNAP logs to identify what authentication has been attempted / has failed ?

[schumaku]

a) ensure there are no groups or users set to [deny]
b) set the "Guest Access Right: Full access"
b') do not try to add any access rights for a user named "guest"
c) ensure the ACLs are fully deployed with the Advanced Folder Permissions enabled, and the ACLs are fully replaced on the Piblic share tree
d) ensure the Microsoft Networking Host Access Control (per share) don't prohibit the access

That's all I can think of ...

Post the [Public] section of /etc/smb.conf - example:

[Public]
comment = System default share
path = /share/MD0_DATA/Public
browsable = yes
oplocks = yes
ftp write only = no
public = yes
invalid users = "ftp","homedir"
read list =
write list = "admin",@"everyone","guest"
valid users = "root","admin",@"everyone","guest"
inherit permissions = yes

Post the ACL on the Public storage directory - use /share/HDA_DATA/Public if it's a single disk volume, ...HDB_DATA for the second single disk, ...:

[~] # getfacl /share/MD0_DATA/Public
getfacl: Removing leading '/' from absolute path names
# file: share/MD0_DATA/Public
# owner: admin
# group: administrators
user::rwx
user:admin:rwx
user:guest:rwx
group::---
group:everyone:rwx
mask::rwx
other::rwx
default:user::rwx
default:user:admin:rwx
default:user:guest:rwx
default:group::rwx
default:group:everyone:rwx
default:mask::rwx
default:other::---

[TheFax]

Thankyou schumaku for your answers.
For me the problem is solved (I finally created two users with the same name, and I added a password in Windows, as recommended by you), but, just out of curiosity, I went to see the permissions of my Public folder and the folder should be private...

PUBLIC:

Code: Select all

[~] # getfacl /share/HDA_DATA/Public
getfacl: Removing leading '/' from absolute path names
# file: share/HDA_DATA/Public
# owner: admin
# group: administrators
user::rwx
group::rwx
other::rwx


PRIVATE:

Code: Select all

[~] # getfacl /share/HDA_DATA/Backup
getfacl: Removing leading '/' from absolute path names
# file: share/HDA_DATA/Backup
# owner: admin
# group: administrators
user::rwx
group::rwx
other::rwx


the difference between your post and what I saw via ssh, surprised me.

[schumaku]

the difference between your post and what I saw via ssh, surprised me.

By default, the access right are share-based only. MY examples come from NAS with Advanced Folder Protection (ACL Support) enabled and fully deployed. If you want to keep things simple, this is cocmmonly enough.