Gargoyle Forum

ysy wrote:thanks again for everything!

Have you tired the fix?

viewtopic.php?f=14&t=11305

applied new codes (https://github.com/ericpaulbishop/gargo ... /680/files) and tried the following setup, is the behavior to be expected?

files with new codes applied:
/etc/init.d/samba
/etc/samba/smb.conf.template

setup: -
_________usr1_______usr2_______usr3
share1____rw
share2____rw_________ro
share3____rw________________anonymous,ro

a) removed windows credentials, reboot pc and router. both share1 and share2 prompted for usr/pwd, while share3 offered instant anonymous access. perfect.

b) selected share2 and enter usr2's read only pwd, share2 granted ro access which is good; but share1 won't allow access despite entering the correct usr1's pwd, and share3 also denied anonymous access.

c) ran windows cmd 'net use * /delete', took ~10sec to settle and to regain share3 anonymous access, and the pwd prompts for share1/2. looks good.

d) selected share1 and entered usr1's rw pwd, access granted to all shares as expected.

I can get around b), by defining an alternative route \\192.168.1.1\share1, when \\GARGOYLE\share2 is active.

I won’t say “expected”, but it is an unfortunate behaviour of Windows.
I believe if you attempt to connect to a share:
1) Windows first tries your windows login against the share to see if that works
2) tries the current login for other shares at the same IP
3) prompts for password if nothing works

The same tests under Linux act much nicer.
I think your workaround is good thinking. If it works it might be nice to document in the wiki

learned something new. cheers!