samba - Feb 2004 - client connections to shares

Hi All,

I am wondering:
Is it possible for a windows client to use separate tcp/ip connection per
share.

Meaning that if we have SAMBA server that shares let's say three shares,
then each client that connect to those shares (tcon) will end up having
three tcp/ip connections with the server and of course there will be three
separate smbd to handle each share.

Essentially configuring SMBA that each smbd only communicate with one client
(as it does today) and only allow one share access.

Can it be configured on the client side or the server side to allow this
architecture (one smbd/tcp per client per share)

Cheers,
Ephi

On Tue, 24 Feb 2004, Ephi Dror wrote:
> Hi All,
> 
> I am wondering:
> Is it possible for a windows client to use separate tcp/ip connection per
> share.
Yes. This will happen if you use different NetBIOS names for the same 
server, or if you connect via the NetBIOS name first, and then use an IP 
address for the next use ...
 
> Meaning that if we have SAMBA server that shares let's say three
shares,
> then each client that connect to those shares (tcon) will end up having
> three tcp/ip connections with the server and of course there will be three
> separate smbd to handle each share.
>
> Essentially configuring SMBA that each smbd only communicate with one
client
> (as it does today) and only allow one share access.
> 
> Can it be configured on the client side or the server side to allow this
> architecture (one smbd/tcp per client per share) 
It can't be configured to do that, you have to play games with the 
NetBIOS name as far as I know.

Regards
-----
Richard Sharpe, rsharpe[at]richardsharpe.com, rsharpe[at]samba.org, 
sharpe[at]ethereal.com, http://www.richardsharpe.com