From: Ross Boylan <ross@biostat.ucsf.edu>
To: cygwin@cygwin.com
Subject: Re: cygwin port forwarding [working]
Date: Fri, 29 Jun 2012 01:08:00 -0000 [thread overview]
Message-ID: <4FED0028.7070006@biostat.ucsf.edu> (raw)
In-Reply-To: <1340468946.24539.26.camel@corn.betterworld.us>
I have some updates and successes.
First, I do see the forwarded ports with netstat -aon in a windows
command prompt:
TCP [::1]:2525 [::]:0 LISTENING 388
TCP [::1]:9933 [::]:0 LISTENING 388
I may have missed them because I didn't look at the ::1 addresses or
because the destination host and port is oddly blank.
From within a cygwin terminal I did
openssl s_client -connect localhost:9933
which showed me the certificate of the mail server I was trying to reach.
Finally, when I switched thunderbird to use localhost at port 9933 (with
connection security set to SSL/TLS) it did make contact. As René
indicated, T-bird complained about the certificate (which has also
expired). Then I ran into what seems like a T-bird bug: every time I
hit "accept certificate" it brought the same dialogue asking for
confirmation up. Eventually I closed it by hitting the red x on the
window (though it took a couple of tries). It seems to be working.
Even if it's not, it seems clear the port forwarding is working.
I'm not sure why it didn't work the first time.
Thanks to René, Andrey, and Karl for their help.
Ross
--
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
prev parent reply other threads:[~2012-06-29 1:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-23 16:29 cygwin port forwarding Ross Boylan
2012-06-23 17:43 ` René Berber
2012-06-24 0:20 ` Andrey Repin
2012-06-24 2:26 ` Karl M
2012-06-24 18:33 ` Ross Boylan
2012-06-24 21:42 ` René Berber
2012-06-25 9:50 ` Andrey Repin
2012-06-29 1:08 ` Ross Boylan [this message]
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=4FED0028.7070006@biostat.ucsf.edu \
--to=ross@biostat.ucsf.edu \
--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).