22 August 2009

LANLet’s say you have a network of more than ten Windows computers connected in a local workgroup without a domain controller. One of the computers has a printer connected to it, and more than ten machines in the workgroup need to print at the same time.

Well, you might say, “Dude, get a server!” or “Dude, get a print server!”

True, that would solve the problem… But sometimes, things like money and technical knowledge are limiting factors in such cases.

The good news: It’s actually really easy to increase the limit and get everybody printing/sharing files in a very short time!

Alrighty, first a few more words about Windows Networking. If a computer is running Windows XP Home, the max number of connections that can be made to/from that computer on the LAN is 5. If the machine is running XP Pro, Vista, etc. then the max is 10.

Also, you have to understand that the limit refers to connections, not number of computers. Technically, you can have a LAN with 500 Windows machines, and as long as no more than 10 computers are trying to connect to any other computer, everything will work okay. But you will still probably have a few headaches like when you browse Network Neighborhood, not all the computers will show up. That’s pretty annoying.

So now, here’s how you fix it:

First, type Win-R to open the “Run” dialog box, and type gpedit.msc.

At this point, one of two things will happen:

  1. You have a fancier version of Windows, so a nice management console will pop up.
  2. You have a less fancy version of Windows, so it will give you an error message.

If you see the management window, then navigate thisaway:

Computer Config -> Windows Settings -> Security Settings -> Local Policies -> Security Option

And set Interactive Logon to 50 (the maximum) or 0 (i.e. disable caching completely)

If you get the error message instead of the management window, then do the following:

  • Type Win-R
  • Type regedt32 and hit Enter
  • Search for the following entry:
    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\CachedLogonsCount
  • Change CachedLogonsCount to 50 (the max) or 0 (disabled)
  • Close the Registry Editor

Repeat on each machine on the network just for good measure, et voila! You’re done.

I’ve used this trick before on multi-version Windows networks, and it works like a charm. It’s also a heckuva lot easier than setting up a server, and cheaper than buying a standalone print server of some kind.

Finally, note that for Windows versions without gpedit.msc, you can download an Excel file with the corresponding registry entries to edit in Vista (entries are usually the same in other versions of Windows).

Have fun!

Expanding your network? I recommend D-Link gigabit switches, and TP-LINK routers!

How to Increase the 10 Connection Limit on a Windows LAN
Tagged on:         

34 thoughts on “How to Increase the 10 Connection Limit on a Windows LAN

  • 22 November 2009 at 12:31
    Permalink

    Brilliant – have just the symptoms as you laid out. Not sure if this is in breach of Microsoft Licence.

    Reply
  • 27 January 2010 at 11:52
    Permalink

    tried to do it on VISTA 32. Not working 🙁
    The registry key is set to 20, but the pc give me a limit of 10 pc connected…
    any ideas??

    Reply
  • 30 March 2010 at 15:41
    Permalink

    Just because you can doesn’t mean you should. In other words, don’t do this.

    Workgroups are insecure by nature, and if you have to enforce any kind of security in a workgroup then you are in a world of high-maintenance hurt. You have to keep passowrds and user groups and all that in sync, or else you have to have people sharing passwords.

    Also, at least at one point (and I think it is still the case), there isn’t just a technical limit imposed. Without a domain controller you are violating the license agreement of WinXP Pro, Vista and 7 if you make these OSes do more than 10 connections at a time.

    Of course, if you don’t care about security then there are chances you don’t care about breaking the law either and you are using cracked software 😉

    If you are too broke to buy a computer with Windows server on it then use some old junk PC with Linux on it running Samba and you can save a few hundred bucks. Don’t give me crap about Linux being hard either–I’ve set up Windows AND samba domains and samba ain’t any harder these days with OSes like Ubuntu and Mandriva (I’ve done it on both of those OSes without opening a command promt at all). Since it is pretty common practice to do this and there isn’t any language in MSFT EULA’s that says you have to use THEIR server oses to do domains, then I think this option is far more solid. Might not have full group policy capabilities w/ samba, but at least you can manage security better.

    Reply
  • 31 March 2010 at 09:28
    Permalink

    Vey useful dude……..
    thanks very much…how long i am facing this problem.
    once again thanks.

    Reply
  • 12 April 2010 at 12:06
    Permalink

    hey all
    really useful tut but its not working with me
    i just went to know if its necessary to config all the pc’s on the lan or just the admin pc ?
    another thing :p
    if som1 knows how or a program to distribute a file over all the lan computers
    thx

    Reply
    • 12 April 2010 at 19:28
      Permalink

      I made the change to all the puters on the LAN, and that fixed the problem of not having all the computers show up in Network Neighborhood.

      Dunno about your second question though!

      Reply
  • 2 July 2010 at 04:30
    Permalink

    what about Win 2000 server….

    Reply
    • 2 July 2010 at 15:14
      Permalink

      Not sure about Win2k server. Don’t know much about it, although I think the server versions are far more restrictive since they want you to pay lots more money for a server that can handle more connections. I could be wrong, though!

      Reply
  • 20 December 2010 at 20:24
    Permalink

    Hey, thanks a bunch. I couldn’t find a solution anywhere online for this issue after many pages of google results. This was a quick, easy fix. I only wanted to allow all the users on our network to access a 2TB harddrive on our ‘server’ computer and was able to do so by only editing the ‘server’s settings.

    Anyway, thanks for saving me $1000!

    Reply
  • 15 March 2011 at 09:44
    Permalink

    HI, why I can’t see the comments ?

    Btw, I tried this method in my XP server, then I found that in “Computer management”, I can adjust the max users to 20 of the shared resources, however, after 10 computers connect to the server, the 11 will still cannot access the shared folder. It seems no hope. I also install the “Event4226 Patch”, any idea ?

    I haven’t set all the workstations to this method, since some computers haven’t gpedit.msc, I can’t download from yr site. please help, thanks !!

    Reply
    • 15 March 2011 at 18:08
      Permalink

      Hmm. I can’t seem to find that XLS file any more. You could just try searching the registry for “CachedLogonsCount”. I’m not sure if that’s correct, because I don’t have a Vista machine anymore to try it out.

      Reply
  • 24 November 2011 at 02:58
    Permalink

    Very useful tip…I used this when the each client can’t print to the shared printer in one of the workstation here at the office.

    Reply
  • 15 August 2012 at 19:08
    Permalink

    cached logons has nothing to do with how many users can connect to a shared network resource. It only controls how many domain user profiles are stored locally, so that after you log into the domain once, if you cant connect to the domain later you are still able to login. The limit is 50 user profiles. There is a 20 user limit for connections to network resources and is controlled in the share settings for that folder. There might be a way to work around it but this isnt it.

    Reply
  • 6 September 2012 at 20:41
    Permalink

    @MSH
    Actually it is not “breaking the law” to do this. Microsoft is a corporation not a government entity. So, they do not have the power to create law when they write their user agreements. Doing this simply violates the license agreement, which is not law.

    The real issue, if it ever gets to court, is whether or not you intend to, or actually, deprived Microsoft of their just due. (Payment for a license.)

    Reply
  • 10 June 2013 at 02:30
    Permalink

    I’m about to set this up on our hospital’s network. I have a Windows server (2003 OS). Way too many headaches and overhead to keep it continuously running. Latest MS firewall auto updated and blocked every PC from accessing the practice management software (PMS) we run on the server. We use a common user account login on all 10 PCs. It’s the PMS that we log into with unique IDs. One of the notes above indicated that with all the user logins and passwords, this was a bad idea. I’m just commenting that there are possibly other scenarios where a small business has a single user login to get onto the Domain, then uses unique ID’s for their management software.

    Reply
  • 4 August 2013 at 08:35
    Permalink

    I did it in windows 7 32bit it was not working..

    Reply
  • 29 August 2013 at 17:03
    Permalink

    You saved my day ! Thanks

    Reply
  • 11 April 2014 at 15:22
    Permalink

    Hi, I am wondering if this solution still works with Windows 7 pcs and Windows 8 pcs?
    Have you tried this with those OS’es.
    In addition, generally, is this still a solution that works?
    It is a big headache when I max out at t10 simultaneous connections and the 11th person cannot get in.
    I now have a mix of xp, win 7, and win 8 in my network

    Reply
  • 11 April 2014 at 16:31
    Permalink

    Thank you very much.
    I noticed just now, when I went to one of my Windows 7 machines, and one of my Windows 8 machines, that the default registry setting, before I change it, is still 10.

    I had expected it to say 20, because I keep reading everywhere that the max sessions in windows 7 was increased from 10 to 20. Does that make sense to you that the registry entry still says 10 and not 20? Or does that mean I am looking at the wrong registry entry?

    This is enormously helpful and useful … I have looking to see how to overcome the limit for years and have never found an answer until I found your site.

    Thank you again.

    Reply
    • 11 April 2014 at 20:31
      Permalink

      I’ve never understood that either, because it always says 10. Somebody told me the setting I mention is not doing what I think it’s doing, which is entirely possible. But, nevertheless it works, so it must be doing something good.

      Reply
  • 29 August 2014 at 10:36
    Permalink

    Does not work. open a command prompt and type: net config server. you will see the actual number of users that are equal to 10. sorry.

    Reply
  • 12 September 2014 at 16:32
    Permalink

    @MSH
    Not all printers have linux drivers. Like that 20 year old plotter that can only run on xp.

    Reply
  • 8 October 2014 at 05:39
    Permalink

    how may possible 20 more system access shared folder in windows 7 workgroup topology is possible ore not.

    Reply
    • 8 October 2014 at 09:40
      Permalink

      Should be possible with the hack here (works for me!). If that doesn’t work, you would need Windows Server on 1 machine, I think.

      Reply
  • 6 January 2015 at 19:20
    Permalink

    Official solution from Microsoft for the same problem when you upgrade from win 3.5 Workstation to win 3.5 server; I think it may work on WinXPHome & Pro:

    1.Start the Registry Editor (REGEDT32.EXE)
    2.Find the following key:

    \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services \LanmanServer\Parameters

    3.From the Edit menu, choose Add Value. Type “Users” (without quotation marks) in the Value Name field. Select REG_DWORD for the Data Type and choose OK. Enter the value of 0xFFFFFFFF in the String field and choose OK.
    4.Exit the Registry Editor.
    5.Either shut down and restart Windows NT, or from a command prompt type:
    NET STOP SERVER
    And then type:
    NET START SERVER

    That’s all!

    Check it out at: http://support.microsoft.com/kb/122925/EN-US/

    Reply
  • 12 January 2015 at 16:02
    Permalink

    @MSH

    MSH,

    Way to rain on his parade goofball. LOL breaking lic agreements, calling him a pirate. You sound like a turd.

    Reply
  • 17 August 2015 at 23:10
    Permalink

    Thanks for the info this really helps with a situation im working on at the moment.

    Reply
  • 19 December 2015 at 09:08
    Permalink

    i have done .following steps .but facing same issue here.what i do .tell me urhent for me and my company.

    Reply
  • 11 July 2016 at 12:35
    Permalink

    VERY HELPFUL Thank you! Now how to fix the same issue for the mobile phones!!? 🙂

    Reply
  • 5 October 2016 at 08:08
    Permalink

    What is the limit in windows 10 home?

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *