I think MS just did us (and themselves) a disservice.

[Christopher R. Hertel]

:
> >It allows the IP because, by choosing the IP, you force it to connect to 
> >the *SMBSERVER generic name rather than the specific name.  Note that the 
> >IP address is equivalent to using a DNS name.
> 
> More precisely, the client observes that the server name is different than
> any it already has connected, so it places a new TCP connection.

Right, but since Windows boxes do not allow aliases, the only two options 
are the 'real' service name and the *SMBSERVER generic name.  Thus, two 
connections max.

> This is suboptimal, though, because if server, and user and workgroup are
> the same, we should be able to put the new share request down the same TCP
> connection, but if user is different, then we will automatically create a
> new connection.

In the case where Samba is the server, would reusing the existing
connection reduce the number of spawned smbd daemons?

In any case, it sounds like a worth-while optimization.

Chris -)-----

-- 
Christopher R. Hertel -)-----                   University of Minnesota
crh at nts.umn.edu              Networking and Telecommunications Services

    Ideals are like stars; you will not succeed in touching them
    with your hands...you choose them as your guides, and following
    them you will reach your destiny.  --Carl Schultz