1

Experiencing a very weird RemoteApp issue. I will do my best to explain what is going on.

Environment:

  • There are two Active Directory Domains, both live on a seperate network, both share a router/firewall in a SonicWall. Will refer to as “new” and “old”.
  • There are some accounts defined in both Active Directory Domain, there is no domain trust.
  • There is full pathway for network traffic between each network through the SonicWall.
  • There is a pair of Server 2016 machines with the Remote Desktop Gateway Services and Connection Broker roles on the “new” domain, as well as a Server 2019 Remote Desktop Session Host. This server has published RemoteApps.

Issue:

  • A user, “user”, is unable to utilize the RemoteApps from the “old” network to the “new” network. They are able to use the RemoteApps externally over Remote Desktop Gateway Services, or from another network such as the “new” network.

Now here is the kicker, if I change the username from “user” to “user1”, authentication works. When I change the username back to “user”, it does not. I have re-created the account, and it does not work with the specific username. I have tried using public DNS servers on a workstation on the “old” network and it does not work. I have tested the RemoteApp through the Gateway Services Server as well as directly to the Session Host and neither work. Somehow the name is the issue, the name…

Any and all help is appreciated.

Thanks!

4 Spice ups
2

Does the name “user” exist in both ADs? How about “user1”?

3

The name does existing in both ADs, however I tested with another user, by creating an account for them in the “new” AD and did not experiencing the same issue.

4

You said unable to use… what error, exactly, is the user getting when it doesn’t work?

5

The only thing I can think of is the SonicWall causing the issue. We have LDAP enabled, as well as an SSO agent on the “new” AD. I tried to disable both, albeit at separate times, and experienced the same symptoms. I am going to test the wireless, which is again on another network and see if that works.

1 Spice up
6

“The logon attempt failed” very generic and non specific. It is like you are entering a wrong password. I can see in the logs on the Gateway Services server that the user is authenticating, but then it disconnects within seconds before any UDP traffic transmits.