Remote Desktop Gateway - users getting Http transport: IN channel could not find a corresponding OUT channel

Question

Hi Team,

Need some help here on Remote Desktop Gateway.

I only have one gateway configured which has been working fine. All of a sudden, users are getting the below error. We dont have any load balancing configured.

Http transport: IN channel could not find a corresponding OUT channel

Thanks in advance.

Daham

Answer 1

Hello @manodha daham dias ，

Thanks for your query.

1.What's your RDS environment?
2.This issue seems to be caused by 3rd party load balancing.Pls try to Create a Remote Desktop Gateway Server Farm with Network Load Balancing rather than non-Microsoft load-balancing devices to see whether it works.
Create a Remote Desktop Gateway Server Farm: http://technet.microsoft.com/en-us/library/cc732370.aspx
Http transport: IN channel could not find a corresponding OUT channel: https://social.technet.microsoft.com/Forums/zh-CN/5925c7d8-2b3f-49e6-b3fc-6a4a6a1f02cd/http-transport-in-channel-could-not-find-a-corresponding-out-channel?forum=winserverTS
3.Did you connect to the gateway with using a web browser? You would connect to using the gateway using MSTSC, or using a RDP file.
RDS 2012 – Configuring a RD Gateway Farm: https://ryanmangansitblog.com/2013/03/31/rds-2012-configuring-a-rd-gateway-farm/

Best regards,
Leila

---

If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

HI Leila,

Thank you for the response.

1. Just one RDG behind a Fortigate FW. Users use this gateway to RDP to other internal servers.

2.We do not use any load balancer. It was very strange to see this error since I was getting results about load balancer when I searched for the error. We only have one RDG hence, we do not use the server farm feature.

3. Users use RDP file to connect (not the web browser)
4. This error shows up only to a certain users. It seems to be from a specific pub ip subnet. But not sure what to do with troubleshooting.

Thanks for the help.

Daham

Answer 3

Hello @manodha daham dias ,

Thanks for your response.

1.When the issue occurred, whether the certain users failed to connect to the internal session host persistently through Rdgateway or not? If so, please try to shut down firewall temporarily on Win 10 client to check if the problem of remote desktop session host still existed?
When the issue occurred, try to disconnect the network on Win 10 client and reconnect, then check if you can remotely connect to the internal session host through Rdgateway?

2.Please run Network Monitor (or wireshark) separately on both the normal client & remote desktop gateway server and problematic client & remote desktop gateway server to compare the differences between the netmon log and GDgateway log of normal client and problematic client.
https://www.microsoft.com/en-us/download/details.aspx?id=4865
https://learn.microsoft.com/en-us/windows/client-management/troubleshoot-tcpip-netmon

Answer 4

Hello @manodha daham dias ,

How are things going there on this issue?
Please let me know if you would like further assistance.