ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Suddenly Can't RDP

    IT Discussion
    windows 8.1 rdp pertino
    3
    5
    1.7k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • thanksajdotcomT
      thanksajdotcom
      last edited by thanksajdotcom

      So I RDP to my home computer over my Pertino connection to use Chrome primarily because my work computer is incapable of running smoothly if I have Chrome open with all the tabs I use. Well, I rebooted a few minutes ago and can now no longer RDP to my home laptop. I can ping the Pertino interface. If I SSH into my jump server, I can ping it locally as well. I can open it in Teamviewer and see it's working. I made sure the RDP settings haven't changed. It just suddenly stopped working. I also can RDP to one of my other machines on the same network, but cannot RDP from that machine to my home laptop either. I'm going to check Windows Firewall next but this is just weird. I did run a couple Windows Updates but not sure what would have changed...

      EDIT: Ok, that was weird. Just tried it again and now I can RDP again no problem. Not sure why it wasn't working. Disregard thread.

      1 Reply Last reply Reply Quote -2
      • thanksajdotcomT
        thanksajdotcom
        last edited by

        This post is deleted!
        1 Reply Last reply Reply Quote 0
        • gjacobseG
          gjacobse
          last edited by

          Timing?

          It's possible that there was an off chance that all the services had not started an that port / service wasn't available yet?

          thanksajdotcomT 1 Reply Last reply Reply Quote 0
          • thanksajdotcomT
            thanksajdotcom @gjacobse
            last edited by

            @g.jacobse said:

            Timing?

            It's possible that there was an off chance that all the services had not started an that port / service wasn't available yet?

            That's what I'm thinking.

            1 Reply Last reply Reply Quote 0
            • StrongBadS
              StrongBad
              last edited by

              With so many services starting up, there is a lot of chances for things to have not all fired up yet.

              1 Reply Last reply Reply Quote 1
              • 1 / 1
              • First post
                Last post