Will Renkel wrote:
I have 2 windows 7 puters. I would like to telnet and ftp
between them. I can login to each other but cant get a usable
shell - ksh is choice. I can start it but it does not stay up -
executes the login stuff like .bashrc and ,profile, but then
exits. I am looking for a setup similar to what you get when you
telnet to a unix system. Any ides? All help appreciated.


The client is a little easier to deal with.

https://social.technet.microsoft.com...et-client.aspx

The server side (telnetd) is not. While this subsystem existed
in the Win2K era, it probably isn't around today (Windows Services for UNIX???).

https://technet.microsoft.com/en-us/.../bb463201.aspx

Interix Telnetd

Login shell:

All users login to the Interix shell /bin/ksh.

https://en.wikipedia.org/wiki/Windows_Services_for_UNIX

https://docs.microsoft.com/en-us/pre...771470(v=ws.11)

Unbelievably, the download still works. I thought for
sure this idea was dead. Now, you'll have to find out
whether they included a telnetd, or whether the package
is mainly candy floss.

http://www.microsoft.com/en-us/downl...s.aspx?id=2391

OK, I saw an "in.telnetd" in there. Which means you can test it.

Back up your C: first, test out the kit. If not
happy, restore from backup.

The inetd server should dispatch in.telnetd when
a telnet program comes calling. This is Unix stuff
from like, 30 years ago. Even your average Linux
distro doesn't offer this now, because everything
(your username and password) all travel in plaintext.
This protocol should not be port forwarded through
your router. You should not telnet into the Windows
machine from Starbucks, for best security. Everyone in
Starbucks will know your password if you do that :-/
(Never assume a public Wifi is immune to scraping.)
Anything you do in public, should use good crypto.
Stelnet, sshd, openssh or whatever. Don't expect to find
good crypto support, in those packages Microsoft
has kindly provided for historical reasons.

Finding the client side, is always going to be easy.

https://en.wikipedia.org/wiki/PuTTY

It's the server bits that aren't going to be quite
as easy. Especially modern server bits with the
necessary crypto. So while PuTTY may have some
support for more secure login, there might not
be a server side piece for Windows to go with it.
You might be able to go from Windows PuTTY to
Linux ssh of some sort.

Paul