homes share mapping problem in samba 3

Milewski, Evan evan.milewski at
Tue Jun 1 19:48:34 GMT 2004

The homes share is not mapping properly anymore once upgrading to samba 3.
This works without problems in samba 2.2.8a and 3.0.0.  However I have seen
this problem consistently in 3.0.1, 3.0.2, 3.0.3 and 3.0.4; if I go back to
2.2.8a then the problem goes away.  I have searched the newsgroups and
others have had the same problem, but no one had found a solution and said
that "homes" as a mapping was no longer supported (which I am hoping is not
the case). 

>From windows 2000 clients, I have an NT profile home drive mapping to
\\MachineName\homes.  When I sign on this does not map and I get a message
in the log.smbd file of "Can't become connected user!".  If mapping manually
it says "network path not found".  If I change this to
\\MachineName\Username (where Username is my login ID) then it works fine;
it is the generic "homes" mapping that broke in 3.0.1 and up.  Any help
would be greatly this a bug, or is this officially not
supported anymore in samba 3?

[2004/06/01 15:30:59, 2] smbd/uid.c:(205)
  change_to_user: Invalid vuid used 103 or vuid not permitted access to
[2004/06/01 15:30:59, 0] smbd/service.c:(541)
  Can't become connected user!
[2004/06/01 15:30:59, 2] smbd/service.c:(72
  [homes] share not available for this user because it was not found or
created at session setup time


	workgroup = EHSAMBA
	security = domain
	password server = pusehc0j pusehc0k
	name resolve order = wins host bcast
	deadtime = 5
	encrypt passwords = yes
	invalid users = nobody
	local master = no
	lm announce = False
	wins server =
	lock dir = /pw/export/prod/svr4/samba/locks
	delete readonly = yes
	log level = 1

	comment = Home Directories
	read list = nobody
	read only = No
	create mask = 0777
	directory mask = 0755
	browseable = No

More information about the samba-technical mailing list