Hi all,

We have quite some pc's in our local network. All of them are Windows 10
Pro x64. From my pc I created RDP connections to the other pc's. With 2
of them it works fine. With 2 other pc's I get the message: "You have
been disconnected because another connection was made to the remote
computer." And then the connection breaks.
What can be wrong?

Thanks in advance.

Fokke Nauta

Fokke Nauta <usenet@solfon.nl> wrote:

> We have quite some pc's in our local network. All of them are Windows
> 10 Pro x64. From my pc I created RDP connections to the other pc's.
> With 2 of them it works fine. With 2 other pc's I get the message:
> "You have been disconnected because another connection was made to
> the remote computer." And then the connection breaks. What can be
> wrong?

As I recall, you get just 2 concurrent RDP connections. With Terminal
Server, you get more. If a user does not logoff, their session remains
active, and counts against the quota of max concurrent sessions. A
session could freeze, the user closes the window(s) and leaves, but the
session is still active. You get a lot of users that just leave at the
end of the workday instead of logging out of their RD session.

It's been many years (probably a decade) since I last used RDP. There
was some admin-level tool you used to kill the still-alive sessions.

https://smallbusiness.chron.com/kill-remote-desktop-sessions-55424.html
https://www.msnoob.com/how-to-remotely-force-kill-a-remote-desktop-session.html

Back when I had to kill RDP sessions, I loaded the Remoted Desktop
Services Manager as an admin (I think that was "mstsc /admin"), selected
the console at the remote host, and disconnect the session(s) to it.

On 27/08/2021 09:49, VanguardLH wrote:
> Fokke Nauta <usenet@solfon.nl> wrote:
>
>> We have quite some pc's in our local network. All of them are Windows
>> 10 Pro x64. From my pc I created RDP connections to the other pc's.
>> With 2 of them it works fine. With 2 other pc's I get the message:
>> "You have been disconnected because another connection was made to
>> the remote computer." And then the connection breaks. What can be
>> wrong?
>
> As I recall, you get just 2 concurrent RDP connections. With Terminal
> Server, you get more. If a user does not logoff, their session remains
> active, and counts against the quota of max concurrent sessions. A
> session could freeze, the user closes the window(s) and leaves, but the
> session is still active. You get a lot of users that just leave at the
> end of the workday instead of logging out of their RD session.

Thanks. Both pc's where it does not work, are automatically logged in
after starting up. So that's the reason.

> It's been many years (probably a decade) since I last used RDP. There
> was some admin-level tool you used to kill the still-alive sessions.

I haven't been using RDP for a long time either. I used VNC Viewer for a
long time. Recently, after a reset of my router, it does not work
anymore and I couldn't find what was the cause. So I went back to RDP.
I can start with RDPWrap or find another program to achieve remote control.

> https://smallbusiness.chron.com/kill-remote-desktop-sessions-55424.html
> https://www.msnoob.com/how-to-remotely-force-kill-a-remote-desktop-session.html

I think neither of the links above are a proper solution. I'll have to
look for another way.

>
> Back when I had to kill RDP sessions, I loaded the Remoted Desktop
> Services Manager as an admin (I think that was "mstsc /admin"), selected
> the console at the remote host, and disconnect the session(s) to it.
>

This is too much of a hassle.
I really have to look for a different solution.
Thanks anyway.

Fokke

On 8/26/21 11:25 PM, Fokke Nauta wrote:
> Hi all,
>
> We have quite some pc's in our local network. All of them are Windows 10
> Pro x64. From my pc I created RDP connections to the other pc's. With 2
> of them it works fine. With 2 other pc's I get the message: "You have
> been disconnected because another connection was made to the remote
> computer." And then the connection breaks.
> What can be wrong?
>
> Thanks in advance.
>
> Fokke Nauta
>

Hi Fokke,

I see what I think is happening to you a lot.
Maybe not.

What I see is when someone sits down at the remote
server and logs in and kicks you off. Then
comedy ensues: the local user remotes back in
and kick the guy off at the remote end and back
and forth, neither realizing what is occurring.
It only ends when one get frustrated or until
one calls the other on the phone and they negotiate
things. Or they call me.

The same thing will happen if two clients are
trying to log into the same desktop server.
Both will keep kicking each other off.

Desktop RDP server IS NOT MULTIUSER. Only Windows
Server RDP is multiuser. (Linux xrdp server
is multiuser and does not care if you are
configured as a server, a desktop, or both.)

RDP server from a desktop can only handle one
connection at a time. RDP client is suppose
(watch the weasel word) to handle multiple
connections to multiple servers.

As a test fall back, you can always install
wfreerdp for the client side:

