NTDOM: remote profile created, but automatic logoff?

[Luke Kenneth Casson Leighton]

On Thu, 12 Feb 1998, Tyler Saxton wrote:

> 
> I'm been trying to get the BRANCH_NTDOM samba source code to work as a
> primary domain controller for some NT workstations in a small computer
> room.
> 
> In the smb.conf file, I have set:
> 
> logon path = \\samba-server\profiles\%U\profile
> 
> and when I try to log into the samba domain for the first time for a user,
> the directory %U/profile is created in the "profiles" share, and filled
> with ntuser.dat, and other directories and files like "application data",
> "desktop", etc.  (All files are created with their names in lower case.)

check out the standard samba case sensitivity and case preserve options.
see smb.conf.
 
> So, it looks to me like the remote profile for the user is created
> successfully.  However, after entering the username and password on the NT
> machine, what I see is the "Microsoft Windows NT Workstation 4.0..." logo
> disappear, leaving a blank background, and then after a short time, I get
> prompted to logon again, without any error messages or explanation.

oops.  bugger.  ok.  can you do the standard debugging procedure, which i
would appreciate everyone doing if reporting difficulties like this:

- increase debug log levels to 150 check there are no
"INTERNAL..." messages; 

- core dump check (related to above)

- run NetMonitor on an NT server somewhere.  first run NetMonitor, _then_
start smbd (killall smbd; ./smbd) this is important, as connections may
have been established on the \PIPE\NETLOGON, and NetMonitor will not be
able to decode things properly unless it "sees" the connection being
established as well as the data.

- alternatively: run tcpdump, and obtain capconvert.c from the samba site
ftp://samba.anu.edu.au/pub/samba/tcpdump-smb/capconvert.c and convert the
tcpdump output to a .cap file.


> I've also tried to copy a local profile across manually, using the System
> Control Panel, with the same results.

hm.  try _without_ a profile what happens? set profile path = ""
 
> The DOMAIN.txt document mentions having to create a .PDS directory by
> hand...  I'm not sure where exactly to do this (path) what to put in it,
> or if it's relevant -- At one stage NT did complain that it couldn't
> create a \\samba-server\profiles\user\profile.pds directory, but that was
> before I was getting profiles transferred across properly, I think.  It
> doesn't say that now, anyway.

good.

luke