Error 204: Terminal Server Client TCP Port error
When you try to connect to a Beta 2 Terminal Server using the TerminalServer Client, you may get a "Failure to connect: 204" error. The cause ofthis error is most likely that you are using a pre-Beta 2 version of theclient. A change was made in Terminal Server so that it listens for trafficon port 3389, rather than on port 1503, as in pre-Beta 2 versions.
You can verify that this is the cause of your connection problem bycapturing the network traffic with Network Monitor (included with TerminalServer) as you attempt to connect. After stopping the trace, the summaryview screen will show the client attempting to connect. You should see thesource port number (src:) and the destination port number (dst:3389) in thedescription field.
Uninstall any client versions prior to Beta 2, and install the new version.
If this is not the problem, the 204 error points to a TCP port problem. Itmeans that the initial socket connection between the Terminal Server andthe client could not be established. You might have a protocol problem onthe client computer, particularly with Windows for Workgroups 3.11 clients.Be sure you are using the TCP/IP-32B version from the Clients subdirectoryon the Terminal Server CD. For Windows 95 or Windows NT Clients, tryreinstalling the TCP/IP protocol. Third, you could have a protocol problemon the Terminal Server. Reboot the server and then, if this doesn't resolvethe problem, reinstall the TCP/IP protocol on the server.
Article ID: 186617 - Last Review: 06/22/2014 19:00:00 - Revision: 3.0