Re: Shared Network Path Unavailable
- From: "Willy Denoyette [MVP]" <willy.denoyette@xxxxxxxxxx>
- Date: Thu, 18 Aug 2005 16:06:18 +0200
"Rahul Anand" <RahulAnand@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A0DF69EF-B8B2-406B-AB7D-F93578A2CD32@xxxxxxxxxxxxxxxx
> Hi Willy,
>
> Thanks for your response.
>
> There are times when session count reraches 0 but #Connections is not 0.
> Not able to understand the behavior but sometimes session count reaches 0
> but #connection is 2 (Maxconnection) and that causes refusal to further
> connections to that folder.
>
Not sure what you are looking at and what tol you are using to get at these
figures, as far as I know there is no such thing like connections on a
LanManager share. There are sessions that are bound to client logon sessions
and there are opens which be part of multiple sessions. If you have 2 as
max. number of users (I guess this is what you mean with #connection) you
can have at most two (user) sessions open to the share, but one single user
can have multiple files and folders open at any one time. So I realy don't
see what you may have as problem, unless you are trying to open more than 2
sessions. In the latter case you should know that LM keeps a session open
for a OS specific time-out period after the last file has been closed.
Willy.
.
- Follow-Ups:
- Re: Shared Network Path Unavailable
- From: Rahul Anand
- Re: Shared Network Path Unavailable
- References:
- Shared Network Path Unavailable
- From: Rahul Anand
- Re: Shared Network Path Unavailable
- From: Willy Denoyette [MVP]
- Re: Shared Network Path Unavailable
- From: Rahul Anand
- Shared Network Path Unavailable
- Prev by Date: Re: What does '@' prefix on strings in C# do?
- Next by Date: Re: What does '@' prefix on strings in C# do?
- Previous by thread: Re: Shared Network Path Unavailable
- Next by thread: Re: Shared Network Path Unavailable
- Index(es):
Relevant Pages
|