In our office we are using various computers as "file
servers" to handle different types of data that we need
to store. We just upgrades one of the computers to
Windows XP Home ( from win me), and now when other people
try to connect to their network drive (remapped, so I
know the connection is good) they get the following error
message:
\\[Computer name] 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 new connections can be made to this remote
computer at this time because there are already as many
connections as the computer can accept.
Microsoft's Knowledge Base doesn't have anything
specific, that I can find, relating to this problem. Is
there a limit that XP home can support at one time? ME
handled everything fine, it's only been after the upgrade
that we've encountered problems.
Thanks in advance for your help.
It's well known (but offhand I don't know where documented but if this
important I'm sure someone can chip and and give where this documented
in the product's Help file or in the accompanying paperwork) that XP
Home will support 5 connections per box, XP Pro will support 10.
You are hitting these limits. These limits are hard-coded to the OS and
can't be changed.
Was there a compelling reason to "upgrade". Consider instead of using XP
for this server function to move to Windows Server or use Linux. XP
Home (and XP Pro) not intended for this service, esp. as a file server
which requires some level of security and control that I'm sure that ME
can't provide.
Hope this is useful to you. Let us know.
rms
Jonathan S wrote:
> In our office we are using various computers as "file
> servers" to handle different types of data that we need
> to store. We just upgrades one of the computers to
> Windows XP Home ( from win me), and now when other people
> try to connect to their network drive (remapped, so I
> know the connection is good) they get the following error
> message:
> \\[Computer name] 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 new connections can be made to this remote
> computer at this time because there are already as many
> connections as the computer can accept.
>
> Microsoft's Knowledge Base doesn't have anything
> specific, that I can find, relating to this problem. Is
> there a limit that XP home can support at one time? ME
> handled everything fine, it's only been after the upgrade
> that we've encountered problems.
> Thanks in advance for your help.
>
> Jonathan
_________________
Eric Cross, MS-MVP (Windows Networking)
"Rob Schneider" <rmschne@removetheones_b1e1e1b.net.net> wrote in message
news:Oz2hbMAREHA.624@TK2MSFTNGP11.phx.gbl...
> It's well known (but offhand I don't know where documented but if this
> important I'm sure someone can chip and and give where this documented
> in the product's Help file or in the accompanying paperwork) that XP
> Home will support 5 connections per box, XP Pro will support 10.
>
> You are hitting these limits. These limits are hard-coded to the OS and
> can't be changed.
>
> Was there a compelling reason to "upgrade". Consider instead of using XP
> for this server function to move to Windows Server or use Linux. XP
> Home (and XP Pro) not intended for this service, esp. as a file server
> which requires some level of security and control that I'm sure that ME
> can't provide.
>
> Hope this is useful to you. Let us know.
>
> rms
>
>
>
>
> Jonathan S wrote:
> > In our office we are using various computers as "file
> > servers" to handle different types of data that we need
> > to store. We just upgrades one of the computers to
> > Windows XP Home ( from win me), and now when other people
> > try to connect to their network drive (remapped, so I
> > know the connection is good) they get the following error
> > message:
> > \\[Computer name] 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 new connections can be made to this remote
> > computer at this time because there are already as many
> > connections as the computer can accept.
> >
> > Microsoft's Knowledge Base doesn't have anything
> > specific, that I can find, relating to this problem. Is
> > there a limit that XP home can support at one time? ME
> > handled everything fine, it's only been after the upgrade
> > that we've encountered problems.
> > Thanks in advance for your help.
> >
> > Jonathan
In article <Oz2hbMAREHA.624@TK2MSFTNGP11.phx.gbl>, Rob Schneider
<rmschne@removetheones_b1e1e1b.net.net> wrote:>
>Jonathan S wrote:
>> In our office we are using various computers as "file
>> servers" to handle different types of data that we need
>> to store. We just upgrades one of the computers to
>> Windows XP Home ( from win me), and now when other people
>> try to connect to their network drive (remapped, so I
>> know the connection is good) they get the following error
>> message:
>> \\[Computer name] 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 new connections can be made to this remote
>> computer at this time because there are already as many
>> connections as the computer can accept.
>>
>> Microsoft's Knowledge Base doesn't have anything
>> specific, that I can find, relating to this problem. Is
>> there a limit that XP home can support at one time? ME
>> handled everything fine, it's only been after the upgrade
>> that we've encountered problems.
>> Thanks in advance for your help.
>It's well known (but offhand I don't know where documented but if this
>important I'm sure someone can chip and and give where this documented
>in the product's Help file or in the accompanying paperwork) that XP
>Home will support 5 connections per box, XP Pro will support 10.
>
>You are hitting these limits. These limits are hard-coded to the OS and
>can't be changed.
>
>Was there a compelling reason to "upgrade". Consider instead of using XP
>for this server function to move to Windows Server or use Linux. XP
>Home (and XP Pro) not intended for this service, esp. as a file server
>which requires some level of security and control that I'm sure that ME
>can't provide.
>
>Hope this is useful to you. Let us know.
Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.
Yes, I knew this KB could be found ... but I hesitated to give this URL
since it not really connected with the product. How is one supposed to
have known of the existing of this KB article prior to naively buying
the product for the wrong purpose? Surely it's documented with the
product somewhere?
rms
Steve Winograd [MVP] wrote:
> In article <Oz2hbMAREHA.624@TK2MSFTNGP11.phx.gbl>, Rob Schneider
> <rmschne@removetheones_b1e1e1b.net.net> wrote:>
>
>>Jonathan S wrote:
>>
>>>In our office we are using various computers as "file
>>>servers" to handle different types of data that we need
>>>to store. We just upgrades one of the computers to
>>>Windows XP Home ( from win me), and now when other people
>>>try to connect to their network drive (remapped, so I
>>>know the connection is good) they get the following error
>>>message:
>>>\\[Computer name] 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 new connections can be made to this remote
>>>computer at this time because there are already as many
>>>connections as the computer can accept.
>>>
>>>Microsoft's Knowledge Base doesn't have anything
>>>specific, that I can find, relating to this problem. Is
>>>there a limit that XP home can support at one time? ME
>>>handled everything fine, it's only been after the upgrade
>>>that we've encountered problems.
>>>Thanks in advance for your help.
>
>
>>It's well known (but offhand I don't know where documented but if this
>>important I'm sure someone can chip and and give where this documented
>>in the product's Help file or in the accompanying paperwork) that XP
>>Home will support 5 connections per box, XP Pro will support 10.
>>
>>You are hitting these limits. These limits are hard-coded to the OS and
>>can't be changed.
>>
>>Was there a compelling reason to "upgrade". Consider instead of using XP
>>for this server function to move to Windows Server or use Linux. XP
>>Home (and XP Pro) not intended for this service, esp. as a file server
>>which requires some level of security and control that I'm sure that ME
>>can't provide.
>>
>>Hope this is useful to you. Let us know.
>
>
> Here's the documentation, Rob and Jonathan:
>
> Inbound Connections Limit in Windows XP
> http://support.microsoft.com/default...b;en-us;314882
It can also be found in the EULA (right at the top). The following is from
the Windows XP Pro EULA:
1. GRANT OF LICENSE. Microsoft grants you the following rights
provided that you comply with all terms and conditions of
this EULA:
* Installation and use. You may install, use, access,
display and run one copy of the Product on a single
computer, such as a workstation, terminal or other device
("Workstation Computer"). The Product may not be used
by more than two (2) processors at any one time on any
single Workstation Computer. You may permit a maximum
of ten (10) computers or other electronic devices (each
a "Device") to connect to the Workstation Computer to
utilize the services of the Product solely for File and
Print services, Internet Information Services, and remote
access (including connection sharing and telephony
services). The ten connection maximum includes any
indirect connections made through "multiplexing" or other
software or hardware which pools or aggregates
connections. Except as otherwise permitted by the
NetMeeting, Remote Assistance, and Remote Desktop
features described below, you may not use the Product
to permit any Device to use, access, display or run other
executable software residing on the Workstation Computer,
nor may you permit any Device to use, access, display,
or run the Product or Product's user interface, unless
the Device has a separate license for the Product.
"Rob Schneider" <rmschne@removetheones_b1e1e1b.net.net> wrote in message
news:Opd4xWBREHA.3748@TK2MSFTNGP09.phx.gbl...
> Yes, I knew this KB could be found ... but I hesitated to give this URL
> since it not really connected with the product. How is one supposed to
> have known of the existing of this KB article prior to naively buying
> the product for the wrong purpose? Surely it's documented with the
> product somewhere?
>
> rms
>
>
>
>
> Steve Winograd [MVP] wrote:
> > In article <Oz2hbMAREHA.624@TK2MSFTNGP11.phx.gbl>, Rob Schneider
> > <rmschne@removetheones_b1e1e1b.net.net> wrote:>
> >
> >>Jonathan S wrote:
> >>
> >>>In our office we are using various computers as "file
> >>>servers" to handle different types of data that we need
> >>>to store. We just upgrades one of the computers to
> >>>Windows XP Home ( from win me), and now when other people
> >>>try to connect to their network drive (remapped, so I
> >>>know the connection is good) they get the following error
> >>>message:
> >>>\\[Computer name] 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 new connections can be made to this remote
> >>>computer at this time because there are already as many
> >>>connections as the computer can accept.
> >>>
> >>>Microsoft's Knowledge Base doesn't have anything
> >>>specific, that I can find, relating to this problem. Is
> >>>there a limit that XP home can support at one time? ME
> >>>handled everything fine, it's only been after the upgrade
> >>>that we've encountered problems.
> >>>Thanks in advance for your help.
> >
> >
> >>It's well known (but offhand I don't know where documented but if this
> >>important I'm sure someone can chip and and give where this documented
> >>in the product's Help file or in the accompanying paperwork) that XP
> >>Home will support 5 connections per box, XP Pro will support 10.
> >>
> >>You are hitting these limits. These limits are hard-coded to the OS and
> >>can't be changed.
> >>
> >>Was there a compelling reason to "upgrade". Consider instead of using XP
> >>for this server function to move to Windows Server or use Linux. XP
> >>Home (and XP Pro) not intended for this service, esp. as a file server
> >>which requires some level of security and control that I'm sure that ME
> >>can't provide.
> >>
> >>Hope this is useful to you. Let us know.
> >
> >
> > Here's the documentation, Rob and Jonathan:
> >
> > Inbound Connections Limit in Windows XP
> > http://support.microsoft.com/default...b;en-us;314882
Duh ... that should have been the first place I thought of ... and is
also included with the product paper work (which of course nobody reads
but that's not the point, of course).
thanks!
rms
Mark Weinreb wrote:
> It can also be found in the EULA (right at the top). The following is from
> the Windows XP Pro EULA:
>
> 1. GRANT OF LICENSE. Microsoft grants you the following rights
> provided that you comply with all terms and conditions of
> this EULA:
>
> * Installation and use. You may install, use, access,
> display and run one copy of the Product on a single
> computer, such as a workstation, terminal or other device
> ("Workstation Computer"). The Product may not be used
> by more than two (2) processors at any one time on any
> single Workstation Computer. You may permit a maximum
> of ten (10) computers or other electronic devices (each
> a "Device") to connect to the Workstation Computer to
> utilize the services of the Product solely for File and
> Print services, Internet Information Services, and remote
> access (including connection sharing and telephony
> services). The ten connection maximum includes any
> indirect connections made through "multiplexing" or other
> software or hardware which pools or aggregates
> connections. Except as otherwise permitted by the
> NetMeeting, Remote Assistance, and Remote Desktop
> features described below, you may not use the Product
> to permit any Device to use, access, display or run other
> executable software residing on the Workstation Computer,
> nor may you permit any Device to use, access, display,
> or run the Product or Product's user interface, unless
> the Device has a separate license for the Product.
>
>
> "Rob Schneider" <rmschne@removetheones_b1e1e1b.net.net> wrote in message
> news:Opd4xWBREHA.3748@TK2MSFTNGP09.phx.gbl...
>
>>Yes, I knew this KB could be found ... but I hesitated to give this URL
>>since it not really connected with the product. How is one supposed to
>>have known of the existing of this KB article prior to naively buying
>>the product for the wrong purpose? Surely it's documented with the
>>product somewhere?
>>
>>rms
>>
>>
>>
>>
>>Steve Winograd [MVP] wrote:
>>
>>>In article <Oz2hbMAREHA.624@TK2MSFTNGP11.phx.gbl>, Rob Schneider
>>><rmschne@removetheones_b1e1e1b.net.net> wrote:>
>>>
>>>>Jonathan S wrote:
>>>>
>>>>
>>>>>In our office we are using various computers as "file
>>>>>servers" to handle different types of data that we need
>>>>>to store. We just upgrades one of the computers to
>>>>>Windows XP Home ( from win me), and now when other people
>>>>>try to connect to their network drive (remapped, so I
>>>>>know the connection is good) they get the following error
>>>>>message:
>>>>>\\[Computer name] 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 new connections can be made to this remote
>>>>>computer at this time because there are already as many
>>>>>connections as the computer can accept.
>>>>>
>>>>>Microsoft's Knowledge Base doesn't have anything
>>>>>specific, that I can find, relating to this problem. Is
>>>>>there a limit that XP home can support at one time? ME
>>>>>handled everything fine, it's only been after the upgrade
>>>>>that we've encountered problems.
>>>>>Thanks in advance for your help.
>>>
>>>
>>>>It's well known (but offhand I don't know where documented but if this
>>>>important I'm sure someone can chip and and give where this documented
>>>>in the product's Help file or in the accompanying paperwork) that XP
>>>>Home will support 5 connections per box, XP Pro will support 10.
>>>>
>>>>You are hitting these limits. These limits are hard-coded to the OS and
>>>>can't be changed.
>>>>
>>>>Was there a compelling reason to "upgrade". Consider instead of using XP
>>>>for this server function to move to Windows Server or use Linux. XP
>>>>Home (and XP Pro) not intended for this service, esp. as a file server
>>>>which requires some level of security and control that I'm sure that ME
>>>>can't provide.
>>>>
>>>>Hope this is useful to you. Let us know.
>>>
>>>
>>>Here's the documentation, Rob and Jonathan:
>>>
>>>Inbound Connections Limit in Windows XP
>>>http://support.microsoft.com/default...b;en-us;314882
>
>
>
Thanks everyone for your help in this issue. Maybe now I can get
something pounded through managements head that we need a dedicated file
server.
Wish me luck, I may need it. ;-)
User limits in Windows? 
Linear Mode
