Announcement

Collapse

Please Read: Significant Update Planned, Migrating Forum Software This Month

See more
See less

Unable to take remote after rebooting 2008 server

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Unable to take remote after rebooting 2008 server

    Hi,

    I usually used to take remote of one of our 2008 server but now after rebooting the server, i am not able to connect to the server remotely. The error message displayed is

    "This computer can't connect to the remote computer.

    Try connecting again. if the problem continues, contact owner or network administrator"

    Please help..

    Info: 3389 port access is available, Remote desktop is also enabled.

    Regards,
    Anishk

  • #2
    Has the IP address changed?
    Can you ping etc. to the computer?
    Tom Jones
    MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
    PhD, MSc, FIAP, MIITT
    IT Trainer / Consultant
    Ossian Ltd
    Scotland

    ** Remember to give credit where credit is due and leave reputation points where appropriate **

    Comment


    • #3
      Originally posted by Ossian View Post
      Has the IP address changed?
      Can you ping etc. to the computer?
      Ip address is same. iam able to ping the server and also able to take share.

      Regards,
      Anishk

      Comment


      • #4
        Originally posted by Ossian View Post
        Has the IP address changed?
        Can you ping etc. to the computer?
        Also, In system event logs, Event ID 50 TermDD is generated when rdp is taken "The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client".

        Regards,
        Anishk

        Comment


        • #5
          Originally posted by Ossian View Post
          Has the IP address changed?
          Can you ping etc. to the computer?
          Event ID 50 is generated in the server eventlog TermDD "The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client" while client tries rdp to the server.

          Comment


          • #6
            Is it a physical server or is it a Virtual Machine?

            Oooo, found this.
            1 1 was a racehorse.
            2 2 was 1 2.
            1 1 1 1 race 1 day,
            2 2 1 1 2

            Comment


            • #7
              Originally posted by biggles77 View Post
              Is it a physical server or is it a Virtual Machine?

              Oooo, found this.
              It is a physical server. Tried those steps already.


              netsh int tcp show global

              netsh int tcp set global chimney=disabled

              netsh int tcp set global rss=disabled

              added entry EnableTCPA registry

              didn't find NetDMA.

              Regards,
              Anishk

              Comment


              • #8
                Originally posted by biggles77 View Post
                Is it a physical server or is it a Virtual Machine?

                Oooo, found this.
                Already tried the above steps using the doc

                netsh int tcp set global chimney=disabled


                netsh int tcp set global rss=disabled

                Added EnableTCPA registry entry to 0

                didn't find NetDMA


                Regards,
                Anishk

                Comment


                • #9

                  Already tried the above steps using the doc

                  netsh int tcp set global chimney=disabled


                  netsh int tcp set global rss=disabled

                  Added EnableTCPA registry entry to 0

                  didn't find NetDMA


                  Comment


                  • #10
                    Physical machine

                    Comment


                    • #11
                      Have you checked the account you are using has permission to access the server? Have you checked the account is listed in the allowed users list for remote access in System Properties?
                      A recent poll suggests that 6 out of 7 dwarfs are not happy

                      Comment


                      • #12
                        account used is a member of administrator. But, here the username & password page itself is not prompting.

                        MSTSC -> (Server IP) -> "This computer can't connect to the remote computer.

                        Try connecting again. if the problem continues, contact owner or network administrator"
                        Last edited by Anishk; 2nd June 2018, 05:42.

                        Comment


                        • #13
                          Finally changing encryption level from FIPS Compliant to Client compatible solved the issue. Thanks....

                          Comment


                          • #14
                            Thanks for posting back with your solution!
                            A recent poll suggests that 6 out of 7 dwarfs are not happy

                            Comment


                            • #15
                              This one??

                              https://support.microsoft.com/en-us/...-march-13-2018

                              Comment

                              Working...
                              X