Windows Thread, Remote Desktop connection to server problem in Technical; Interesting you think that. I'll take a deeper look and let you know...
17th June 2011, 05:14 PM #16
Interesting you think that. I'll take a deeper look and let you know
17th June 2011, 05:24 PM #17
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.
17th June 2011, 05:36 PM #18
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?
20th June 2011, 09:40 AM #19
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
20th June 2011, 09:46 AM #20
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 10:05 AM.
16th September 2013, 07:55 PM #21
- Rep Power
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.
16th September 2013, 10:29 PM #22
This is how I fix it:
It turns out that the cause for the problem is two important Windows security updates:
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.
By pete in forum Downloads
Last Post: 17th June 2010, 06:40 PM
By albertwt in forum Windows Server 2008 R2
Last Post: 24th March 2010, 12:42 AM
By jmair in forum Windows
Last Post: 29th October 2008, 08:09 PM
Last Post: 21st October 2007, 03:11 PM
By russdev in forum Wireless Networks
Last Post: 16th November 2005, 09:07 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)