Network connection limits w/ XP Pro

I have a network with a few systems (mix of XP/Pro, XP/Home 2000/Pro)
without a domain server. On Friday I configured one of the XP/Pro (#1)
with a shared folder and one of the 2000/Pro (#2) with a shared folder.

On a 3rd computer (#3) (an XP/Pro), I had configured two network
drives to the two shared folders. However, today, the XP/Pro
network drive did not connect.

When I tried to recreate it I get the error:
<Workgroup> is not accessible. You might not have permission to use this
network resource....

No more connections can be made to this remote computer at this time
because there are already as many connections as the computer can accept.

I was told that there was a limit of 10 shared folders, but is that
on a single computer? That is, with #1, there can be 10 computers that
share it's folder? Or is there a network wide limit?

If I am up against the 10 limit, is there a way I can list where
the connections are from?

Thanks.

bru <bru@ha.com> wrote:
> I have a network with a few systems (mix of XP/Pro, XP/Home 2000/Pro)
> without a domain server. On Friday I configured one of the XP/Pro
> (#1) with a shared folder and one of the 2000/Pro (#2) with a shared
> folder.
> On a 3rd computer (#3) (an XP/Pro), I had configured two network
> drives to the two shared folders. However, today, the XP/Pro
> network drive did not connect.
>
> When I tried to recreate it I get the error:
> <Workgroup> is not accessible. You might not have permission to
> use this network resource....
>
> No more connections can be made to this remote computer at this time
> because there are already as many connections as the computer can
> accept.
> I was told that there was a limit of 10 shared folders, but is that
> on a single computer? That is, with #1, there can be 10 computers
> that share it's folder? Or is there a network wide limit?
>
> If I am up against the 10 limit, is there a way I can list where
> the connections are from?
>
> Thanks.

Try nbtstat /? at a command prompt....

Note that it's not a simple "one computer = one connection" thing. Multiple
simultaneous connections may be made by a single computer. If you're running
into this problem a lot, you need to get a server. Either Windows server or
a NAS / Linux box or something - not a workstation OS.

Lanwench [MVP - Exchange] wrote:
>
> Try nbtstat /? at a command prompt....
>
> Note that it's not a simple "one computer = one connection" thing.
> Multiple simultaneous connections may be made by a single computer.
> If you're running into this problem a lot, you need to get a server.
> Either Windows server or a NAS / Linux box or something - not a
> workstation OS.

Unless the OS on the "server" is WIN98 - it doesn't have the 10-connection
limit.

HeyBub <heybub@gmail.com> wrote:
> Lanwench [MVP - Exchange] wrote:
>>
>> Try nbtstat /? at a command prompt....
>>
>> Note that it's not a simple "one computer = one connection" thing.
>> Multiple simultaneous connections may be made by a single computer.
>> If you're running into this problem a lot, you need to get a server.
>> Either Windows server or a NAS / Linux box or something - not a
>> workstation OS.
>
> Unless the OS on the "server" is WIN98 - it doesn't have the
> 10-connection limit.

Heck, you could use two orange juice cans and a piece of string, if you want
to go back that far! :-)