Erreur Connexion bureau à distance

%3CLINGO-SUB%20id%3D%22lingo-sub-3494812%22%20slang%3D%22fr-FR%22%3ERemote%20Desktop%20Connection%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3494812%22%20slang%3D%22fr-FR%22%3E%3CP%3EGood%20morning%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20on%20this%20configuration%3A%3C%2FP%3E%3CP%3EA%20Windows%20server%202022%20with%20HyperV%20on%20which%20are%20installed%202%20VMs%20in%20Windows%20server%202022%2C%20one%20for%20the%20roles%20AD%2C%20ADCS%2C%20DNS%2C%20DHCP%20...%20and%20another%20for%20the%20RDS%20role%2C%20IIS%2C%20...%3C%2FP%3E%3CP%3EEverything%20worked%20perfectly%20until%20today%2C%20but%20following%20a%20power%20outage%2C%20when%20trying%20to%20connect%20to%20the%20RDS%20server%20via%20the%20remote%20desktop%20connection%20I%20receive%20the%20following%20error%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAn%20internal%20error%20has%20occurred%3C%2FP%3E%3CP%3EError%20code%3A%200x4%3C%2FP%3E%3CP%3EExtended%20error%20code%3A%200x0%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20Get-Help%20!%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3494812%22%20slang%3D%22fr-FR%22%3E%3CLINGO-LABEL%3EActive%20Directory%20(AD)%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHyper-V%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ERds%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3497382%22%20slang%3D%22fr-FR%22%3ERe%3A%20Remote%20Desktop%20Connection%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3497382%22%20slang%3D%22fr-FR%22%3EI%20come%20back%20to%20say%20that%20after%20disabling%20the%20NLA%20the%20connection%20via%20remote%20desktop%20to%20the%20RDS%20Server%20is%20functional%20again%2C%20but%20much%20less%20secure%20as%20a%20result!%20What%20can%20I%20do%20to%20make%20everything%20work%20as%20before%3F%20Do%20I%20need%20to%20regenerate%20the%20certificates%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3497901%22%20slang%3D%22en-US%22%3ERe%3A%20Erreur%20Connexion%20bureau%20%C3%A0%20distance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3497901%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CSPAN%3Ebut%20following%20a%20power%20outage%3C%2FSPAN%3E%3CBR%20%2F%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%0A%3CP%3ESounds%20like%20a%20race%20condition.%20Try%20delaying%20the%20RDS%20server%20startup%20so%20that%20active%20directory%20domain%20services%20is%20fully%20started%20before%20RDS%20boots%20up.%20Other%20option%20is%20to%20have%20a%20scheduled%20task%20that%20after%20a%20short%20delay%20restarts%20NLA%20service%20on%20RDS%20server.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Bonjour,

 

Je suis sur cette configuration :

Un Windows server 2022 avec HyperV sur lequel sont installées 2 VM en Windows server 2022, l'une pour les rôles AD, ADCS, DNS, DHCP ... et une autre pour le rôle RDS, IIS, ...

Tout fonctionnait parfaitement jusqu’à aujourd'hui, mais suite à une coupure de courant, lors d'une tentative de connexion au serveur RDS via la connexion bureau à distance je recois l'erreur suivante :

 

Une erreur interne s'est produite

Code erreur : 0x4

Code erreur étendue : 0x0

 

Please Get-Help ! :)

2 Replies
Je reviens pour dire qu'après désactivation du NLA la connexion via bureau à distance au Serveur RDS est de nouveau fonctionnelle, mais beaucoup moins sécurisée du coup ! Que puis-je faire pour que tout refonctionne comme avant ? Dois-je régénérer les certificats ?
but following a power outage

Sounds like a race condition. Try delaying the RDS server startup so that active directory domain services is fully started before RDS boots up. Other option is to have a scheduled task that after a short delay restarts NLA service on RDS server.