From: "L. V. Lammert" <lvl@omnitec.net>
To: Andrew Schulman <schulman.andrew@epamail.epa.gov>
Cc: cygwin@cygwin.com
Subject: Re: Troubleshooting AutoSSH
Date: Fri, 12 Jul 2013 19:15:00 -0000 [thread overview]
Message-ID: <Pine.BSO.4.53.1307121338440.32610@Mail.omnitec.net> (raw)
In-Reply-To: <f7f0u8hgn9uc1r03vf8lctj3v0io4b10l8@4ax.com>
On Fri, 12 Jul 2013, Andrew Schulman wrote:
> Hi Lee. Okay, that does seem to narrow it down.
>
> You're right that autossh doesn't have any ipv4 options. It hasn't been
> updated in a few years, and I think it's just not ipv6-aware yet.
>
Looks like it may not be autossh - if I start sshd with a default config,
it works [ssh localhost], .. if I try ssh -4 localhost, nada!
It looks like *sshd* can only bind IPV6 - forcing it to bind IPV4 only
prevents startup.
Windows Firewall is not enabled, .. Trend Micro is installed, but I can
find no evidence it is more than virus scanner. The service user
(cyg_server) is a local Administrator, .. tried Administrator credentials,
but the service still cannot start if I try to force IPV4.
*User* level IPV4 connections (e.g. Firefox) are working, as I just did a
Cygwin reinstall to verify the situation.
Any thought on what might be blocking sshd from binding to the IPV4 stack?
FYI, this is the first machine we have used as a Domain Member, previously
we have only been running standalone; cyg_server is a local user, as is
our admin user.
TIA!!
Lee
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2013-07-12 18:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 0:52 L. V. Lammert
2013-07-12 7:37 ` Andrew Schulman
2013-07-12 16:47 ` L. V. Lammert
2013-07-12 18:48 ` Andrew Schulman
2013-07-12 19:15 ` L. V. Lammert [this message]
2013-07-12 19:18 ` Andrew Schulman
2013-07-12 21:19 ` L. V. Lammert
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=Pine.BSO.4.53.1307121338440.32610@Mail.omnitec.net \
--to=lvl@omnitec.net \
--cc=cygwin@cygwin.com \
--cc=schulman.andrew@epamail.epa.gov \
/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).