(no subject)
Jan. 21st, 2009 10:14 am![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
theweaselkingWhy the hell is "telnet" not included in the default load of programs in Server 2008?
Not "telnet server", not "receiving incoming telnet sessions", I mean the telnet CLIENT.
Not "telnet server", not "receiving incoming telnet sessions", I mean the telnet CLIENT.
(no subject)
Date: 2009-01-21 03:18 pm (UTC)Contempt for society.
(no subject)
Date: 2009-01-21 03:43 pm (UTC)(no subject)
Date: 2009-01-21 03:50 pm (UTC)(no subject)
Date: 2009-01-21 04:01 pm (UTC)(no subject)
Date: 2009-01-21 04:03 pm (UTC)Bonus: You can *install* the telnet client, manually. From the "server features" menu.
(no subject)
Date: 2009-01-21 04:03 pm (UTC)(no subject)
Date: 2009-01-21 04:14 pm (UTC)(no subject)
Date: 2009-01-21 04:16 pm (UTC)Which doesn't mean it's not foolish of them, just that I can understand their foolishness.
(no subject)
Date: 2009-01-21 04:30 pm (UTC)(no subject)
Date: 2009-01-21 04:34 pm (UTC)(no subject)
Date: 2009-01-21 04:35 pm (UTC)(no subject)
Date: 2009-01-21 04:38 pm (UTC)(no subject)
Date: 2009-01-21 04:39 pm (UTC)(no subject)
Date: 2009-01-21 04:45 pm (UTC)(no subject)
Date: 2009-01-21 04:46 pm (UTC)(no subject)
Date: 2009-01-21 05:14 pm (UTC)(no subject)
Date: 2009-01-21 05:34 pm (UTC)(no subject)
Date: 2009-01-21 05:34 pm (UTC)SSH is prettymuch the defacto replacement, which is basically a telnet session with the encryption goodies (i.e. blowfish, DES/3DES, Arcfour, yadda yadda)
I guess this is their way of "encouraging" migration to more secure tools. Doesn't matter anyway since puTTY is sooooo much cooler.
Kinda sad though, considering I cut my teeth on good ole telnet.
(no subject)
Date: 2009-01-21 05:35 pm (UTC)(no subject)
Date: 2009-01-21 05:38 pm (UTC)Grrr. Easy to enable, but the fact that I have to do it annoys me.
(no subject)
Date: 2009-01-21 05:40 pm (UTC)Now. About the soon to be deceased...
(no subject)
Date: 2009-01-21 05:41 pm (UTC)(no subject)
Date: 2009-01-21 05:57 pm (UTC)(no subject)
Date: 2009-01-21 06:13 pm (UTC)http://technet.microsoft.com/en-us/library/bb490994.aspx
- James -
(no subject)
Date: 2009-01-21 06:16 pm (UTC)(no subject)
Date: 2009-01-21 06:20 pm (UTC)(no subject)
Date: 2009-01-21 06:21 pm (UTC)(no subject)
Date: 2009-01-21 06:55 pm (UTC)Here is a list of alternatives, if you're still interested, to get runas functionality from within a script.
http://www.commandline.co.uk/sanur/
- James -
(no subject)
Date: 2009-01-21 06:55 pm (UTC)Oh, and when Cisco releases an IOS update for all their routers still in use with SSH support, I'll consider getting rid of telnet, but even then, I've still got networking gear that either requires a serial console or only speaks telnet.
(no subject)
Date: 2009-01-21 07:01 pm (UTC)(no subject)
Date: 2009-01-21 07:06 pm (UTC)Or, in the case that prompted this specific rant today, how else am I supposed to determine if the rsync server really IS picking up the phone on 873 the way it says it is?
(It wasn't. This was most of the problem - but I figured "telnet localhost 873" would be a perfectly sensible way to find out!)
(no subject)
Date: 2009-01-21 07:07 pm (UTC)Could install teraterm, too.
But the problem with those is that they are *extra applications*, and telnet is *core OS functionality, dammit*.
(no subject)
Date: 2009-01-21 07:38 pm (UTC)- James -
(no subject)
Date: 2009-01-21 07:41 pm (UTC)Well, not really or the OS wouldn't function with it missing ;) It's definitely a utility fairly common to basic testing though, and I use it in exactly the same way when testing a mail server. Confirming the open port, banner check, sending mail via that telnet session so I can see the errors without having to install/use wireshark.
Off the original topic, but on topic for the segue, netcat/nc is a damned handy tool that allows you to test both tcp and udp connection - worth playing with if you haven't already.
(no subject)
Date: 2009-01-21 08:44 pm (UTC)Eventually I'll figure out how to do (d) with ssh, maybe. As for (c), once upon a time there were several wee informational services connected to port 23 on machines around the net (also on port 79, 'finger') where you didn't enter a password and login; just telnetted to the port and got a message (such as a weather forecast), or a prompt for some database query. I don't know whether any of those are still around -- they may have all been replaced by HTTP-based versions by now.
Note that troubleshooting by using telnet to connect to the mail or web port is often useful when you're telnetting back to the same box your telnetting from.
Once in a whie I even find it useful o telnet to 127.0.0.1 and log in, when I'm getting some sort of weirdness from environment variables using su or just invoking a subshell. I'm not all that worried about password sniffing when telnetting to the loopback address, especially when I'm the only user on the box. Though admittedly that case doesn't come up very often in Windows.
For that matter, I've used telnet to troubleshoot odd routing and ipconfig glitches. Using telnet instead of ssh removes one layer of potential glitch-source during low-level troubleshooting.
I find telnet a very useful tool to have around, even in the age of ssh.
(no subject)
Date: 2009-01-21 08:48 pm (UTC)It's just... an extra application. Yick.
(no subject)
Date: 2009-01-21 09:10 pm (UTC)(no subject)
Date: 2009-01-21 09:12 pm (UTC)(no subject)
Date: 2009-01-21 09:18 pm (UTC)(no subject)
Date: 2009-01-21 11:51 pm (UTC)Fair enough but I really didn't want to delve into the sordid and incestuous history of ARPnet and friends. Such details would be for "How Networks Give Us Headaches 102". I'm trying to keep things to an elementary level for our current class of "Why Networks Suck 101".
(no subject)
Date: 2009-01-21 11:56 pm (UTC)(no subject)
Date: 2009-01-22 01:08 am (UTC)