No, if TS is installed, you shouldn't have to do anything else
than giving the users the proper permissions to use it (by making
them members of the build-in Remote Desktop Users group and in the
properties of their account). But a permission problem would not
give you a "server not available" error.

Can you post the *exact* text of the error message?
Have you checked the EventLog on the TS?
Have you verified that the TS is listening on port 3389, with the
netstat -an command?
Have you checked in TS Administration if there is a listener
session, and that it is not "down"?

Although this will not fix it, have you tried to install the
newest rdp 5.2 client? Apart from everthing else, it sometimes
gives better error messages. Download from

http://www.microsoft.com/downloads/details.aspx?FamilyID=a8255ffc-
4b4a-40e7-a706-cde7e9b57e79&DisplayLang=en

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---