Member Avatar for Benita_1

I am trying to remotely access a computer running UNIX/Linux from another computer by using telnet. I was able to activated the telnet in windows but I cant find the right server address and (port) to open the connection between windows and unix. Do you have any suggestion for me?

  • 3 Contributors
  • 3 Replies
  • 249 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by Benita_1

Dani AI

Generated

Useful follow-up: since got a working remote shell and others pointed toward using a secure remote-login protocol, the notes below cover how to find the correct server address, common causes of failed connections, and practical hardening and troubleshooting steps not discussed earlier.

On the Linux/UNIX host, identify which IP to use (local vs public) and confirm the service is reachable. Common commands:

hostname -I
ip addr show
ifconfig -a

Local addresses shown by those commands are suitable for same-LAN tests. For access from outside the LAN, the router’s public address (or a dynamic‑DNS name) plus a router rule forwarding the remote‑login service to the server’s local address is required; set a DHCP reservation or static local IP on the server so the router rule remains valid.

When a connection fails, distinguish “refused” (service not listening) from “timed out” (network/firewall/NAT). Useful checks on the server:

systemctl status sshd     # or service ssh status
ss -tlnp | grep sshd      # or netstat -tlnp
sudo ufw status           # or sudo iptables -L -n -v or sudo firewall-cmd --list-all
journalctl -u sshd -n 200  # or check /var/log/auth.log

Logs and listening-socket output quickly show whether the daemon is running, which address it’s bound to, and whether a firewall is blocking access.

Hardening and reliability notes not covered above: prefer key‑based authentication and restrict/disable password and direct administrative account logins in the server configuration; use AllowUsers/AllowGroups or firewall rules to limit source IPs; deploy automated blocking (fail2ban) for repeated failures; keep the server packages updated; consider multi‑factor or hardware-key authentication for higher security. For Windows clients, modern releases include a native OpenSSH client usable from PowerShell or Windows Terminal, which is convenient for same‑LAN testing before making router changes.

Recommended Answers

All 3 Replies

Member Avatar for rubberman

Telnet is insecure. Most servers have disabled it so you probably cannot access them with it. Try ssh instead.

Member Avatar for CimmerianX

To expand... for windows, get a free program called putty.exe. This lets you create an ssh session. You need the IP address or dns name of the server you want to hit. SSH usually runs on port 22 by default.

Don't use telnet, passwords are sent in cleartext.

Member Avatar for Benita_1

Thank you every one. It did work using ssh and port 22. I was using telnet and automatic runs port 23 by default. System did not recognized it. Thanks guys again,I got it running now

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.