https://cloudbase.it/freerdp-for-windows-nightly-builds/

Here are the command line options:

https://github.com/FreeRDP/FreeRDP/wiki/CommandLineInterface

-T

On 8/27/21 12:49 AM, VanguardLH wrote:
> Back when I had to kill RDP sessions, I loaded the Remoted Desktop
> Services Manager

Back when I was administering RDP for Windows servers,
the admin tool pissed me off to no end. They were
crash city, especially thre sharing utility where yo could see what the
user was seeing. NEVER, NEVER, worked right.
And you had to reboot to fix them -- pissing off all
the folks using the server who took it out on me.

For the last ten years or so, I have been removed
server Windows Servers (big "S") and just did file sharing
from a desktop. And most small business programs that serve
will work off a desktop. The increase in reliability
and cost savings to the customer is astronomical.
(If they let me, I configure their desktop with RAID 1.)
Windows Server is such a piece of ....

There is a few guys around these parts that will
put an exchange server (speaking of pieces of s***)
in your bathtub if you are not careful. Put two
of these guys on g-suite. YUGE difference in
reliability and cost.

On 8/26/21 11:25 PM, Fokke Nauta wrote:
> Hi all,
>
> We have quite some pc's in our local network. All of them are Windows 10
> Pro x64. From my pc I created RDP connections to the other pc's. With 2
> of them it works fine. With 2 other pc's I get the message: "You have
> been disconnected because another connection was made to the remote
> computer." And then the connection breaks.
> What can be wrong?
>
> Thanks in advance.
>
> Fokke Nauta
>

Hi Fokke,

Are you doing this in the same local area network?
Or are you logging into these computers from a
Wide Area Connection (the Internet).

If a wide area network, there is a tweak you
have to do on your clients.

-T

On 27/08/2021 23:24, T wrote:
> On 8/26/21 11:25 PM, Fokke Nauta wrote:
>> Hi all,
>>
>> We have quite some pc's in our local network. All of them are Windows
>> 10 Pro x64. From my pc I created RDP connections to the other pc's.
>> With 2 of them it works fine. With 2 other pc's I get the message:
>> "You have been disconnected because another connection was made to the
>> remote computer." And then the connection breaks.
>> What can be wrong?
>>
>> Thanks in advance.
>>
>> Fokke Nauta
>>
>
> Hi Fokke,
>
> Are you doing this in the same local area network?
> Or are you logging into these computers from a
> Wide Area Connection (the Internet).
>
> If a wide area network, there is a tweak you
> have to do on your clients.
>
> -T

Hi,

Yes, it's all in a local network: 192.168.1.xxx.

I have been using RealVCN for these remote operations for a long time,
but since a reset of my router this does not work anymore. So that's why
I went back to RDP.

Fokke

On 27/08/2021 22:44, T wrote:
> On 8/26/21 11:25 PM, Fokke Nauta wrote:
>> Hi all,
>>
>> We have quite some pc's in our local network. All of them are Windows
>> 10 Pro x64. From my pc I created RDP connections to the other pc's.
>> With 2 of them it works fine. With 2 other pc's I get the message:
>> "You have been disconnected because another connection was made to the
>> remote computer." And then the connection breaks.
>> What can be wrong?
>>
>> Thanks in advance.
>>
>> Fokke Nauta
>>
>
> Hi Fokke,
>
> I see what I think is happening to you a lot.
> Maybe not.
>
> What I see is when someone sits down at the remote
> server and logs in and kicks you off.  Then
> comedy ensues: the local user remotes back in
> and kick the guy off at the remote end and back
> and forth, neither realizing what is occurring.
> It only ends when one get frustrated or until
> one calls the other on the phone and they negotiate
> things.  Or they call me.
>
> The same thing will happen if two clients are
> trying to log into the same desktop server.
> Both will keep kicking each other off.
>
> Desktop RDP server IS NOT MULTIUSER.  Only Windows
> Server RDP is multiuser.  (Linux xrdp server
> is multiuser and does not care if you are
> configured as a server, a desktop, or both.)
>
> RDP server from a desktop can only handle one
> connection at a time.   RDP client is suppose
> (watch the weasel word) to handle multiple
> connections to multiple servers.
>
> As a test fall back, you can always install
> wfreerdp for the client side:
>
> https://cloudbase.it/freerdp-for-windows-nightly-builds/
>
> Here are the command line options:
>
> https://github.com/FreeRDP/FreeRDP/wiki/CommandLineInterface
>
> -T

Thanks!

One of the reasons may be that some pc's have been logged in already.
They have an auto login when they boot up.

Fokke