how many browser connections, and do mapped drives count?

Hi,
Seems like I should know this (or at least be able to find it definitively,
but I can't). How many browser connections will a W2K3 server support at
once? Does that number of connections include mapped network drives, or not?
I have a server which really gets very little use: there aren't more than
5-10 other XP systems on the net with it, yet people are frequently locked
out with the "too many connetions" error. Sometimes you can get it, other
times not. This is the first time I've even thought about how many *browser*
connections a server could support - did something change between win 2000
server and W2K3?
help?
Trink

"trink" wrote:

> Hi,
> Seems like I should know this (or at least be able to find it definitively,
> but I can't). How many browser connections will a W2K3 server support at
> once? Does that number of connections include mapped network drives, or not?
> I have a server which really gets very little use: there aren't more than
> 5-10 other XP systems on the net with it, yet people are frequently locked
> out with the "too many connetions" error. Sometimes you can get it, other
> times not. This is the first time I've even thought about how many *browser*
> connections a server could support - did something change between win 2000
> server and W2K3?
> help?
> Trink
by *browser* do you mean windows explorer uesrs visiting \\servername\share ?
if you do, what licensing model did you choose at install? (did you specify
the number of CALs you have, or did you state that each client should have
it's own CAL ?

By browser I mean folks trying to get there by opening and explorer, network
neighborhood, and winnowing their way to my domain and server. As soon as
they click the domain, they get a refusal to connect. I have specified that I
have 20 CALs, but there can't be even close to that number of machines
trying to connect. This system is also a terminal server, but that licensing
seems to be going as it should... (even though I have issues with not being
able to reset a license once it's been dished out).
Trink

"Ewan" wrote:

>
>
> "trink" wrote:
>
> > Hi,
> > Seems like I should know this (or at least be able to find it definitively,
> > but I can't). How many browser connections will a W2K3 server support at
> > once? Does that number of connections include mapped network drives, or not?
> > I have a server which really gets very little use: there aren't more than
> > 5-10 other XP systems on the net with it, yet people are frequently locked
> > out with the "too many connetions" error. Sometimes you can get it, other
> > times not. This is the first time I've even thought about how many *browser*
> > connections a server could support - did something change between win 2000
> > server and W2K3?
> > help?
> > Trink
> by *browser* do you mean windows explorer uesrs visiting \\servername\share ?
> if you do, what licensing model did you choose at install? (did you specify
> the number of CALs you have, or did you state that each client should have
> it's own CAL ?

hi,

I last saw this issue on windows 2000 - see MS article Q302099.
I see q328459 also exists for XP

This article does not appear to cover w2k3, but it could be that the issue
occurs in your configuration.
As long as you are not connecting more users then you are licensed for (i
have only ever worked in environments where all clients have their own CAL -
licences not attached to a particular server) it might be interesting to
double the llicense number and see what happens

what edition of w2k3 are you using, and what service pack / hotfix level? I
can't see any kb's for this os, though i haven't spent much time searching

ewan

"trink" wrote:

> By browser I mean folks trying to get there by opening and explorer, network
> neighborhood, and winnowing their way to my domain and server. As soon as
> they click the domain, they get a refusal to connect. I have specified that I
> have 20 CALs, but there can't be even close to that number of machines
> trying to connect. This system is also a terminal server, but that licensing
> seems to be going as it should... (even though I have issues with not being
> able to reset a license once it's been dished out).
> Trink
>
> "Ewan" wrote:
>
> >
> >
> > "trink" wrote:
> >
> > > Hi,
> > > Seems like I should know this (or at least be able to find it definitively,
> > > but I can't). How many browser connections will a W2K3 server support at
> > > once? Does that number of connections include mapped network drives, or not?
> > > I have a server which really gets very little use: there aren't more than
> > > 5-10 other XP systems on the net with it, yet people are frequently locked
> > > out with the "too many connetions" error. Sometimes you can get it, other
> > > times not. This is the first time I've even thought about how many *browser*
> > > connections a server could support - did something change between win 2000
> > > server and W2K3?
> > > help?
> > > Trink
> > by *browser* do you mean windows explorer uesrs visiting \\servername\share ?
> > if you do, what licensing model did you choose at install? (did you specify
> > the number of CALs you have, or did you state that each client should have
> > it's own CAL ?

i'm adding a post as i didn't notice first time you write that when clients
connect to your domain. can you elaborate with:
sample unc path that causes the error (is this on a domain controller)
stupid question: are the clients members of the domain (do the computers
have accounts in the domain?)

"trink" wrote:

> By browser I mean folks trying to get there by opening and explorer, network
> neighborhood, and winnowing their way to my domain and server. As soon as
> they click the domain, they get a refusal to connect. I have specified that I
> have 20 CALs, but there can't be even close to that number of machines
> trying to connect. This system is also a terminal server, but that licensing
> seems to be going as it should... (even though I have issues with not being
> able to reset a license once it's been dished out).
> Trink
>
> "Ewan" wrote:
>
> >
> >
> > "trink" wrote:
> >
> > > Hi,
> > > Seems like I should know this (or at least be able to find it definitively,
> > > but I can't). How many browser connections will a W2K3 server support at
> > > once? Does that number of connections include mapped network drives, or not?
> > > I have a server which really gets very little use: there aren't more than
> > > 5-10 other XP systems on the net with it, yet people are frequently locked
> > > out with the "too many connetions" error. Sometimes you can get it, other
> > > times not. This is the first time I've even thought about how many *browser*
> > > connections a server could support - did something change between win 2000
> > > server and W2K3?
> > > help?
> > > Trink
> > by *browser* do you mean windows explorer uesrs visiting \\servername\share ?
> > if you do, what licensing model did you choose at install? (did you specify
> > the number of CALs you have, or did you state that each client should have
> > it's own CAL ?

now that's an interesting question... it *is* a domain controller, but
computers both in and out of the domain have been getting this error. All
users have accounts in the domain, but never get a chance to prove it with a
challenge login box. I haven't posted a url because that's not the
methodology that causes the problem. In other words, when folks explicitly
map a drive to \\eclipse\5600, it usually works, but when they open the
network neighborhood, go through the entire network, MS windows network, and
then try to select the domain they get the error. At that point, (I can
verify that my system has this error on my screen right this second) they get
"(domain) is not accessible. You might not have permission to use this
network resource. contact the administrator of this server to find out if you
have access permissions. 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." My machine is a member of a domain with a two-way trust
with the domain in question. Is there any way to see *all* the connections
the server thinks it is supporting at any given moment?
Trink


"Ewan" wrote:

> i'm adding a post as i didn't notice first time you write that when clients
> connect to your domain. can you elaborate with:
> sample unc path that causes the error (is this on a domain controller)
> stupid question: are the clients members of the domain (do the computers
> have accounts in the domain?)
>
> "trink" wrote:
>
> > By browser I mean folks trying to get there by opening and explorer, network
> > neighborhood, and winnowing their way to my domain and server. As soon as
> > they click the domain, they get a refusal to connect. I have specified that I
> > have 20 CALs, but there can't be even close to that number of machines
> > trying to connect. This system is also a terminal server, but that licensing
> > seems to be going as it should... (even though I have issues with not being
> > able to reset a license once it's been dished out).
> > Trink
> >
> > "Ewan" wrote:
> >
> > >
> > >
> > > "trink" wrote:
> > >
> > > > Hi,
> > > > Seems like I should know this (or at least be able to find it definitively,
> > > > but I can't). How many browser connections will a W2K3 server support at
> > > > once? Does that number of connections include mapped network drives, or not?
> > > > I have a server which really gets very little use: there aren't more than
> > > > 5-10 other XP systems on the net with it, yet people are frequently locked
> > > > out with the "too many connetions" error. Sometimes you can get it, other
> > > > times not. This is the first time I've even thought about how many *browser*
> > > > connections a server could support - did something change between win 2000
> > > > server and W2K3?
> > > > help?
> > > > Trink
> > > by *browser* do you mean windows explorer uesrs visiting \\servername\share ?
> > > if you do, what licensing model did you choose at install? (did you specify
> > > the number of CALs you have, or did you state that each client should have
> > > it's own CAL ?

hey, maybe this can help... here's an nbtstat -n printout (I deleted our IP
addresses, for obvious reasons):

C:\Documents and Settings\Administrator>nbtstat -n

Local Area Connection 2:
Node IpAddress: [xxx.xxx.xxx.50] Scope Id: []

NetBIOS Local Name Table

Name Type Status
---------------------------------------------
ECLIPSE <00> UNIQUE Registered
ECLIPSE <20> UNIQUE Registered
VAULT <00> GROUP Registered
VAULT <1C> GROUP Registered
VAULT <1E> GROUP Registered
VAULT <1D> UNIQUE Registered
..__MSBROWSE__.<01> GROUP Registered
VAULT <1B> UNIQUE Registered
ECLIPSE <03> UNIQUE Registered
ALLMAN <03> UNIQUE Registered

Local Area Connection:
Node IpAddress: [xxx.xxx.xxx.49] Scope Id: []

NetBIOS Local Name Table

Name Type Status
---------------------------------------------
ECLIPSE <00> UNIQUE Registered
ECLIPSE <20> UNIQUE Registered
VAULT <00> GROUP Registered
VAULT <1C> GROUP Registered
VAULT <1E> GROUP Registered
VAULT <1B> UNIQUE Registered
ECLIPSE <03> UNIQUE Registered
ALLMAN <03> UNIQUE Registered

now, sorry to be uneducated about this, but I also see this when I type net
file

C:\Documents and Settings\Administrator>net file

ID Path User name #
Locks

-------------------------------------------------------------------------------
24832 \PIPE\HydraLsPipe ECLIPSE$ 0
24833 \PIPE\HydraLsPipe ECLIPSE$ 0
27056 \PIPE\HydraLsPipe ECLIPSE$ 0
27183 L:\MAST\...winOtter_TestPlan_050527.DOC ALLMAN 0
32798 \PIPE\HydraLsPipe ECLIPSE$ 0
32803 \PIPE\HydraLsPipe ECLIPSE$ 0
33482 \PIPE\HydraLsPipe ECLIPSE$ 0
34696 \PIPE\HydraLsPipe ECLIPSE$ 0
63838 \PIPE\HydraLsPipe ECLIPSE$ 0
64084 \PIPE\HydraLsPipe ECLIPSE$ 0
The command completed successfully.

All these \pipe\ commands may well be from a mis-behaved piece of home-grown
software, could this be causing a problem?

Trink

"trink" wrote:

> now that's an interesting question... it *is* a domain controller, but
> computers both in and out of the domain have been getting this error. All
> users have accounts in the domain, but never get a chance to prove it with a
> challenge login box. I haven't posted a url because that's not the
> methodology that causes the problem. In other words, when folks explicitly
> map a drive to \\eclipse\5600, it usually works, but when they open the
> network neighborhood, go through the entire network, MS windows network, and
> then try to select the domain they get the error. At that point, (I can
> verify that my system has this error on my screen right this second) they get
> "(domain) is not accessible. You might not have permission to use this
> network resource. contact the administrator of this server to find out if you
> have access permissions. 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." My machine is a member of a domain with a two-way trust
> with the domain in question. Is there any way to see *all* the connections
> the server thinks it is supporting at any given moment?
> Trink
>
>
> "Ewan" wrote:
>
> > i'm adding a post as i didn't notice first time you write that when clients
> > connect to your domain. can you elaborate with:
> > sample unc path that causes the error (is this on a domain controller)
> > stupid question: are the clients members of the domain (do the computers
> > have accounts in the domain?)
> >
> > "trink" wrote:
> >
> > > By browser I mean folks trying to get there by opening and explorer, network
> > > neighborhood, and winnowing their way to my domain and server. As soon as
> > > they click the domain, they get a refusal to connect. I have specified that I
> > > have 20 CALs, but there can't be even close to that number of machines
> > > trying to connect. This system is also a terminal server, but that licensing
> > > seems to be going as it should... (even though I have issues with not being
> > > able to reset a license once it's been dished out).
> > > Trink
> > >
> > > "Ewan" wrote:
> > >
> > > >
> > > >
> > > > "trink" wrote:
> > > >
> > > > > Hi,
> > > > > Seems like I should know this (or at least be able to find it definitively,
> > > > > but I can't). How many browser connections will a W2K3 server support at
> > > > > once? Does that number of connections include mapped network drives, or not?
> > > > > I have a server which really gets very little use: there aren't more than
> > > > > 5-10 other XP systems on the net with it, yet people are frequently locked
> > > > > out with the "too many connetions" error. Sometimes you can get it, other
> > > > > times not. This is the first time I've even thought about how many *browser*
> > > > > connections a server could support - did something change between win 2000
> > > > > server and W2K3?
> > > > > help?
> > > > > Trink
> > > > by *browser* do you mean windows explorer uesrs visiting \\servername\share ?
> > > > if you do, what licensing model did you choose at install? (did you specify
> > > > the number of CALs you have, or did you state that each client should have
> > > > it's own CAL ?

ok, to recap the problem as i understand/guess it:
you have a multi-homed (two network adapters) W2k3 domain controller hosting
the eclipse domain. there is only one domain controller for the domain
on one of the network adapters is a LAN. on the other adapter I am not sure
what there is - since you have two domains and a trust between them, but only
have 20 license seats i'm struggling to guess how big an operation you are.
Its also possibly important to understand what type of "gap" is between the
eclipse DC, and the DC for the domain that trusts it. by "gap" i mean are
they on the same lan (logical segment) or different Lan (different logical or
physical segement)

from XP pc with dns name "A.eclipse.something" a user can browse the
domain/net-neighbourhood ok on monday. on tuesday (these days are just
examples) they cannot. The important point here is that a client "sometimes"
can browse ok, without any modification

i googled for the error you are receiving, and i'm wondering if we need to
explore this kb article:
http://support.microsoft.com/default...b;en-us;191611
even though w2k3 is not listed as an affected platform, i think this is an
omission

I suspect you might be suffering from the issues that are documented here;
I suspect "Master browser issues" might describe the problem and "How to
browse with a multihomed PDC" might describe a work around that you can try.
make sure you understand what this workaround is suggesting you do - if
there are mission critical applications that require WINS then you should
arrange an appropriate downtime to try this (remember i'm used to a large
enterprise environment, so that might be heavy handed for your small setup)

let us know if this resolves your issue

"trink" wrote:

> hey, maybe this can help... here's an nbtstat -n printout (I deleted our IP
> addresses, for obvious reasons):
>
> C:\Documents and Settings\Administrator>nbtstat -n
>
> Local Area Connection 2:
> Node IpAddress: [xxx.xxx.xxx.50] Scope Id: []
>
> NetBIOS Local Name Table
>
> Name Type Status
> ---------------------------------------------
> ECLIPSE <00> UNIQUE Registered
> ECLIPSE <20> UNIQUE Registered
> VAULT <00> GROUP Registered
> VAULT <1C> GROUP Registered
> VAULT <1E> GROUP Registered
> VAULT <1D> UNIQUE Registered
> ..__MSBROWSE__.<01> GROUP Registered
> VAULT <1B> UNIQUE Registered
> ECLIPSE <03> UNIQUE Registered
> ALLMAN <03> UNIQUE Registered
>
> Local Area Connection:
> Node IpAddress: [xxx.xxx.xxx.49] Scope Id: []
>
> NetBIOS Local Name Table
>
> Name Type Status
> ---------------------------------------------
> ECLIPSE <00> UNIQUE Registered
> ECLIPSE <20> UNIQUE Registered
> VAULT <00> GROUP Registered
> VAULT <1C> GROUP Registered
> VAULT <1E> GROUP Registered
> VAULT <1B> UNIQUE Registered
> ECLIPSE <03> UNIQUE Registered
> ALLMAN <03> UNIQUE Registered
>
> now, sorry to be uneducated about this, but I also see this when I type net
> file
>
> C:\Documents and Settings\Administrator>net file
>
> ID Path User name #
> Locks
>
> -------------------------------------------------------------------------------
> 24832 \PIPE\HydraLsPipe ECLIPSE$ 0
> 24833 \PIPE\HydraLsPipe ECLIPSE$ 0
> 27056 \PIPE\HydraLsPipe ECLIPSE$ 0
> 27183 L:\MAST\...winOtter_TestPlan_050527.DOC ALLMAN 0
> 32798 \PIPE\HydraLsPipe ECLIPSE$ 0
> 32803 \PIPE\HydraLsPipe ECLIPSE$ 0
> 33482 \PIPE\HydraLsPipe ECLIPSE$ 0
> 34696 \PIPE\HydraLsPipe ECLIPSE$ 0
> 63838 \PIPE\HydraLsPipe ECLIPSE$ 0
> 64084 \PIPE\HydraLsPipe ECLIPSE$ 0
> The command completed successfully.
>
> All these \pipe\ commands may well be from a mis-behaved piece of home-grown
> software, could this be causing a problem?
>
> Trink
>
> "trink" wrote:
>
> > now that's an interesting question... it *is* a domain controller, but
> > computers both in and out of the domain have been getting this error. All
> > users have accounts in the domain, but never get a chance to prove it with a
> > challenge login box. I haven't posted a url because that's not the
> > methodology that causes the problem. In other words, when folks explicitly
> > map a drive to \\eclipse\5600, it usually works, but when they open the
> > network neighborhood, go through the entire network, MS windows network, and
> > then try to select the domain they get the error. At that point, (I can
> > verify that my system has this error on my screen right this second) they get
> > "(domain) is not accessible. You might not have permission to use this
> > network resource. contact the administrator of this server to find out if you
> > have access permissions. 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." My machine is a member of a domain with a two-way trust
> > with the domain in question. Is there any way to see *all* the connections
> > the server thinks it is supporting at any given moment?
> > Trink
> >
> >
> > "Ewan" wrote:
> >
> > > i'm adding a post as i didn't notice first time you write that when clients
> > > connect to your domain. can you elaborate with:
> > > sample unc path that causes the error (is this on a domain controller)
> > > stupid question: are the clients members of the domain (do the computers
> > > have accounts in the domain?)
> > >
> > > "trink" wrote:
> > >
> > > > By browser I mean folks trying to get there by opening and explorer, network
> > > > neighborhood, and winnowing their way to my domain and server. As soon as
> > > > they click the domain, they get a refusal to connect. I have specified that I
> > > > have 20 CALs, but there can't be even close to that number of machines
> > > > trying to connect. This system is also a terminal server, but that licensing
> > > > seems to be going as it should... (even though I have issues with not being
> > > > able to reset a license once it's been dished out).
> > > > Trink
> > > >
> > > > "Ewan" wrote:
> > > >
> > > > >
> > > > >
> > > > > "trink" wrote:
> > > > >
> > > > > > Hi,
> > > > > > Seems like I should know this (or at least be able to find it definitively,
> > > > > > but I can't). How many browser connections will a W2K3 server support at
> > > > > > once? Does that number of connections include mapped network drives, or not?
> > > > > > I have a server which really gets very little use: there aren't more than
> > > > > > 5-10 other XP systems on the net with it, yet people are frequently locked
> > > > > > out with the "too many connetions" error. Sometimes you can get it, other
> > > > > > times not. This is the first time I've even thought about how many *browser*
> > > > > > connections a server could support - did something change between win 2000
> > > > > > server and W2K3?
> > > > > > help?
> > > > > > Trink
> > > > > by *browser* do you mean windows explorer uesrs visiting \\servername\share ?
> > > > > if you do, what licensing model did you choose at install? (did you specify
> > > > > the number of CALs you have, or did you state that each client should have
> > > > > it's own CAL ?

hmm, i should have tested the steps before posting. I think you achieve the
same solution in w2k3 by doing:
Control Panel-->Network Connections
- click "Avanced" from the toolbar, click "Advanced settings" from the menu
remove the ticks for "File and PRinter Sharing...." & "Client for ......"
for all except one adapter

"Ewan" wrote:

> ok, to recap the problem as i understand/guess it:
> you have a multi-homed (two network adapters) W2k3 domain controller hosting
> the eclipse domain. there is only one domain controller for the domain
> on one of the network adapters is a LAN. on the other adapter I am not sure
> what there is - since you have two domains and a trust between them, but only
> have 20 license seats i'm struggling to guess how big an operation you are.
> Its also possibly important to understand what type of "gap" is between the
> eclipse DC, and the DC for the domain that trusts it. by "gap" i mean are
> they on the same lan (logical segment) or different Lan (different logical or
> physical segement)
>
> from XP pc with dns name "A.eclipse.something" a user can browse the
> domain/net-neighbourhood ok on monday. on tuesday (these days are just
> examples) they cannot. The important point here is that a client "sometimes"
> can browse ok, without any modification
>
> i googled for the error you are receiving, and i'm wondering if we need to
> explore this kb article:
> http://support.microsoft.com/default...b;en-us;191611
> even though w2k3 is not listed as an affected platform, i think this is an
> omission
>
> I suspect you might be suffering from the issues that are documented here;
> I suspect "Master browser issues" might describe the problem and "How to
> browse with a multihomed PDC" might describe a work around that you can try.
> make sure you understand what this workaround is suggesting you do - if
> there are mission critical applications that require WINS then you should
> arrange an appropriate downtime to try this (remember i'm used to a large
> enterprise environment, so that might be heavy handed for your small setup)
>
> let us know if this resolves your issue
>
> "trink" wrote:
>
> > hey, maybe this can help... here's an nbtstat -n printout (I deleted our IP
> > addresses, for obvious reasons):
> >
> > C:\Documents and Settings\Administrator>nbtstat -n
> >
> > Local Area Connection 2:
> > Node IpAddress: [xxx.xxx.xxx.50] Scope Id: []
> >
> > NetBIOS Local Name Table
> >
> > Name Type Status
> > ---------------------------------------------
> > ECLIPSE <00> UNIQUE Registered
> > ECLIPSE <20> UNIQUE Registered
> > VAULT <00> GROUP Registered
> > VAULT <1C> GROUP Registered
> > VAULT <1E> GROUP Registered
> > VAULT <1D> UNIQUE Registered
> > ..__MSBROWSE__.<01> GROUP Registered
> > VAULT <1B> UNIQUE Registered
> > ECLIPSE <03> UNIQUE Registered
> > ALLMAN <03> UNIQUE Registered
> >
> > Local Area Connection:
> > Node IpAddress: [xxx.xxx.xxx.49] Scope Id: []
> >
> > NetBIOS Local Name Table
> >
> > Name Type Status
> > ---------------------------------------------
> > ECLIPSE <00> UNIQUE Registered
> > ECLIPSE <20> UNIQUE Registered
> > VAULT <00> GROUP Registered
> > VAULT <1C> GROUP Registered
> > VAULT <1E> GROUP Registered
> > VAULT <1B> UNIQUE Registered
> > ECLIPSE <03> UNIQUE Registered
> > ALLMAN <03> UNIQUE Registered
> >
> > now, sorry to be uneducated about this, but I also see this when I type net
> > file
> >
> > C:\Documents and Settings\Administrator>net file
> >
> > ID Path User name #
> > Locks
> >
> > -------------------------------------------------------------------------------
> > 24832 \PIPE\HydraLsPipe ECLIPSE$ 0
> > 24833 \PIPE\HydraLsPipe ECLIPSE$ 0
> > 27056 \PIPE\HydraLsPipe ECLIPSE$ 0
> > 27183 L:\MAST\...winOtter_TestPlan_050527.DOC ALLMAN 0
> > 32798 \PIPE\HydraLsPipe ECLIPSE$ 0
> > 32803 \PIPE\HydraLsPipe ECLIPSE$ 0
> > 33482 \PIPE\HydraLsPipe ECLIPSE$ 0
> > 34696 \PIPE\HydraLsPipe ECLIPSE$ 0
> > 63838 \PIPE\HydraLsPipe ECLIPSE$ 0
> > 64084 \PIPE\HydraLsPipe ECLIPSE$ 0
> > The command completed successfully.
> >
> > All these \pipe\ commands may well be from a mis-behaved piece of home-grown
> > software, could this be causing a problem?
> >
> > Trink
> >
> > "trink" wrote:
> >
> > > now that's an interesting question... it *is* a domain controller, but
> > > computers both in and out of the domain have been getting this error. All
> > > users have accounts in the domain, but never get a chance to prove it with a
> > > challenge login box. I haven't posted a url because that's not the
> > > methodology that causes the problem. In other words, when folks explicitly
> > > map a drive to \\eclipse\5600, it usually works, but when they open the
> > > network neighborhood, go through the entire network, MS windows network, and
> > > then try to select the domain they get the error. At that point, (I can
> > > verify that my system has this error on my screen right this second) they get
> > > "(domain) is not accessible. You might not have permission to use this
> > > network resource. contact the administrator of this server to find out if you
> > > have access permissions. 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." My machine is a member of a domain with a two-way trust
> > > with the domain in question. Is there any way to see *all* the connections
> > > the server thinks it is supporting at any given moment?
> > > Trink
> > >
> > >
> > > "Ewan" wrote:
> > >
> > > > i'm adding a post as i didn't notice first time you write that when clients
> > > > connect to your domain. can you elaborate with:
> > > > sample unc path that causes the error (is this on a domain controller)
> > > > stupid question: are the clients members of the domain (do the computers
> > > > have accounts in the domain?)
> > > >
> > > > "trink" wrote:
> > > >
> > > > > By browser I mean folks trying to get there by opening and explorer, network
> > > > > neighborhood, and winnowing their way to my domain and server. As soon as
> > > > > they click the domain, they get a refusal to connect. I have specified that I
> > > > > have 20 CALs, but there can't be even close to that number of machines
> > > > > trying to connect. This system is also a terminal server, but that licensing
> > > > > seems to be going as it should... (even though I have issues with not being
> > > > > able to reset a license once it's been dished out).
> > > > > Trink
> > > > >
> > > > > "Ewan" wrote:
> > > > >
> > > > > >
> > > > > >
> > > > > > "trink" wrote:
> > > > > >
> > > > > > > Hi,
> > > > > > > Seems like I should know this (or at least be able to find it definitively,
> > > > > > > but I can't). How many browser connections will a W2K3 server support at
> > > > > > > once? Does that number of connections include mapped network drives, or not?
> > > > > > > I have a server which really gets very little use: there aren't more than
> > > > > > > 5-10 other XP systems on the net with it, yet people are frequently locked
> > > > > > > out with the "too many connetions" error. Sometimes you can get it, other
> > > > > > > times not. This is the first time I've even thought about how many *browser*
> > > > > > > connections a server could support - did something change between win 2000
> > > > > > > server and W2K3?
> > > > > > > help?
> > > > > > > Trink
> > > > > > by *browser* do you mean windows explorer uesrs visiting \\servername\share ?
> > > > > > if you do, what licensing model did you choose at install? (did you specify
> > > > > > the number of CALs you have, or did you state that each client should have
> > > > > > it's own CAL ?