FIX: NT sending null username effects %U expansion

[Luke Kenneth Casson Leighton]

On Thu, 29 Oct 1998 thwartedefforts at wonky.org wrote:

> On Wed, 28 October 1998, Jeremy Allison wrote:
> <snip>
> > I think your patch is nearly correct - the actual intent
> > of the original code is :
> > 
> >    if((lp_security() != SEC_SHARE) || (*user && !guest))
> >       pstrcpy(sesssetup_user,user);
> <snip> 
> > The intent was only to change sesssetup_user in share level
> > security when a valid username was given.
> 
> Well, you see I'm trying to work around (what Luke described as) a
>  bug in NT4.  It insists on sending a null username/password when it
>  requests subsiquent share lists (it seems to send the logon
>  username/password for the initial request).  This screws up the list
>  of configuration files read and shares disappear and reappear
>  depending on the mood of NT4.

kit's not a bug in nt4: it's just that we have different processes for
each connection.  the _first_ connection, in one smbd process, must jave
the username etc.  the _second_ connection does not, because that's in a
separate smbd process.