Skip to content
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

14393 Even if RDP Listener State is listening, no concurrence users are allow. #353

Open
iinrlv00 opened this issue Nov 22, 2017 · 11 comments

Comments

@iinrlv00
Copy link

Ver W10 Pro 14393.1884
Ver termsvr.dll 10.0.14393.1737
Last INI avalaible from ebdd795

RDPConf.exe -> OK Listener state : Listening [fully suported]

captura

Working properly for months.
Now concurrence users are not supported anymore. A new season close the older one.
Seems affected by a W10 update ( updateds installed after last confirm RDPWrapper proper use: KB4023057, KB4011188, KB4011197, KB4011270, KB4048951, KB4048953, KB890830, KB4049065, KB4023057)

Thanks for your amazing job!

@iinrlv00 iinrlv00 changed the title Even if RDP wrapper is listening, non concurrence urers are alow. 14393 Even if RDP Listener State is listening, no concurrence users are allow. Nov 22, 2017
@endmarsfr
Copy link

endmarsfr commented Nov 23, 2017

Hello,
I had the same issue.
I succeeded using two different users (not the same login)
please see : #326

@binarymaster
Copy link
Member

@iinrlv00 I noticed there is old version of RDPConf in your screenshot.

@iinrlv00
Copy link
Author

@binarymaster , you are right.
I have installled v1.6.1, but RDPConf v1.6.1 is reconaized as virus by my Mcafee, so i have used an older RDPConf v1.6 whitch seems ok for Mcafee.
Anyway RDPwrap.dll in ProgramFiles is in version v1.6.1.

@endmarsfr
Copy link

I already installed latest rdpwrap v1.6.1 but it it still show v1.5 in the GUI
and still same behavior

@iinrlv00
Copy link
Author

image
I have reinstall v1.6.1 in a new instance of the machine. Same condition, no more concurrent users allow anymore....

@wastingoctober
Copy link

wastingoctober commented Nov 30, 2017

I'm encountering this issue as well even after reinstalling. If I use the RDPCheck.exe app, I can connect on 127.0.0.2, but it doesn't work when connecting via RDP.

@sebaxakerhtc
Copy link

Closed as solved. If not - reopen it.

@sebaxakerhtc
Copy link

Some helpful info can be found here #1883

@ghost
Copy link

ghost commented Jun 4, 2022

Which Microsoft Visual C++ Redistributable are needed?

@JEmlay
Copy link

JEmlay commented Jun 8, 2022

Which Microsoft Visual C++ Redistributable are needed?

Does it use it? When I load a new machine one of the first things I do is install RDP Wrapper and it works fine (well, used to) on a vanilla machine all by itself.

@JEmlay
Copy link

JEmlay commented Jun 8, 2022

I had originally posted my termsrv.dll in #1873 . Was it actually checked? Now that I'm trying to do this on my own the only hex I see listed on the interwebs is:

39 81 3C 06 00 00 0F 84 DB 61 01 00
39 81 3C 06 00 00 0F 84 2B 5F 01 00
39 81 3C 06 00 00 0F 84 21 68 01 00
39 81 3C 06 00 00 0F 84 D9 51 01 00
39 81 3C 06 00 00 0F 84 5D 61 01 00
39 81 3C 06 00 00 0F 84 5D 61 01 00
39 81 3C 06 00 00 0F 84 3B 2B 01 00
39 81 3C 06 00 00 0F 84 B1 7D 02 00

However my hex is:

39 81 3C 06 00 00 0F 84 2B 86 01 00

I'm curious why mine isn't listed anywhere. I know it doesn't matter and I just replace what's there but I wonder if it's why RDP Wrapper isn't working.

RDPConf still lists my version as 10.0.19041.1682

BTW, after having altered my DLL myself, it works fine. I can login as two different users. So something very screwy is going on here between RDP Wrapper and the info in the INI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants