Windows 8 cannot log in into a locked computer





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







5
















The number of connections to this computer is limited and all connections are in use right now. Try connecting later or contact your system administrator.




I get this error message from time to time, when I try to unlock my Windows 8 Pro Tablet.
(I have also a Laptop running Windows 8, but I have never faced this error there.)



I remember it from times, with Windows 7 and XP or 2003 Server, when somebody (or too many people) were accessing the computer via Remote Desktop simultaneously. That's why I disabled Remote Desktop and everything I could find about it on my tablet, after I've seen the Message the first time.



Usually I get it about once or twice a month. The only "solution" I've found so far, is to turn of the tablet by holding the power button (hard reset).



Any ideas which application or bug could be causing it?



And AFAIR, in Windows 7, I could say that I want to kick out the other people so I can log in - do you know, how I can do it in Windows 8?



My user is the only user on that system (I have administrator permissions)



Thank you for your help, cheers.



Peter










share|improve this question

























  • Any 3th party software you have installed that might trigger this behavior?

    – ZippyV
    Jul 7 '13 at 11:46











  • nothing I could think of - except development tools and some services like SQL Server, ... there are DropBox and similar sync software running in the background. The only one I could think of theoretically would be TeamViewer, but that was supposedly turned of the last time, it happened. And nobody ever connected to my tablet using TeamViewer.

    – peter
    Jul 7 '13 at 11:53


















5
















The number of connections to this computer is limited and all connections are in use right now. Try connecting later or contact your system administrator.




I get this error message from time to time, when I try to unlock my Windows 8 Pro Tablet.
(I have also a Laptop running Windows 8, but I have never faced this error there.)



I remember it from times, with Windows 7 and XP or 2003 Server, when somebody (or too many people) were accessing the computer via Remote Desktop simultaneously. That's why I disabled Remote Desktop and everything I could find about it on my tablet, after I've seen the Message the first time.



Usually I get it about once or twice a month. The only "solution" I've found so far, is to turn of the tablet by holding the power button (hard reset).



Any ideas which application or bug could be causing it?



And AFAIR, in Windows 7, I could say that I want to kick out the other people so I can log in - do you know, how I can do it in Windows 8?



My user is the only user on that system (I have administrator permissions)



Thank you for your help, cheers.



Peter










share|improve this question

























  • Any 3th party software you have installed that might trigger this behavior?

    – ZippyV
    Jul 7 '13 at 11:46











  • nothing I could think of - except development tools and some services like SQL Server, ... there are DropBox and similar sync software running in the background. The only one I could think of theoretically would be TeamViewer, but that was supposedly turned of the last time, it happened. And nobody ever connected to my tablet using TeamViewer.

    – peter
    Jul 7 '13 at 11:53














5












5








5


1







The number of connections to this computer is limited and all connections are in use right now. Try connecting later or contact your system administrator.




I get this error message from time to time, when I try to unlock my Windows 8 Pro Tablet.
(I have also a Laptop running Windows 8, but I have never faced this error there.)



I remember it from times, with Windows 7 and XP or 2003 Server, when somebody (or too many people) were accessing the computer via Remote Desktop simultaneously. That's why I disabled Remote Desktop and everything I could find about it on my tablet, after I've seen the Message the first time.



Usually I get it about once or twice a month. The only "solution" I've found so far, is to turn of the tablet by holding the power button (hard reset).



Any ideas which application or bug could be causing it?



And AFAIR, in Windows 7, I could say that I want to kick out the other people so I can log in - do you know, how I can do it in Windows 8?



My user is the only user on that system (I have administrator permissions)



Thank you for your help, cheers.



Peter










share|improve this question

















The number of connections to this computer is limited and all connections are in use right now. Try connecting later or contact your system administrator.




I get this error message from time to time, when I try to unlock my Windows 8 Pro Tablet.
(I have also a Laptop running Windows 8, but I have never faced this error there.)



I remember it from times, with Windows 7 and XP or 2003 Server, when somebody (or too many people) were accessing the computer via Remote Desktop simultaneously. That's why I disabled Remote Desktop and everything I could find about it on my tablet, after I've seen the Message the first time.



Usually I get it about once or twice a month. The only "solution" I've found so far, is to turn of the tablet by holding the power button (hard reset).



Any ideas which application or bug could be causing it?



And AFAIR, in Windows 7, I could say that I want to kick out the other people so I can log in - do you know, how I can do it in Windows 8?



My user is the only user on that system (I have administrator permissions)



Thank you for your help, cheers.



Peter







windows-8 login






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jul 7 '13 at 11:19









matan129

1,85421323




1,85421323










asked Jul 7 '13 at 8:55









peterpeter

13329




13329













  • Any 3th party software you have installed that might trigger this behavior?

    – ZippyV
    Jul 7 '13 at 11:46











  • nothing I could think of - except development tools and some services like SQL Server, ... there are DropBox and similar sync software running in the background. The only one I could think of theoretically would be TeamViewer, but that was supposedly turned of the last time, it happened. And nobody ever connected to my tablet using TeamViewer.

    – peter
    Jul 7 '13 at 11:53



















  • Any 3th party software you have installed that might trigger this behavior?

    – ZippyV
    Jul 7 '13 at 11:46











  • nothing I could think of - except development tools and some services like SQL Server, ... there are DropBox and similar sync software running in the background. The only one I could think of theoretically would be TeamViewer, but that was supposedly turned of the last time, it happened. And nobody ever connected to my tablet using TeamViewer.

    – peter
    Jul 7 '13 at 11:53

















Any 3th party software you have installed that might trigger this behavior?

– ZippyV
Jul 7 '13 at 11:46





Any 3th party software you have installed that might trigger this behavior?

– ZippyV
Jul 7 '13 at 11:46













nothing I could think of - except development tools and some services like SQL Server, ... there are DropBox and similar sync software running in the background. The only one I could think of theoretically would be TeamViewer, but that was supposedly turned of the last time, it happened. And nobody ever connected to my tablet using TeamViewer.

– peter
Jul 7 '13 at 11:53





nothing I could think of - except development tools and some services like SQL Server, ... there are DropBox and similar sync software running in the background. The only one I could think of theoretically would be TeamViewer, but that was supposedly turned of the last time, it happened. And nobody ever connected to my tablet using TeamViewer.

– peter
Jul 7 '13 at 11:53










2 Answers
2






active

oldest

votes


















0














Sounds like a network services problem.



Did you check the event logs? Do they give you any clues?



Do you have a static IP address? Or do you get one via DHCP (preferred)? A static IP address could be causing the problem. Make sure you use DHCP.



Could also be a network adaptor problem. Get a driver update if available.






