We have two terminal servers setup on our new MAG and we keep getting the following errror:
The client could not connect to the remote computer. Remote connections might not be enabled or the computer might be too busy to accept new connections. It is also possible that network problems are preventing your connection.
Multiple machines and browsers all come back with the same error. The MAG sits behind a Cisco ASA 5510 firewall. Is it a port issue on 3389 or a settings issue on the MAG?
Strictly based on what you are saying, sounds like something on the backend (either the FW or the server). Some things you can do to rule out the MAG:
1) Make sure you have an ACL set at Users>Resource Policies>Terminal Services that allows access to the server(s) you are connecting to
2) Make sure you are only setting the server port on the bookmark
3) Make sure the MAG can reach the server through ping/tracert (if enabled on your network) at Maintenance>Troubleshooting>Tools>Commands
4) Take a TCP dump on the internal port, started before a user connects and stopped after the error is seen, and filter for port 3389 or the IP of the server you are connecting against
#1 did it - didn't have the proper group associated with it. Good catch - thanks Zany!