home share issue: //server/homes errs, while //server/<username> works
in [Samba]
|
Prev: [Samba] home share issue: //server/homes errs, while //server/<username> works
Next: Automatic change of machine passwords seems to brake trust relationship for Windows 7 clients
From: David Roid on 10 Aug 2010 03:30 Forgot to metion that mapped AD user can login with smbclient (huh, better than with windows explorer), but any further operation will hit the error below. # smbclient //localhost/homes -U <ADusername> Enter cifs5's password: Domain=[MYDOMAIN] OS=[Unix] Server=[Samba 3.5.3-1.1-2362-SUSE-CODE10] smb: \> ls do_list: [\*] NT_STATUS_OBJECT_PATH_NOT_FOUND Error in dskattr: NT_STATUS_OBJECT_PATH_NOT_FOUND "smbclient //localhost/<ADusername> -U" works just fine, again. Samba ver = 3.5.3 and the homes share is a msdfs root. 2010/8/10 David Roid <dataroid(a)gmail.com> > Hello list, > > I'm running a samba server in AD domain, with some AD users explicitly > mapped into local users by "username map = sambauser.map", which is a text > file. > > Problem is found with explicitly mapped user, I can only access home share > by //server/<ADusername>, not //server/homes (using windows explorer). This > feels wrong because I also tried those AD users not listed in the map file, > they could access home share either way. > > So it's bothering me, any idea what did I miss out anything or it's a samba > bug? > > Bests > David > -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba |