+ Post New Thread
Page 2 of 2 FirstFirst 12
Results 16 to 22 of 22
Windows Thread, Remote Desktop connection to server problem in Technical; Interesting you think that. I'll take a deeper look and let you know...
  1. #16
    randle's Avatar
    Join Date
    Dec 2006
    Location
    Chelmsford, Essex
    Posts
    604
    Thank Post
    68
    Thanked 17 Times in 16 Posts
    Rep Power
    20
    Interesting you think that. I'll take a deeper look and let you know

  2. #17

    m25man's Avatar
    Join Date
    Oct 2005
    Location
    Romford, Essex
    Posts
    1,663
    Thank Post
    49
    Thanked 473 Times in 342 Posts
    Rep Power
    142
    Sounds like you have another application/service running that is overlapping the RDP stack.

    What do you see in a dos box when you run netstat -a

    Is port 3389 bound and listening on the correct IP?

    Try disabling any other non critical services or recently installed apps and restart the Terminal Services or reboot the server this may reveal which app is preventing your RDP from starting correctly.

  3. #18

    maniac's Avatar
    Join Date
    Feb 2007
    Location
    Kent
    Posts
    3,081
    Thank Post
    210
    Thanked 431 Times in 311 Posts
    Rep Power
    145
    It was event 2019 that was plaguing our error logs, I've just looked back at my notes. Is that the same error you're getting?

  4. #19
    randle's Avatar
    Join Date
    Dec 2006
    Location
    Chelmsford, Essex
    Posts
    604
    Thank Post
    68
    Thanked 17 Times in 16 Posts
    Rep Power
    20
    Since rebooting I can log on so will be a little while before this starts being an issue again. When it does I'll check out what's been mentioned and report back.

    I haven't been getting any errors in the event log but will double check next time.

    Thanks for your replies

  5. #20
    RobBaxter's Avatar
    Join Date
    Jun 2011
    Location
    Baldock
    Posts
    93
    Thank Post
    8
    Thanked 21 Times in 15 Posts
    Blog Entries
    1
    Rep Power
    11
    It's something in windows update. *Fumes towards MS direction* if its Windows Server 2008 R2 (as i have) I am unsure as to if this happens on other versions.

    Anywhoo... let me explain. When my servers installed SP1 for R2 back in feb, when they applied the update, which the server was "online" maybe services apeared in a state of wierd 1/2 up 1/2 down mode. RDP was one of them, while authentication seemed to be functioning, the moment it tryed to show me a desktop the application just terminated as if i closed it my self.

    What I later found out, was while windows is applying updates "which in theory is only when it boots". Once the updates where applied, the RDP sessions worked fine.

    Now, its very coincidental that a professional such as yourself seems to have the "same" symptoms. Try taking a look at windows update and see if its glitching out on you, as maybe this is a reason for the "wierd time to kick in" as we all know, windows update is scheduled, do they coincide?

    Food for thought!
    Last edited by RobBaxter; 20th June 2011 at 11:05 AM.

  6. #21

    Join Date
    Sep 2013
    Location
    ooltewah
    Posts
    1
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0

    I found it was Windows Server 2008 SP2 - waiting for OK at the 'actual' console

    In my case, it was after applying Windows Server 2008 SP2 - the console itself was waiting for a person to click "Ok" that SP2 had finished installing.
    Sometimes, there's an additional whrily-gig of dos-window activity related to the Service Pack CAB file after you log in.
    Funny thing: even if you RDP /console (or /admin), it won't let you in, you have to go THE ACTUAL console, login and click 'OK.'
    Maybe because some piece of RDP itself was being updated.
    After clickink 'ok' at console, all is well, RDP is happy, etc.

  7. #22
    ass17's Avatar
    Join Date
    Feb 2013
    Posts
    361
    Thank Post
    5
    Thanked 40 Times in 37 Posts
    Rep Power
    27
    This is how I fix it:

    It turns out that the cause for the problem is two important Windows security updates:

    KB 2621440
    KB 2667402
    These updates were part of MS012-20, and were downloaded to the servers sometime in the second half of March 2012, if their settings were configured so.

    The solution to the problem begins by uninstalling both updates. First, we uninstall KB 2667402:

    Then we reboot the server.

    Next, we uninstall KB 2621440:

    Then we reboot the server again.

    Now, we need to reinstall the updates, but we need to do so in this particular order.

    First, install KB 2667402:

    Then reboot the server.

    Next, we install KB 2621440:

    Then reboot the server again.



SHARE:
+ Post New Thread
Page 2 of 2 FirstFirst 12

Similar Threads

  1. MS Remote Desktop Connection Manager 2.2
    By pete in forum Downloads
    Replies: 5
    Last Post: 17th June 2010, 07:40 PM
  2. Replies: 3
    Last Post: 24th March 2010, 01:42 AM
  3. Remote Desktop Connection to Server.
    By jmair in forum Windows
    Replies: 3
    Last Post: 29th October 2008, 09:09 PM
  4. Remote Desktop Connection Problem
    By FN-GM in forum *nix
    Replies: 15
    Last Post: 21st October 2007, 04:11 PM
  5. isa server and remote desktop connection
    By russdev in forum Wireless Networks
    Replies: 1
    Last Post: 16th November 2005, 10:07 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •