Thanks MS Jim,
We are having what you refer to as slow/failing connections and this is happening for all users both ADMIN and NON-ADMINS. From the server logs, I see the following 3 successive errors:
The user "user@domain", on client computer "IP:Port1", has initiated an outbound connection. This connection may not be be authenticated yet.
The user "user@domain", on client computer "IP:Port2", has initiated an inbound connection. This connection may not be be authenticated yet.
The user "user@domain", on client computer "IP:Port2", has initiated an inbound connection. This connection may not be be authenticated yet.
...and then nothing. On the client side we get either:
----- Begin RemoteApp Disconnected Error
Remote Desktop can't connect to the remote computer for one of the following reasons:
1) Remote access to the server is not enabled
2) The remote comptuer is turned off
3) The remote computer is not available on the network
Make sure the remote computer is turned on and connected to the network, and that remote access is enabled.
----- End Error
OR
------Begin RemoteApp Disconnected Error
Your computer can't connect to the remote computer because of an error occurred on the remote computer that you want to connect to. Contact your network administrator for assistance.
------ End Error
Both of these error happen while other clients are actively connected and working.
After subsequent tries from the failed clients, the authorization policy requirements are met and the user will be able to login.
Do you have any advise on specific logs to look for as this is a pretty basic installation NOT farmed out across multiple serves, our GPOs haven't be modified from default, we're not using login scripts and our server load looks fine from resource monitor.
I'd really appreciate anything you can suggest to make this system more stable for our developers.
Thank you.