share|improve this answer































    0














    The official solution (from the Microsoft Answers site here: http://answers.microsoft.com/en-us/windows/forum/windows8_1-system/the-number-of-connections-to-this-computer-is/2e044b7e-b016-4933-a1ea-6add9fca94a3) is this:




    1. Unplug your network cable, or turn off your Wi-Fi.

    2. Reboot your computer

    3. Login to your computer. It will let you do it without the network plugged in.

    4. Once you are logged in, plug in your network cable or turn your Wi-Fi back on.


    Personally, I swapped the 3rd and 4th steps and it worked OK. This appears to be a bit of a known issue with Windows 8.1 at least since around February of last year. I've only seen it myself once.






    share|improve this answer



















    • 1





      Just rebooting worked as well. It's just a pain if I had unsaved files,... It's a shame that such a bug is just classified as known issue and a turning off / on is still considered being a valid workaround

      – peter
      Apr 16 '15 at 19:09












    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f616517%2fwindows-8-cannot-log-in-into-a-locked-computer%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    Sounds like a network services problem.



    Did you check the event logs? Do they give you any clues?



    Do you have a static IP address? Or do you get one via DHCP (preferred)? A static IP address could be causing the problem. Make sure you use DHCP.



    Could also be a network adaptor problem. Get a driver update if available.






    share|improve this answer




























      0














      Sounds like a network services problem.



      Did you check the event logs? Do they give you any clues?



      Do you have a static IP address? Or do you get one via DHCP (preferred)? A static IP address could be causing the problem. Make sure you use DHCP.



      Could also be a network adaptor problem. Get a driver update if available.






      share|improve this answer


























        0












        0








        0







        Sounds like a network services problem.



        Did you check the event logs? Do they give you any clues?



        Do you have a static IP address? Or do you get one via DHCP (preferred)? A static IP address could be causing the problem. Make sure you use DHCP.



        Could also be a network adaptor problem. Get a driver update if available.






        share|improve this answer













        Sounds like a network services problem.



        Did you check the event logs? Do they give you any clues?



        Do you have a static IP address? Or do you get one via DHCP (preferred)? A static IP address could be causing the problem. Make sure you use DHCP.



        Could also be a network adaptor problem. Get a driver update if available.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 19 '15 at 15:37









        Brian TowersBrian Towers

        1012




        1012

























            0














            The official solution (from the Microsoft Answers site here: http://answers.microsoft.com/en-us/windows/forum/windows8_1-system/the-number-of-connections-to-this-computer-is/2e044b7e-b016-4933-a1ea-6add9fca94a3) is this:




            1. Unplug your network cable, or turn off your Wi-Fi.

            2. Reboot your computer

            3. Login to your computer. It will let you do it without the network plugged in.

            4. Once you are logged in, plug in your network cable or turn your Wi-Fi back on.


            Personally, I swapped the 3rd and 4th steps and it worked OK. This appears to be a bit of a known issue with Windows 8.1 at least since around February of last year. I've only seen it myself once.






            share|improve this answer



















            • 1





              Just rebooting worked as well. It's just a pain if I had unsaved files,... It's a shame that such a bug is just classified as known issue and a turning off / on is still considered being a valid workaround

              – peter
              Apr 16 '15 at 19:09
















            0














            The official solution (from the Microsoft Answers site here: http://answers.microsoft.com/en-us/windows/forum/windows8_1-system/the-number-of-connections-to-this-computer-is/2e044b7e-b016-4933-a1ea-6add9fca94a3) is this:




            1. Unplug your network cable, or turn off your Wi-Fi.

            2. Reboot your computer

            3. Login to your computer. It will let you do it without the network plugged in.

            4. Once you are logged in, plug in your network cable or turn your Wi-Fi back on.


            Personally, I swapped the 3rd and 4th steps and it worked OK. This appears to be a bit of a known issue with Windows 8.1 at least since around February of last year. I've only seen it myself once.






            share|improve this answer



















            • 1





              Just rebooting worked as well. It's just a pain if I had unsaved files,... It's a shame that such a bug is just classified as known issue and a turning off / on is still considered being a valid workaround

              – peter
              Apr 16 '15 at 19:09














            0












            0








            0







            The official solution (from the Microsoft Answers site here: http://answers.microsoft.com/en-us/windows/forum/windows8_1-system/the-number-of-connections-to-this-computer-is/2e044b7e-b016-4933-a1ea-6add9fca94a3) is this:




            1. Unplug your network cable, or turn off your Wi-Fi.

            2. Reboot your computer

            3. Login to your computer. It will let you do it without the network plugged in.

            4. Once you are logged in, plug in your network cable or turn your Wi-Fi back on.


            Personally, I swapped the 3rd and 4th steps and it worked OK. This appears to be a bit of a known issue with Windows 8.1 at least since around February of last year. I've only seen it myself once.






            share|improve this answer













            The official solution (from the Microsoft Answers site here: http://answers.microsoft.com/en-us/windows/forum/windows8_1-system/the-number-of-connections-to-this-computer-is/2e044b7e-b016-4933-a1ea-6add9fca94a3) is this:




            1. Unplug your network cable, or turn off your Wi-Fi.

            2. Reboot your computer

            3. Login to your computer. It will let you do it without the network plugged in.

            4. Once you are logged in, plug in your network cable or turn your Wi-Fi back on.


            Personally, I swapped the 3rd and 4th steps and it worked OK. This appears to be a bit of a known issue with Windows 8.1 at least since around February of last year. I've only seen it myself once.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Apr 16 '15 at 19:02









            music2myearmusic2myear

            32.4k860101




            32.4k860101








            • 1





              Just rebooting worked as well. It's just a pain if I had unsaved files,... It's a shame that such a bug is just classified as known issue and a turning off / on is still considered being a valid workaround

              – peter
              Apr 16 '15 at 19:09














            • 1





              Just rebooting worked as well. It's just a pain if I had unsaved files,... It's a shame that such a bug is just classified as known issue and a turning off / on is still considered being a valid workaround

              – peter
              Apr 16 '15 at 19:09








            1




            1





            Just rebooting worked as well. It's just a pain if I had unsaved files,... It's a shame that such a bug is just classified as known issue and a turning off / on is still considered being a valid workaround

            – peter
            Apr 16 '15 at 19:09





            Just rebooting worked as well. It's just a pain if I had unsaved files,... It's a shame that such a bug is just classified as known issue and a turning off / on is still considered being a valid workaround

            – peter
            Apr 16 '15 at 19:09


















            draft saved

            draft discarded




















































            Thanks for contributing an answer to Super User!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f616517%2fwindows-8-cannot-log-in-into-a-locked-computer%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown