[Samba] Upgraded from 2.2.7a to 3.0.0 - funny with roaming profiles

[Rob MacGregor]

Well, I did a test install of 3.0.0 today (different base from the old 
2.2.7a incase it all went wrong).  Everything seems to work (minor glitch 
failing to read the documentation carefully enough), but the roaming 
profiles appear to be broken.

What I'm seeing is that the profile isn't loaded and a vaguely default 
profile is provided instead.  I'm not seeing any error messages though, 
which is odd.  If somebody could run a quick eye over the (snipped) smb.conf 
I'd be grateful.  I'm probably missing something obvious, but it's late and 
I've read the file too many times to spot it:

[global]
<---SNIP--->
	logon script = logon.cmd
	logon path = \\%N\Profiles\%U
	logon drive = H:
	logon home = \\archie\%u
	domain logons = Yes

[profiles]
	path = /disk2/home/profiles
	read only = No
	create mask = 0600
	directory mask = 0700
	profile acls = Yes


Incase it matters the client is WindowsXP, SP1 (happily working in the 
domain hosted by 2.2.7a) and samba is running on Mandrake 9.1, stock 
Mandrake 2.4.20 kernel.

TIA


  Please DO NOT send me ANY email directly unless it's a privacy issue.
       Reply-to mangled to assist those who don't read the above.
--
Rob  |  What part of "no" was it you didn't understand?

_________________________________________________________________
Find a cheaper internet access deal - choose one to suit you. 
http://www.msn.co.uk/internetaccess