Hi Reinier, What you have in the configuration file is essentially correct - the "accept" parameter defines which port and IP to bind to, and the "connect" parameter is the IP and port that you have bound what ever service it is that you are securing with stunnel. More information on those two options is here: http://stunnel.org/static/stunnel.html (search case-insensitive for "Service-level options") When you configure IIS, make sure to also define it's IP and socket that it is binding to. Cheers, Mit Rowe On Mon, Jun 27, 2011 at 8:21 AM, R. van der Gugten <info@rgit.eu> wrote:
Hi,****
** **
Is it possible to run STunnel on my server to lisen to IP1 on port 443****
And to have IIS listen to IP2 on port 443? ****
** **
Should I make changes in the config file? ****
** **
Thanks,****
** **
Reinier****
** **
** **
** **
Current server stunnel file:****
** **
cert = stunnel.pem****
key = stunnel.pem****
** **
; Some performance tunings****
socket = l:TCP_NODELAY=1****
socket = r:TCP_NODELAY=1****
** **
; Authentication stuff****
verify = 2****
CAfile = certs.pem****
** **
; Use it for client mode****
client = no****
** **
; Service-level configuration****
[SQLServer]****
accept = <<IP1:xxx.xxx.xxx.xxx>>:443****
connect = 127.0.0.1:31433****
** **
_______________________________________________ stunnel-users mailing list stunnel-users@stunnel.org http://stunnel.mirt.net/mailman/listinfo/stunnel-users
-- Will 'Mit' Rowe Stagename* *1-866-326-3098 mit@stagename.com <josh@stagename.com> www.stagename.com Twitter: @stagename *The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. If you received this transmission in error, please contact the sender and delete all material contained herein from your computer.*