From: Marco Atzeri <marco.atzeri@gmail.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Ssh
Date: Sun, 17 Jan 2021 19:11:37 +0100 [thread overview]
Message-ID: <d682400b-b3fe-10e6-6807-6d84f1edf8b1@gmail.com> (raw)
In-Reply-To: <CAEMWCRts5+OTXxgztq8s3yWZre-4ZfiixARYNGmE8a0nrD+y0A@mail.gmail.com>
please reply to mailing list, thanks
On 17.01.2021 18:30, Jim McNamara wrote:
>
>
> On Sun, Jan 17, 2021, 12:04 PM Marco Atzeri via Cygwin
> <cygwin@cygwin.com <mailto:cygwin@cygwin.com>> wrote:
>
> On 17.01.2021 17:26, Jim McNamara via Cygwin wrote:
> > Hi-
> >
> > If I am trying to ssh by local port forwarding from machine A to
> remote
> > host B, do I need cygserv or sshd running on A?
>
> No. You need sshd (ssh demon) on B
>
> >
> > B is the sshd server I want to connect to. A is the ssh client.
> >
> > If I test either vnc or ssh on linux virtual machine guest it
> connects no
> > problem. For some reason NAT is not working from A even though I
> port
> > forward on my NAT adapter on virtual box.
> >
> > Thanks,
> > Robo-loki
>
> use ssh in verbose mode to see more details
>
> -v Verbose mode. Causes ssh to print debugging messages
> about its
> progress. This is helpful in debugging connection,
> authentica‐tion, and configuration problems.
> Multiple -v options increase the verbosity.
> The maximum is 3.
> --
> Problem reports: https://cygwin.com/problems.html
> <https://cygwin.com/problems.html>
> FAQ: https://cygwin.com/faq/ <https://cygwin.com/faq/>
> Documentation: https://cygwin.com/docs.html
> <https://cygwin.com/docs.html>
> Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
> <https://cygwin.com/ml/#unsubscribe-simple>
>
>
> Hi Marco,
>
> I had it setup like you suggested.
>
> I will have to look at some other things.
>
> Thanks,
> Robo-loki
>
Regards
Marco
next prev parent reply other threads:[~2021-01-17 18:11 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-17 16:26 Ssh Jim McNamara
2021-01-17 17:03 ` Ssh Marco Atzeri
[not found] ` <CAEMWCRts5+OTXxgztq8s3yWZre-4ZfiixARYNGmE8a0nrD+y0A@mail.gmail.com>
2021-01-17 18:11 ` Marco Atzeri [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-26 19:54 ssh Jimmy Hayes
[not found] ` <75EA21FE420C864D895DE6E87383D6A157EB81@exchange1.meddatahc s.com>
2004-05-27 17:52 ` ssh Larry Hall
2004-05-06 17:34 ssh Clemson, Chris
2004-05-06 17:01 ssh Jimmy Hayes
2004-02-28 0:53 SSH Tim Ashman
2004-02-28 1:08 ` SSH Brian Dessent
2003-12-07 18:29 ssh Martin Gainty
2003-12-08 0:36 ` ssh Igor Pechtchanski
2003-11-20 23:19 ssh Ben Anderson
2003-06-27 9:42 ssh Julien VARLET
2003-06-30 4:30 ` ssh Karsten M. Self
2001-02-19 10:38 ssh Matt Presser
2000-09-28 21:02 ssh Guansong Zhang
2000-09-29 5:37 ` ssh Corinna Vinschen
1999-01-31 23:52 ssh Xiaomao Xiao
1997-09-10 21:15 SSH Sergey Okhapkin
1997-09-10 2:25 SSH Paul Haas
1997-09-12 1:24 ` SSH Andy Piper
1997-08-14 5:10 SSH Glenn Jones
1997-08-13 15:57 SSH dahms
1997-08-13 23:57 ` SSH Leonard Weincier
1997-08-14 6:41 ` SSH Andy Piper
1997-08-14 8:07 ` SSH Paul Prescod
1997-08-15 12:35 ` SSH Leonard Weincier
1997-08-12 9:18 SSH Leonard Weincier
1997-08-12 21:32 ` SSH Bilbo Baggins
1997-08-12 21:53 ` SSH Bilbo Baggins
1997-08-13 0:10 ` SSH Leonard Weincier
1997-08-13 7:25 ` SSH Dan Maynard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d682400b-b3fe-10e6-6807-6d84f1edf8b1@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).