Комментарии:
i did all things, even firewall, still not solve plz help
ОтветитьMuito obrigado
ОтветитьThanks. Worked for me.
You don't need a reboot if you open an elevated command prompt after the group policy change and give the command: GPUPDATE /FORCE
I have been trying to solve this problem for so long. The edit group policy did the trick. Thank you for your help!
ОтветитьBrother i owe you a beer - just got a new VPS for my trading and it wouldnt work... strange as i was using another VPS a week prior... is it possible ive picked up a bug from the dark web and its altered these settings ? (It fixed my Internal error) thanks again
ОтветитьHow I can fix it on Android?
ОтветитьWorked like a charm
ОтветитьJust simply change your default port from 3389 to any other 3379 or 3388 any you like it will work
ОтветитьJust simply change your default port from 3389 to any other 3379 or 3388 any you like it will work
ОтветитьThank you your a life saver, it worked perfectly . i had afew people try but failed you succeeded first time thank you very much!
ОтветитьDoes anyone els thinks he sounds like Kermit
ОтветитьGreat.....
ОтветитьAnd Windows XP ??? PLEASE 🙏
Ответитьit worked, thanks
ОтветитьIt works for me. Much appreciated!
ОтветитьUnchecking "Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended)” in the Remote Settings worked for me.
ОтветитьI can’t get mine fixed, it’s saying
Remote access to server is not enabled
The remote computer is turned off
The remote computer is not available on the network
I have set up everything but still it’s not connecting.. I need help please
my OS is window 10 home and it is giving the same error as you explained the videos but I want to know that does RDC support in window 10 home
ОтветитьVery easy to understand. Good work!
ОтветитьWorks
ОтветитьFuncionou no meu caso. Obrigado plea dica! Parabéns pelo vídeo.
Ответитьstill Facing the same Issue. please Help.
ОтветитьThis didnt work for me what did work is on the host computer open a command prompt with admin privileges type net stop termservice then type net start termservice and you should be good to go
ОтветитьTHANK YOU...I have been trying to figure this out for Server 2016 for a while. The Security Layer setting in the Local Policy was the fix.
ОтветитьGood thanks
ОтветитьThank you very much sir,worked very well for my installed Windows10
ОтветитьSometimes the issue is with the PC you are connecting to. Try doing a network reset (located in the network and Internet settings on windows 10) on the PC you are logging into and that will repair the issue. I had the same issue today and that was the fix. Super easy.
ОтветитьSadly none of these worked to fix my "Internal Error"....any other suggestions? I am so frustrated with this as I really want to work from home. I have even tried resetting my computer and a dozen other fixes I have found online. Any help would be appreciated as I am really trying hard not to have to wipe my pc. Thank you!!!
ОтветитьResolved thank you!!
ОтветитьThanks it works
ОтветитьAre these steps done on the machine you are connecting to, or the one you are connecting FROM?
ОтветитьThank you, saved me from doing a rebuild after a windows update killed my RDP, the group policy thing did the trick!
ОтветитьIt works. Thank you.
ОтветитьI'm your first commenter 😁😁
Ответить