Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
User gets error stating account has been disabled and Event ID 56 in event log (TermDD)

Answered User gets error stating account has been disabled and Event ID 56 in event log (TermDD)

  • Thursday, November 15, 2012 2:37 AM
     
     
    Sign In to Vote
    0

    Server Machine: Windows 7 Ultimate (Sorry, but there isn't a W7 TermServ forum - I'm guessing the code is the same though....)
    Client Machine: Vista Ultimate

    When a user attempts to connect to a W7 box, using machine.domain, from Vista he gets the error stating 'Your account has been disabled.  Please contact a system administrator' after entering the credentials.  On the W7 box TermDD creates an Event ID 56 (The Terminal Server security layer detected an error in the protocol stream and has disconnected the client. Client IP: x.x.x.x).

    However, when connecting using the W7 machines IP address, all is good and user logs in ok.  In addition, connecting from an XP box - using machine.domain or IP address - works fine.   No events are created on the Vista machine and it is the admin account on the W7 that is trying to be logged in to.

    This issue was triggered when I changed the machine name and setup an authoritive/recursive DNS on my LAN.  A symptom was that a Certificate warning was also being shown stating that the machine name it was issued to was different to the machine name I'm connecting to (IE. machine.domain).

    Can anyone suggest where I look to fathom this one out.  I'd like to be able to understand what the sequence of events is when connecting Term Serv.

     

All Replies

  • Thursday, November 15, 2012 10:43 PM
     
     
    Sign In to Vote
    0
    This has me totally stumped.  I've been binging the issue and digging but no - are there any debugging things/files I can hook into?
     
  • Sunday, November 18, 2012 10:01 AM
     
     
    Sign In to Vote
    0

    It seems to be a client-side issue.  Other users/machines can use the url (IP or NetBIOS) and connect ok.  But for this one user on this specific machine me gets 'Your account has been disabled.  Please contact a system administrator'.  Am I missing the glaring obvious?  I've read through other threads that mention Event 56 but none shine a light on it.

    Totally flumoxed; is there a forum that has TermServ/RD guru's on it?

    • Edited by Mat Walker Sunday, November 18, 2012 10:04 AM
    •  
     
  • Sunday, November 18, 2012 10:21 AM
    Moderator
     
     Answered
    Sign In to Vote
    0

    Hi,

    1. Please make sure you are using the full user name (domain\username) when using Remote Desktop to connect to the remote computer.  If you are trying to log on to a local account on the remote computer, then use .\username or machinename\username for your user name.

    2. If you have not done so already, please update your Vista to Remote Desktop Client 7 (6.1.7600):

    Description of the Remote Desktop Connection 7.0 client update for Remote Desktop Services (RDS) for Windows XP SP3, Windows Vista SP1, and Windows Vista SP2

    http://support.microsoft.com/kb/969084

    Thanks.

    -TP

    • Marked As Answer by Mat Walker Sunday, November 18, 2012 9:54 PM
    •  
     
  • Sunday, November 18, 2012 10:06 PM
     
     
    Sign In to Vote
    0

    Hah!!!  TP[] you are a guru!!

    Isn't that weird.  I had not tried giving a full username (machine\user) as the Windows Security dialog showed the machine name as the one being used.  So I, sceptically, tried and hey presto it worked!  Indeed, after it had worked NOT using the full name started to work - so a switch had been flicked somewhere.

    Interestingly I am on RD 6.0.6002 - I didnt know there was an update (I'd kinda have expected it to be part of an Auto Update - or is it very different?).  Going to update now.

    Thanks again TP[] - I'd love to know what was causing the issue and why the strange 'Your account has been disabled.  Please contact a system administrator' message (that's the Tester in me :-)).  If I get time I may try and recreate it (now I know the fix).