-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows 10 version 10.0.18362.267 not supported #848
Comments
net stop termservice |
@SlavaSumyUA thank you, it works good. Do you know if it's possible to resume an already open rdp session? |
it does have admin rights. it gives me this error every time. and when I rdp into the machine it locks the screen. If I uncheck single session per user, that works. it just doesn't work with it in single session per user. |
@yotoprules try with gui or default auth only. network level auth doesn't work |
I already tried that and it still locks me out as the other user connects through RDP. |
So unistall everything and retry from scratch. On my system it works good. |
I've tried that when updating the ink file. Maybe I'll upload a video and show what happens when I get to my pc. |
|
@yotoprules try this:
and try again. |
What about 32 bit (x86) offsets for termsrv.dll version 10.0.18362.267 ? Any progress yet? |
Not working for me either... This is about the 20th time I've had to refresh the concurrent RDP wrapper or termsrv.dll so I'm not new to it, but I can't get it to work this time around... I'm on Win 10 V 1903 build 18262.267, which means termsrv.dll 10.0.18362.267. I've tried the "replace the RDP Wrapper file" with the one linked above by SlavaSumyUA, no luck. Tried modifying my existing rdpwrapper.ini with the code in graphixillusion comment, no luck. Have, of course, done a complete reboot after each attempt... Holding on additional solutions, hopefully they're out there! |
|
@toddmaddison are you using Win 10 Pro? This is very strange, i tried it on two different machines and it works perfect on both sides. |
Yes, sorry I didn't mention that. I've been on Pro for probably at least 3-4 years, have updated termsrv multiple times in that period, it has always worked before... Any suggestions on logs or anything I can look at to see what's failing? |
this is the ini i'm using. try with this file. |
Thanks SlavaSumyUA that worked great |
Hi everyone, please confirm that network level auth does work. Without it this solution is insecure. |
Gosh darn it, tried your new file, rebooted, etc, etc - no luck... Still limited to a single login on the machine... Thanks for the help, though! |
NLA doesn't work. If you need this to remotely connect to your machine using RDP protocol, never expose the port to the internet. Use a private VPN or a secure ssh tunnel with it with a super strong public/private key auth. |
It's very bad that NLA doesn't work, it worked flawlessly on version 10.0.18362.53. |
@romanad |
hey i go it work with nla i just use a (termsrv.dll) from 18362.239 |
Symantec Endpoint Protection has nice IPS service for Windows that prevents common attacks including RDP brute-force. |
Has anyone tested solution from Dyna-007 - does it work for everyone? |
@asmtron Thank you very much for your effort. NLA auth still doesn't work though. And what about to resume an already opened session? Right now it will always open a new one. |
Excellent, works perfectly! |
Hello guys! |
I confirm it works well, thank you very much guys. |
@romanad you got nla and open session resume working too? |
Yes all works fine, no issues at all. |
@romanad what did you do for make them work? On my system if i choose NLA, it always revert back to GUI auth only after the first connect. And i can't have open session resuming becouse it always starts a new session. |
I just replaced ini file in program files and restarted RDP service according to the instruction. |
@romanad No, if you check single session per user in the config, the concurrent logins will stop working. I mean, i would like to restore the old behaviour like the system should prompt a window which offers you the option to resume the already opened session or start a new one. |
https://i.imgur.com/fjdvjwc.png |
Using the RDPCheck.exe or the default mstsc.exe, the NLA auth doesn't work: as i said it reverts back to GUI Auth only after the first connect. I just tried with another rdp client, freerdp for windows and with it NLA works as it should. Just want to report. Now i just need to find a way to resume an already opened concurrent session. |
Sorry to hear that friend. I have no issues at all. I suggest to install your clean version of windows to new VM a test if the issue appears. I tested on Windows x64 Enterprise En. |
@romanad i already tried several times but i always get the same behaviour. Talking about the sessionID, i have tried to connect to the console with this command: mstsc /admin /v:ipaddress but nothing: it doesn't connect to the default console but it opens a new session. During my tests, i observed one thing: when you conect using rdp, the query session shows rdp-tcp#xx in the list. When you disconnect, that value will becomes CONSOLE with a sessionID number which is progressively increase by one each new try. I don't know if it's related. In the meantime we can use tscon switch as a workaround. |
I don't know what's wrong with your configuration, but that same command works fine for me. |
Well, who knows. This is the dafult behaviour on two different machines, clean install, Win10 Pro |
Got it working after removing everything and starting from scratch. |
Muchas gracias hermano uff me sirvio mucho |
THANKS YOU so much for everyone who is involved in the ini-updates above!!! |
I had this situation. |
try updates from others like #860 |
Yes! It Worked!!! Thanks (-_-*) |
In order for everything to work, it is necessary to replace termsrv.dll x64 |
Thanks it worked |
No description provided.
The text was updated successfully, but these errors were encountered: