Inbound connection limit issue with windows 2000 server

Hi,

We have recently taken on a new employee and consequently a new laptop. the server is a file share server where everybody access a shared drive using My Network Places, mainly on Windows XP Pro but also one home machine.

We are now getting messages whch end in:

"no more connection can be made to this remote computer at this time because there are already as many connections as the computer can accept "

I understand that in Windows Professional products there is a 10 user connection limit which cannot be changed. Many sites found by Google after searching " Inbound connection limit" say that Windows Server products have no such limit.

We have Windows 2000 Server, SP 4 version 5.00.2195. Suerly a server edition of the software should take in to account that mabey an office of 100 computers are trying to access a drive on the Windows server PC.

Can anybody advise me about this?


I have seen people mention:
net config server /autodisconnect:<time_before_autodisconnect>
where "<time_before_autodisconnect>" is a number in minutes.
If i set this to 1 or 2 minutes say, what - if any problems can this cause?


Many thanks for having a look at this

Stuart.

 

What licensing mode is your server using?

"Per Device" or "Per Server. Number of concurrent connections ".

 

scorp, many thanks for replying

I dont know where to find what your asking for? Can you possibly clarify?

Thanks,
Stuart.

 

Take a look here.

Start --> Settings --> Control Panel --> Licensing

 

Hi,

I have had a look at that and we are in per server mode. it was set to 5 licences with 7 in use.

I have set it to add 15 licences to take us to 20 but nothing happens.

Do i need to buy additional licences from microsoft to allow more people to access a shared drive?

I have also set the disconnect time to 5 mins rather than 15 mins, that may have some effect but probably not as all PC's are in constant use.

Stuart.

 

If each user is connecting with their own legit copy of Windows then you can change to Per Device mode and this problem should go away.

 

So if i change from "per Server" mode to "per seat" mode things should be OK?

All systems are either windows XP home or XP Pro. All have genuine activated licenses and we have never had any problems activating any products etc.

I was concerned about changeing to Per Seat given the warnings about not being able to change back etc.

If i were to change, what effect would this have on the system?
What reasons could there be to want to change back?

Thanks for getting back,
Stuart.

 

You would want (need) to use per connection licensing if you were using it as a Terminal Serivices box, or your had a lot of non-windows clients connecting for servicse.

 

Hi,

I was looking at some of the computers and running the windows validation tool from the MS website. Some of our employees have there own personal laptop and the windows install is not 100% what MS thinks is "Genuine "

Would running "Per Seat" give these users restriction to accessing the shared drives on the win 2k server machine?

How can i go about possibly bying more per server licences? Do i contact MS? ive not seen any indication on how to do this.

Many thanks,
Stuart.