[stunnel-users] Error message vista

[delaage.pierre at free.fr]

Quoting Reinier van der Gugten <info at rgit.eu>:
I suggest that you stop your firewall & antivirus and then retry.
Other possibility : you have another instance of a program listening to that
same port.
In a windows command line just type : netstat -ab to see a full list of running
programs and what port they listen to.
This is a windows socket layer error, not a stunnel one.

Best regards,
Pierre Delaage

> Hi,
>
> I use Stunnel for some of my customers. However I tried it myself (after a
> while, and after a reinstall of windows) and I get this error. Can anyone
> tell me how to get it to work again?
> I get the same error when I run it as administrator, or when I change the
> port from 443 to 4430.
>
> 2009.02.04 13:54:04 LOG7[2828:5668]: Snagged 64 random bytes from C:/.rnd
> 2009.02.04 13:54:04 LOG7[2828:5668]: Wrote 1024 new random bytes to C:/.rnd
> 2009.02.04 13:54:04 LOG7[2828:5668]: RAND_status claims sufficient entropy
> for the PRNG
> 2009.02.04 13:54:04 LOG7[2828:5668]: PRNG seeded successfully
> 2009.02.04 13:54:04 LOG7[2828:5668]: Certificate: stunnel.pem
> 2009.02.04 13:54:04 LOG7[2828:5668]: Certificate loaded
> 2009.02.04 13:54:04 LOG7[2828:5668]: Key file: stunnel.pem
> 2009.02.04 13:54:04 LOG7[2828:5668]: Private key loaded
> 2009.02.04 13:54:04 LOG7[2828:5668]: SSL context initialized for service
> SQLServer
> 2009.02.04 13:54:04 LOG5[2828:5668]: stunnel 4.26 on x86-pc-mingw32-gnu with
> OpenSSL 0.9.8i 15 Sep 2008
> 2009.02.04 13:54:04 LOG5[2828:5668]: Threading:WIN32 SSL:ENGINE
> Sockets:SELECT,IPv6
> 2009.02.04 13:54:04 LOG5[2828:5672]: No limit detected for the number of
> clients
> 2009.02.04 13:54:04 LOG7[2828:5672]: FD 224 in non-blocking mode
> 2009.02.04 13:54:04 LOG7[2828:5672]: SO_REUSEADDR option set on accept socket
> 2009.02.04 13:54:04 LOG3[2828:5672]: Error binding SQLServer to
> 127.0.0.1:31433
> 2009.02.04 13:54:04 LOG3[2828:5672]: bind: Permission denied (WSAEACCES)
> (10013)
>
> 2009.02.04 13:54:04 LOG3[2828:5672]: Server is down
>
>
>
> My stunnel.conf looks like this (actual IP address has been modified):
>
> ; Sample stunnel configuration file by Michal Trojnara 2002-2006
> ; Some options used here may not be adequate for your particular
> configuration
>
> ; Certificate/key is needed in server mode and optional in client mode
> ; The default certificate is provided only for testing and should not
> ; be used in a production environment
> cert = stunnel.pem
> ;key = stunnel.pem
>
> ; Some performance tunings
> socket = l:TCP_NODELAY=1
> socket = r:TCP_NODELAY=1
>
> ; Authentication stuff
> ;verify = 2
> ; Don't forget to c_rehash CApath
> ;CApath = certs
> ; It's often easier to use CAfile
> ;CAfile = certs.pem
> ; Don't forget to c_rehash CRLpath
> ;CRLpath = crls
> ; Alternatively you can use CRLfile
> ;CRLfile = crls.pem
>
> ; Some debugging stuff useful for troubleshooting
> debug = 7
> ;output = stunnel.log
>
> ; Use it for client mode
> client = yes
>
> ; Service-level configuration
>
> [SQLServer]
> accept = 127.0.0.1:31433
> connect = 85.15.135.121:443
>
> ; In case of a proxy server, use:
> ;connect = 10.3.2.50:8080
> ;protocol = connect
> ;protocolHost = 85.15.135.121:443
>
> _______________________________________________
> stunnel-users mailing list
> stunnel-users at mirt.net
> http://stunnel.mirt.net/mailman/listinfo/stunnel-users
>