Why doesn't the Remote App launch on the first try?

Question

VPN

There is an organization A with a dedicated white static IP, a Mikrotik router, an internal subnet 192.168.0.0/24. The L2TP\IPSec VPN server is up on the router. There is a server running Windows Server 2019 on the network that has Remote App deployed and several apps published. On the local network, the Remote Apps work great - they start right away and work quickly. It is required to access these applications from another network, organization B. Organization B also has a white static IP, a Mikrotik router, an internal subnet of 192.168. 0.0/24 VPN connection. Everything is set up correctly, everything works as intended, with the exception of one nuance: launching a remote application from organization B does not work the first time, i.e. launch the Remote App shortcut, a connection is established ("Setting up a remote session") and everything disappears - neither the application, nor the connection icon in the client system tray. From the second or third time it starts up and works as if nothing had happened, without any problems. Question: what could be the reason for such behavior? So far, I only have an assumption that because of the Internet channel of organization A, which is only 5Mbps, and there is no possibility of increasing the width. On the other hand, for RDP, 5Mbit should, it seems, be enough. Or not? Maybe somewhere there is a timeout setting by which the client stops initiating a connection if the connection is not immediately established, or something like that? From the second or third time it starts up and works as if nothing had happened, without any problems. Question: what could be the reason for such behavior? So far, I only have an assumption that because of the Internet channel of organization A, which is only 5Mbps, and there is no possibility of increasing the width. On the other hand, for RDP, 5Mbit should, it seems, be enough. Or not? Maybe somewhere there is a timeout setting by which the client stops initiating a connection if the connection is not immediately established, or something like that? From the second or third time it starts up and works as if nothing had happened, without any problems. Question: what could be the reason for such behavior? So far, I only have an assumption that because of the Internet channel of organization A, which is only 5Mbps, and there is no possibility of increasing the width. On the other hand, for RDP, 5Mbit should, it seems, be enough. Or not? Maybe somewhere there is a timeout setting by which the client stops initiating a connection if the connection is not immediately established, or something like that?

Answer 1

Packet loss. Channel width also plays a role. She's not only under vpn, but also inet.