logo elektroda
logo elektroda
X
logo elektroda

Dell Optiplex 780 on Win7: Remote Desktop Connection Interruptions & Event Log Entries

WookaszT 9264 12
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
  • #1 16371662
    WookaszT
    Level 12  
    Hello,

    I started noting the following problem.
    No matter if I am connected to my remote computer via remote desktop or not. For unknown reasons, he suddenly stops responding. If I have a session on, it kicks me out, if not - I simply can't connect anymore.
    I don't know what that might be about.
    I had a computer in this configuration for 2 years and I had no such problems.

    It looks like it is crashing somehow, but it does not crash, because there are entries in the event log all the way (manual reset).
    There are also no big bugs (or I don't know) - I can upload screen.

    After such a reset, the start goes without problems and works again until the next blocking of access: / About several dozen minutes.
    It is Dell Optiplex 780 on Win7.
    What else should I give - a screen from the log?

    Thanks to everyone for any help!
  • ADVERTISEMENT
  • #2 16371736
    jdubowski
    Tube devices specialist
    WookaszT wrote:
    If I have a session on, it kicks me out, if not - I simply can't connect anymore.


    Do you make connections in the LAN or do you connect to the Internet through a VPN or a redirected port?
    Do you only have a Windows firewall on the server you connect to or do you have any other traffic control applications?
    After the "hang" service, "Remote Desktop Service" works?

    https://support.microsoft.com/pl-pl/help/2477...disconnected-errors-in-windows-server-2008-r2
  • ADVERTISEMENT
  • #3 16371777
    WookaszT
    Level 12  
    I connect through the external port of my network - this is what I have in the remote desktop, because I connect from different places and it's more convenient for me - it always worked. Also from outside and then redirected port.
    This computer is not a server, but an ordinary desktop with windows 7 - without traffic-regulating applications - and the windows itself after installation was practically not touched. I turn on this computer remotely from time to time to exchange data. It stands without a monitor or keyboard, so I have limited diagnostic possibilities.
    Right now I'm on my local network.
    Unfortunately, I don't know what happens after the hang, because then my remote desktop session freezes and I have to restart it manually. Then it turns on without a problem (I connected the TV standing next to it and suspected the start) and windows respond normally. I log in remotely and I have a connection to "disconnect" again :(
  • ADVERTISEMENT
  • #4 16372033
    jdubowski
    Tube devices specialist
    WookaszT wrote:
    This computer is not a server, but an ordinary desktop with windows 7


    Server as defined by Remote Desktop Service. The client is mstsc.exe that runs on the remote computer.

    WookaszT wrote:
    Right now I'm on my local network.


    And it "crashed"? After the communication is suspended, check if you also lose connection if you connect to the local network. Maybe the fault lies with your network router.

    WookaszT wrote:
    Unfortunately, I don't know what happens after the hang, because then my remote desktop session freezes and I have to restart it manually. Then it turns on without a problem (I connected the TV standing next to it and suspected the start) and windows respond normally. I log in remotely and I have a connection to "disconnect" again :(


    Well, either plug in a keyboard and mouse there, or install another remote access capability such as VNC.
  • ADVERTISEMENT
  • #5 16372800
    WookaszT
    Level 12  
    After losing connectivity, I cannot get through the remote desktop, even if I am on the local network and use the direct local address of the computer.
    Still, I guess I'm betting on the computer. The router is rather decent and there weren't any changes either. I noticed that after hanging up, I can not see any picture on TV - but I do not know yet if it is not specific to TV. I think I will have to connect a normal monitor, keyboard and mouse there and see if I have control when I lose connectivity. It is strange that there are no errors in the log that would tell you something. When I get home, I'll try and answer. All the time thanks for your efforts ...
  • #6 16372895
    jdubowski
    Tube devices specialist
    WookaszT wrote:
    After losing connectivity, I cannot get through the remote desktop, even if I am on the local network and use the direct local address of the computer.


    So the router is innocent.

    WookaszT wrote:
    I noticed that after hanging up, I can not see any picture on TV - but I do not know yet if it is not specific to TV. I think I will have to connect a normal monitor, keyboard and mouse there and see if I have control when I lose connectivity.


    This is probably the specificity of screen blanking. Connect the mouse and you'll find out ...
  • #7 16373770
    WookaszT
    Level 12  
    Welcome back.
    I waited for it for a very moment, but at that moment it "crashed" again. It was extremely long since 6:30 am. Everything was fine as it used to be. I used to call home from outside the house. By RDP clients on the phone, on the laptop - all right.
    A dozen or so minutes ago, I stopped logging in. The router's statistics show that the computer is connected, but there is no transfer at all, so it may be some form of suspension. I brought and hooked up a computer monitor, keyboard and mouse - and ... nothing. Nothing on the screen and the computer does not react - it does not react.

    I will not reset it for now. He stands unanswered. If anyone has an idea, I can try to verify it.
    Thanks a lot!

    Edit.
    Do not quote the preceding posts in their entirety, there is no such need and it is bad to read. RADU23
  • #8 16373923
    enhanced
    Level 43  
    Check the memtestem framework, insert a screen from smart - crystaldiskinfo.
    Give him the OCCT cpu, gpu and if the power supply fails.
  • #9 16374162
    jdubowski
    Tube devices specialist
    WookaszT wrote:
    A dozen or so minutes ago, I stopped logging in. The router's statistics show that the computer is connected, but there is no transfer at all, so it may be some form of suspension. I brought and hooked up a computer monitor, keyboard and mouse - and ... nothing. Nothing on the screen and the computer does not react - it does not react.


    So a more general problem, and probably a hardware problem - the enhanced friend rightly advises to start with checking the disk and memory, see what the CPU temperatures look like.
  • #10 16377195
    WookaszT
    Level 12  
    enhanced wrote:
    Check the memtestem framework, insert a screen from smart - crystaldiskinfo.
    Give him the OCCT cpu, gpu and if the power supply fails.


    Welcome back,
    I did all the tests and I guess it's okay.
    You can find them all here:
    Link
    Hasn't crashed since yesterday.

    ... and when you wrote about this smart test, I remembered something from a few months ago. Namely, a smart error popped up and the system did not turn on and after a few such attempts - finally it turned on one time and it has been on since then and I forgot about it. Crystal disk probably didn't detect anything wrong, so I don't know anymore, but since I remembered it, it's probably worth mentioning.
    Many thanks for your help.
    Regards.] Link [/url]
  • #11 16377373
    enhanced
    Level 43  
    I don't like BC - monitor this value.

    Give him the hddscan read test. You will check if it will not hang because BC shows that the HDD is hanging (poor connection with the mobaskiem).
  • #13 16379528
    enhanced
    Level 43  
    More like a sata cable, but check how it hangs if the smart changes.

Topic summary

The discussion revolves around issues experienced with a Dell Optiplex 780 running Windows 7, specifically regarding interruptions in Remote Desktop Connection (RDP). The user reports that the system becomes unresponsive, disconnecting active sessions and preventing new connections, despite no apparent crashes indicated in the event logs. Various troubleshooting steps are suggested, including checking network configurations, testing hardware components (such as memory and hard drive), and ensuring proper connections. The user eventually connects a monitor and peripherals to diagnose the issue further, suspecting potential hardware failures, particularly with the hard drive or SATA cable. The conversation emphasizes the importance of monitoring system health and connectivity to resolve the recurring access problems.
Summary generated by the language model.
ADVERTISEMENT