Am 20.04.2015 um 00:24 schrieb Andrey Repin:> First, I don't see "guest ok = yes" on your share. > Second, try with "map to guest = bad user", if you don't want to fix the link > to your domain proper.And probably you must also make sure that the user specified at "map to guest" actually exists, and has read permission in the shared directory. However even with everything configured correct, it can still feel like behaving erratic, asking for password when it should not. I think this is because two effects interact: Windows always first tries to log you on with your windows userid, and Samba always accepts local users in addition to guests - but then the passwort must be correct! If you have the same username on your local machine as on the server, but with different passwords, then it will always fail. Workaround: insist that is tries to use a non-existing userid: net use n: \\server\share /user:notexit This works fine, without asking for a password, and immediately connects as guest. A nicer solution would be map to guest = invalid password, but this has other disadvantages (described in the man page). The best solution would be if these options could be set per share, instead of only globally. Then one could make a share specifically for guests, that always just works, no matter what.
Greetings, Klaus Hartnegg!> Workaround: insist that is tries to use a non-existing userid: > net use n: \\server\share /user:notexitNote: If you do not need to map share to a disk (and I strongly suggest to NOT map, as this creates additional easy vector of attack for various malware), you can just net use \\server\share /user:notexit or net use \\server\IPC$ /user:notexit to open access to RPC share and subsequently to all other services on the host.> This works fine, without asking for a password, and immediately connects > as guest.> A nicer solution would be map to guest = invalid password, but this has > other disadvantages (described in the man page).> The best solution would be if these options could be set per share, > instead of only globally. Then one could make a share specifically for > guests, that always just works, no matter what.The best solution is to fix domain link already. -- With best regards, Andrey Repin Monday, April 20, 2015 21:51:54 Sorry for my terrible english...
Am 20.04.2015 um 20:56 schrieb Andrey Repin:> Note: If you do not need to map share to a disk (and I strongly suggest to NOT > map, as this creates additional easy vector of attack for various malware), > you can justI found scripts to run more than 10 times slower when this is done.
Virussus and mailware these days dont bother about looking for a mapped drive.. They just follow the "recently opened .... " (fill in the dots.. documents/network locations , etc etc. ) and i know, i tested against cryptovirus.. And i'm asuming everybody knows : http://www.computerworld.com/article/2485214/microsoft-windows/cryptolocker-how-to-avoid-getting-infected-and-what-to-do-if-you-are.html?page=2 ;-) a nice one to read.. Greetz, Louis>-----Oorspronkelijk bericht----- >Van: hartnegg at uni-freiburg.de >[mailto:samba-bounces at lists.samba.org] Namens Klaus Hartnegg >Verzonden: dinsdag 21 april 2015 15:28 >Aan: samba at lists.samba.org >Onderwerp: Re: [Samba] Map to Guest not working > >Am 20.04.2015 um 20:56 schrieb Andrey Repin: >> Note: If you do not need to map share to a disk (and I >strongly suggest to NOT >> map, as this creates additional easy vector of attack for >various malware), >> you can just > >I found scripts to run more than 10 times slower when this is done. >-- >To unsubscribe from this list go to the following URL and read the >instructions: https://lists.samba.org/mailman/options/samba > >