Saturday, January 11, 2014

Remote Terminal 1.8.1 now available

This update contains a bugfix that was introduced in version 1.8.0.

Crash when switching away from the App fixed
The following steps always caused the app to crash: navigate to the terminal page via Quick Connect or via selecting an existing open connection in the top AppBar on the start/favorites page, then switch to another App.
Sorry for any problems this may have caused!
at
Labels:

6 comments:

  1. UnknownFebruary 18, 2014 at 6:40 PM

    Hello,
    I use both cygwin and Remote Terminal to ssh from my Windows 8 laptop. My Internet connection is sometimes lost for some seconds. With cygwin, it simply lags when that happens but Remote Terminal close the ssh tunnel and says that the existing connection was closed by the remote host. If you could do something to have a behavior similar to the one of cygwin it would be very useful to me.
    Thanks!

    ReplyDelete
  2. AnonymousAugust 15, 2014 at 3:08 PM

    Hi,

    I’m running a local sshd server on my PC, which I can connect to using desktop SSH clients. However, if I try to connect from Remote Terminal, it times out and gives error 0x8007274C. I’m connecting to the loopback interface on the local machine, so a network problem isn’t possible, and desktop SSH clients work. Any idea what the problem might be?

    Thanks!

    ReplyDelete
    Replies
    1. Stefan PodskubkaAugust 17, 2014 at 1:04 PM

      Hello!

      I know exactly what the problem is:

      Windows Store Apps are running in a very restricted sandbox environment and cannot connect to or accept connections from localhost, except from the same app.
      The reason for that is that Windows Store Apps should be allowed access to the system only through the APIs available to them. The localhost sandboxing is a security measure to prevent apps from accessing the system in any other (unsecure) way e.g. by communicating with any other software running locally that gives the Windows Store App access to the filesystem etc.

      As far as I remember, there should be a registry hack to circumvent this issue, which you may use at your own risk.

      Best regards
      Stefan

      Delete
  3. AnonymousDecember 29, 2014 at 11:41 AM

    Hey Stefan,

    great terminal app, I love and use it since half a year now. :) However, there is a small problem: I can't use the @ character in vim, as it's interpreted as escape. It's possible in other terminals (PuTTy for example), but not in the Remote Terminal app. Do you have any idea how to solve that?

    Best regards,
    Felix

    ReplyDelete
  4. AnonymousJune 4, 2015 at 11:24 PM

    I am trying to connect my laptop to a Cisco 1800 router direct through the Ethernet cable and have not been able to do so

    ReplyDelete
  5. UnknownAugust 26, 2015 at 3:27 AM

    The best APP for my environment. no more cygwin :-)

    But I miss SendKeepAlive. Often lose the connection and lose work in progress.

    Is the roadmap to include this feature?

    ReplyDelete

Subscribe to: Post Comments (Atom)