Listener state: Not listening not supported about rdpwrap HOT 14 CLOSED

Confirming the same issue on Windows 10 Home.

from rdpwrap.

Why you don't read closed issues?

from rdpwrap.

Got it but why don't you make a download that just works to avoid the same issue being reported again and again and again ?

from rdpwrap.

Indeed... v1.6 released! :)

from rdpwrap.

So does v1.6 now support running a session on one PC (under my username)
then continuing that same session (applications still running) from another
PC (again under my username)?

On Wed, Aug 12, 2015 at 11:58 AM, binarymaster [email protected]
wrote:

Indeed... v1.6 released! :)

—
Reply to this email directly or view it on GitHub
#51 (comment)
.

from rdpwrap.

So does v1.6 now support running a session on one PC (under my username)
then continuing that same session (applications still running) from another
PC (again under my username)?

No, see this issue: #37

from rdpwrap.

I see in issue #37 #37 that
this has been around since Win8. I've been using it for exactly that on
Win8.1 for quite a while - never had an issue.

So please explain: if this does not work, what exactly does RDPWrapper
accomplish on Windows 10? Isn't that the whole point of it?... (Confused.)

On Wed, Aug 12, 2015 at 12:15 PM, binarymaster [email protected]
wrote:

So does v1.6 now support running a session on one PC (under my username)
then continuing that same session (applications still running) from another
PC (again under my username)?
No, see this issue: #37
#37

—
Reply to this email directly or view it on GitHub
#51 (comment)
.

from rdpwrap.

I actually have none of these issues on my Windows 10 Virtual Machine, so I can't confirm nor refuse it... You have to test it yourself.

from rdpwrap.

Tested on Win 10 Home edition, both 32 and 64 bits, and indeed rdpwrap does nothing...
TermServ service is not even listening on 3389 port.

from rdpwrap.

@aiugrivef
Did you test latest v1.6 release?

from rdpwrap.

Aiugrivef, does it at least accomplish the following? If User A is
physically sitting at and using the "server" - can User B concurrently
access his own login on the server from another computer?

On Wed, Aug 12, 2015 at 12:49 PM, aiugrivef [email protected]
wrote:

Tested on Win 10 Home edition, both 32 and 64 bits, and indeed rdpwrap
does nothing...
TermServ service is not even listening on 3389 port.

—
Reply to this email directly or view it on GitHub
#51 (comment)
.

from rdpwrap.

does it at least accomplish the following? If User A is
physically sitting at and using the "server" - can User B concurrently
access his own login on the server from another computer?

Yes. See the latest screenshot in the README.md

from rdpwrap.

Sorry to bother you.
It is the first time that I use issues. Before I post the issue, I have not noticed that there is a column called closed issues.
Never happen next time.

from rdpwrap.

Thanks :)

from rdpwrap.