|Using telnet to troubleshoot
|6/2/14 5:12 PM
|Last modified on:
|12/13/18 12:58 PM
telnet localhost 52110This status server allows the following functions:
When using the service-based client, a process continuously runs in the background that is responsible for two things:
This status server does not allow any modifications. Use the following command to connect to this server.
telnet localhost 51110
telnet localhost 53110
Newer operating systems do not come with a Telnet Client. This is because a Telnet Client typically connects to a Telnet Server, which is considered insecure and replaced by SSH. Telnet Client, by itself, has other uses besides connecting to a Telnet server. In technical terms, a Telnet Client is a straightforward TCP/IP client that can connect to any text-based TCP/IP server, such as HTTP, SMTP, IMAP, POP3, and many others. As a result, it can be used as an excellent tool for troubleshooting and communicating with any TCP/IP server.
Luckily, you have several options:
Trust us. Using a Telnet Client for troubleshooting a TCP/IP server (other than Telnet Server) does not pose any security risks. Refer to this page for details.
To enable Telnet Client on Windows, go to Add Remove Windows Features and enable it.
Netcat is another good simple TCP/IP client that can connect to any text-based TCP/IP server. Many Mac and Linux machines come with this utility built-in. Here is an example of connecting to a Syncrify Client using Netcat.
nc localhost 53110
Last parameter is the port. Change that value according to the description above to connect to Syncrify Server or the background service.
Syncrify Client has a built-in utility, similar to Telnet Client and Netcat. Use the following syntax to connect.
java -jar SyncrifyClient.jar -talkToService -tPort 51110
Note that the name for
SyncrifyClient.jar is often different. For example, this file is called
clientRT.jar if you look
Data Folder/reqLibs directory.
Do you have a helpful tip related to this document that you'd like to share with other users?