3 ms·
> You can install telnet via the add features option from the control panel. Who wants to have such insecure program available anyway? There's no security prob
by nandhp 11y ago
> You can install telnet via the add features option from the control panel. Who wants to have such insecure program available anyway?
There's no security problem with the telnet client, unless you're using it to log into remote hosts without encryption. But OP, and presumably many other people (like me), use telnet as a simple TCP client for troubleshooting. On Linux, one can use netcat (though I never remember to type nc, and always try telnet first), but of course Windows doesn't come with netcat.
- pjmlp 11y agoThere are better GUI tools for such purposes.
- cturner 11y agoIt's important to have something to be installed by default, and not require admin privileges. This is what you need need if you're supporting people over the phone. That is - something dependable that you can use to check that they don't have TCP obstacles for whatever they're trying to do. Telnet-for-Windows was a terrible interface for this purpose (if it succeeds, you get left at a meaningless command prompt) but it was possible to talk people through that, and that was enough. (You can't trust the proxy configuration of their web browsers.)
- pjmlp 11y agoBack when I was doing UNIX (big boys UNIX, not GNU/Linux) I remember there were lots of tools that weren't available on those systems. And even the common ones lacked lots of useful options from the GNU land. All comparisons of GNU/Linux distributions with Windows, have the fallacy of comparing a distributions with an OS targeted originally for consumers. Normal users just don't go telnet into their local networks. Server editions usually have the proper services in place.