Help with a simple terminal problem

From:
Date: 08/16/02 

Date: 15 Aug 2002 19:52:41 -0700

I just started using OpenSSH. I'm using both PuTTY and the commercial
SSH as clients. In either case, I'm talking to a Windows 2000 server.
I have no problem openning a command prompt session, but then, when I
try to do things like Ctrl-C (for killing a DOS command) or up arrow
(for repeating the last DOS command), the PuTTY or commercial SSH
client doesn't send the expected key to the Win2K server. I haven't
found anything in the configuration docs to fix this. Can anyone help?
Thanks.

Relevant Pages

  • Re: Mitigate FTP
    ... if you use ssh (server) with scp (in clients) using cryptographic key ... Security Trends Report from Cenzic ...
    (Pen-Test)
  • Re: [SLE] nfs server specification
    ... On Wed, 2004-12-29 at 18:26, steve wrote: ... > Both the nfs and ssh methods work but are too slow. ... LTSP has some docs on their page about server requirements. ... I have run 12 clients on a similar ...
    (SuSE)
  • Re: X.509 and ssh
    ... >> Is there any effort going on in standardizing the use of X.509 in ... PG> SSH was specifically designed to not require X.509 (which is one ... distributing them every time a server is added, removed, or rekeyed ... and many clients are simply not available for updating ...
    (comp.security.ssh)
  • RE: Send xterm to remote workstation with OpenSSH
    ... Is this Putty on Windows? ... When you SSH in, it should automatically appropriately set your DISPLAY ... I've tried a variety of X-11 Server, ...
    (SSH)
  • Re: X.509 and ssh
    ... >> Is there any effort going on in standardizing the use of X.509 in ... PG> SSH was specifically designed to not require X.509 (which is one ... distributing them every time a server is added, removed, or rekeyed ... and many clients are simply not available for updating ...
    (comp.security.ssh)