Same as Dhiraj ... the service is running, the port is open and this is logged in the event log.
Faulting application name: svchost.exe_TermService, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1 Faulting module name: rdpcorekmts.dll, version: 6.1.7600.16952, time stamp: 0x4f1f9e66 Exception code: 0xc0000005 I can manage it remotely just fine - it's when we try to use remote desktop that it just won't connect. On Fri, Nov 29, 2013 at 8:17 PM, Ken Schaefer <[email protected]> wrote: > Is the service running? > Is the port open? > Is there anything logged in the Windows Event Log (e.g. a logon failure?) > > Cheers > Ken > > -----Original Message----- > From: [email protected] [mailto: > [email protected]] On Behalf Of Haritwal, Dhiraj > Sent: Saturday, 30 November 2013 1:10 AM > To: [email protected] > Subject: RE: [NTSysADM] Windows 2008 R2 RDP Issues > > Sometimes I have seen this behaviour on some servers. RDP is always > enabled so don’t think so we have to force it through GPO but still won’t > be able to login through RDC. Atleast once need to login locally then only > can login through RDC. > > I would also like to know if anybody find any solution for this issue. > > > Dhiraj > > > > -----Original Message----- > From: [email protected] [mailto: > [email protected]] On Behalf Of Kurt Buff > Sent: 28 November 2013 00:30 > To: [email protected] > Subject: Re: [NTSysADM] Windows 2008 R2 RDP Issues > > Does one of your GPOs enable RDP? > > That's what I do, and it never fails me. > > Kurt > > On Wed, Nov 27, 2013 at 8:59 AM, Kelli Sterley <[email protected]> > wrote: > > The time is dead on and it only occurs on reboots. It really is the > > weirdest thing. And it only happens to this particular server - none > > of my other Win2008 R2 boxes. They all have the same GP's applied to > them. > > > > > > > > On Mon, Nov 25, 2013 at 2:21 PM, John Cook <[email protected]> wrote: > >> > >> I’ve noticed it when the RDP session didn’t close cleanly and it left > >> the session active on the computer but never during a reboot. I’ve > >> seen it on a select few VM’s, nothing I could do but log in through > >> the VCenter and log on and off then it was fine. Maybe this will help > >> http://support.microsoft.com/kb/2571388 > >
