Remote Desktop closes with Fatal Error (Error Code: 5) Announcing the arrival of Valued...

Any stored/leased 737s that could substitute for grounded MAXs?

Is a copyright notice with a non-existent name be invalid?

How to resize main filesystem

Fit odd number of triplets in a measure?

What is "Lambda" in Heston's original paper on stochastic volatility models?

Did pre-Columbian Americans know the spherical shape of the Earth?

What did Turing mean when saying that "machines cannot give rise to surprises" is due to a fallacy?

What was the last profitable war?

How to make triangles with rounded sides and corners? (squircle with 3 sides)

Can gravitational waves pass through a black hole?

Where and when has Thucydides been studied?

Adapting the Chinese Remainder Theorem (CRT) for integers to polynomials

Why do C and C++ allow the expression (int) + 4*5;

Besides transaction validation, are there any other uses of the Script language in Bitcoin

Noise in Eigenvalues plot

Why are current probes so expensive?

Does a random sequence of vectors span a Hilbert space?

Should man-made satellites feature an intelligent inverted "cow catcher"?

.bashrc alias for a command with fixed second parameter

How to make an animal which can only breed for a certain number of generations?

What is a more techy Technical Writer job title that isn't cutesy or confusing?

Is it OK to use the testing sample to compare algorithms?

Determine whether an integer is a palindrome

Twin's vs. Twins'



Remote Desktop closes with Fatal Error (Error Code: 5)



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)How to connect to XP Home PC from XP Pro using Remote DesktopIs remote desktop MSTSC secure?Remote desktop session closes immediately after logging inRemote desktop crashes when connecting with printing local resource enabled (XP to Server 2008)Mac VNC and Windows Remote Desktop License IssueWindows Remote Desktop: “configuring remote session” closes without errorRemote Desktop with custom parameterRemote Desktop shadowing returns 'Access is Denied'connect to remote desktop with same sessionRemote desktop session ended when connect through VPN





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







2















We have one PC (Windows XP SP3) that we can not log onto using a Remote Desktop session. Logging on to the PC directly (sitting in front of it using the connected keyboard and monitor) work fine.



From a second PC (tried a number of different ones but all Windows XP SP3) I run 'mstsc' and type in PC name to connect to. This shows the login box which we can enter the correct login details and click OK. Within a few second we get an error:




Title: Fatal Error (Error Code:5)



Error: Your Remote Desktop session is
about to end. This computer might be
low on virtual memory. Close your
other programs, and then try
connecting to the remote computer
again. If the problem continues,
contact your network administrator or
technical support.




None of the computers we are using are low on memory (2Gb+) and we let windows manage the virtual memory side of things. We do not see this with any other PC and do use Remote Desktop in meeting rooms to connect to user PCs with no problems.










share|improve this question














