SP1 is installed - and your reference to KB2667402 seems to be correct. I finally found this webpage and so far so good.
http://www.petri.co.il/rdp-windows-server-2008-r2.htm# On Tue, Dec 3, 2013 at 10:55 AM, Randal, Phil <[email protected]>wrote: > Further on from that clue… > > > > If SP1 is installed, and Rdpcorekmts.dll is 6.1.7600.16952, then you need > to reinstall http://support.microsoft.com/kb/2667402 > > > > (see the ‘known issues’) > > > > Cheers, > > > > Phil > > > > -- > > *Phil Randal* > > *Infrastructure Engineer* > *Hoople Ltd | Thorn Office Centre | Hereford HR2 6JT* > > Tel: 01432 260415 | Email: [email protected] > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Randal, Phil > *Sent:* 03 December 2013 14:35 > > *To:* [email protected] > *Subject:* RE: [NTSysADM] Windows 2008 R2 RDP Issues > > > > What, no SP1 on the box? > > > > -- > > *Phil Randal* > > *Infrastructure Engineer* > *Hoople Ltd | Thorn Office Centre | Hereford HR2 6JT* > > Tel: 01432 260415 | Email: [email protected] > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Kelli Sterley > > *Sent:* 03 December 2013 13:46 > *To:* NT System Admin Issues Discussion list > *Subject:* Re: [NTSysADM] Windows 2008 R2 RDP Issues > > > > 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 > > > > Hoople Ltd, Registered in England and Wales No. 7556595 > > Registered office: Plough Lane, Hereford, HR4 0LE > > "Any opinion expressed in this e-mail or any attached files are those of > the individual and not necessarily those of Hoople Ltd. You should be aware > that Hoople Ltd. monitors its email service. This e-mail and any attached > files are confidential and intended solely for the use of the addressee. > This communication may contain material protected by law from being passed > on. If you are not the intended recipient and have received this e-mail in > error, you are advised that any use, dissemination, forwarding, printing or > copying of this e-mail is strictly prohibited. If you have received this > e-mail in error please contact the sender immediately and destroy all > copies of it." > >