bumped to the homepage by Community 3 hours ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.






















    2















    We have one PC (Windows XP SP3) that we can not log onto using a Remote Desktop session. Logging on to the PC directly (sitting in front of it using the connected keyboard and monitor) work fine.



    From a second PC (tried a number of different ones but all Windows XP SP3) I run 'mstsc' and type in PC name to connect to. This shows the login box which we can enter the correct login details and click OK. Within a few second we get an error:




    Title: Fatal Error (Error Code:5)



    Error: Your Remote Desktop session is
    about to end. This computer might be
    low on virtual memory. Close your
    other programs, and then try
    connecting to the remote computer
    again. If the problem continues,
    contact your network administrator or
    technical support.




    None of the computers we are using are low on memory (2Gb+) and we let windows manage the virtual memory side of things. We do not see this with any other PC and do use Remote Desktop in meeting rooms to connect to user PCs with no problems.










    share|improve this question














    bumped to the homepage by Community 3 hours ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.


















      2












      2








      2








      We have one PC (Windows XP SP3) that we can not log onto using a Remote Desktop session. Logging on to the PC directly (sitting in front of it using the connected keyboard and monitor) work fine.



      From a second PC (tried a number of different ones but all Windows XP SP3) I run 'mstsc' and type in PC name to connect to. This shows the login box which we can enter the correct login details and click OK. Within a few second we get an error:




      Title: Fatal Error (Error Code:5)



      Error: Your Remote Desktop session is
      about to end. This computer might be
      low on virtual memory. Close your
      other programs, and then try
      connecting to the remote computer
      again. If the problem continues,
      contact your network administrator or
      technical support.




      None of the computers we are using are low on memory (2Gb+) and we let windows manage the virtual memory side of things. We do not see this with any other PC and do use Remote Desktop in meeting rooms to connect to user PCs with no problems.










      share|improve this question














      We have one PC (Windows XP SP3) that we can not log onto using a Remote Desktop session. Logging on to the PC directly (sitting in front of it using the connected keyboard and monitor) work fine.



      From a second PC (tried a number of different ones but all Windows XP SP3) I run 'mstsc' and type in PC name to connect to. This shows the login box which we can enter the correct login details and click OK. Within a few second we get an error:




      Title: Fatal Error (Error Code:5)



      Error: Your Remote Desktop session is
      about to end. This computer might be
      low on virtual memory. Close your
      other programs, and then try
      connecting to the remote computer
      again. If the problem continues,
      contact your network administrator or
      technical support.




      None of the computers we are using are low on memory (2Gb+) and we let windows manage the virtual memory side of things. We do not see this with any other PC and do use Remote Desktop in meeting rooms to connect to user PCs with no problems.







      windows-xp remote-desktop






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Aug 16 '10 at 15:57









      SwindersSwinders

      2351715




      2351715





      bumped to the homepage by Community 3 hours ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 3 hours ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          1 Answer
          1






          active

          oldest

          votes


















          0















          None of the computers we are using are low on memory (2Gb+) and we let windows manage the virtual memory side of things.




          I think you're talking about letting Windows control the size of the paging file. While I would consider that to be a good practice, it doesn't stop the computer from running out of virtual memory.



          At least for the consistency of this question, you should provide some documentation of the actual memory usage of the computer. Like a screenshot from Process Explorer:



          enter image description here



          Also, did you check the Event Log on the machines when the connection is closed? Is there maybe an event that holds more information about the problem?






          share|improve this answer
























            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%2f176451%2fremote-desktop-closes-with-fatal-error-error-code-5%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0















            None of the computers we are using are low on memory (2Gb+) and we let windows manage the virtual memory side of things.




            I think you're talking about letting Windows control the size of the paging file. While I would consider that to be a good practice, it doesn't stop the computer from running out of virtual memory.



            At least for the consistency of this question, you should provide some documentation of the actual memory usage of the computer. Like a screenshot from Process Explorer:



            enter image description here



            Also, did you check the Event Log on the machines when the connection is closed? Is there maybe an event that holds more information about the problem?






            share|improve this answer




























              0















              None of the computers we are using are low on memory (2Gb+) and we let windows manage the virtual memory side of things.




              I think you're talking about letting Windows control the size of the paging file. While I would consider that to be a good practice, it doesn't stop the computer from running out of virtual memory.



              At least for the consistency of this question, you should provide some documentation of the actual memory usage of the computer. Like a screenshot from Process Explorer:



              enter image description here



              Also, did you check the Event Log on the machines when the connection is closed? Is there maybe an event that holds more information about the problem?






              share|improve this answer


























                0












                0








                0








                None of the computers we are using are low on memory (2Gb+) and we let windows manage the virtual memory side of things.




                I think you're talking about letting Windows control the size of the paging file. While I would consider that to be a good practice, it doesn't stop the computer from running out of virtual memory.



                At least for the consistency of this question, you should provide some documentation of the actual memory usage of the computer. Like a screenshot from Process Explorer:



                enter image description here



                Also, did you check the Event Log on the machines when the connection is closed? Is there maybe an event that holds more information about the problem?






                share|improve this answer














                None of the computers we are using are low on memory (2Gb+) and we let windows manage the virtual memory side of things.




                I think you're talking about letting Windows control the size of the paging file. While I would consider that to be a good practice, it doesn't stop the computer from running out of virtual memory.



                At least for the consistency of this question, you should provide some documentation of the actual memory usage of the computer. Like a screenshot from Process Explorer:



                enter image description here



                Also, did you check the Event Log on the machines when the connection is closed? Is there maybe an event that holds more information about the problem?







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered May 4 '12 at 15:21









                Der HochstaplerDer Hochstapler

                68.5k50232288




                68.5k50232288






























                    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%2f176451%2fremote-desktop-closes-with-fatal-error-error-code-5%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







                    Popular posts from this blog

                    VNC viewer RFB protocol error: bad desktop size 0x0I Cannot Type the Key 'd' (lowercase) in VNC Viewer...

                    Tribunal Administrativo e Fiscal de Mirandela Referências Menu de...

                    looking for continuous Screen Capture for retroactivly reproducing errors, timeback machineRolling desktop...