winsock permissions issue (i.e. WSAEACCES 10013 / 0x271D)
Hi Paul. With respect to your winsock permissions issue (i.e. WSAEACCES 10013 / 0x271D), did you open the port in your firewall and authorize communication via anti-virus?
Hi I have a windows 10 machine that I?ve got this running on, and the screen shot below is what I keep getting and I am unable to find the issue,
Can someone please shed some light as to what is wrong? And what else you may need.
It’s an internal connection to our database server, no firewall to go through, hmmm unless Sophos doesn’t like it… From: Brent Kimberley [mailto:brent_kimberley@rogers.com] Sent: Wednesday, June 24, 2020 3:13 PM To: stunnel-users@stunnel.org Cc: teward@thomas-ward.net; Coviello, Paul; chris@christopherschultz.net Subject: winsock permissions issue (i.e. WSAEACCES 10013 / 0x271D) EXTERNAL: This email originated from outside of the organization. Do Not Click any links or open any attachments unless you trust the sender and know the content is safe. Hi Paul. With respect to your winsock permissions issue (i.e. WSAEACCES 10013 / 0x271D), did you open the port in your firewall and authorize communication via anti-virus?
Hi I have a windows 10 machine that I?ve got this running on, and the screen shot below is what I keep getting and I am unable to find the issue,
Can someone please shed some light as to what is wrong? And what else you may need.
Windows has its own Firewall that may interfere.Also Sophos might detect it as a disallowed app category and block it, which requires altering of the Sophos policies to permit it.Sent from my Sprint Samsung Galaxy Note10+. -------- Original message --------From: "Coviello, Paul" <pcoviello@ccsusa.com> Date: 6/24/20 15:30 (GMT-05:00) To: Brent Kimberley <brent_kimberley@rogers.com>, stunnel-users@stunnel.org Cc: teward@thomas-ward.net, chris@christopherschultz.net Subject: RE: winsock permissions issue (i.e. WSAEACCES 10013 / 0x271D) It’s an internal connection to our database server, no firewall to go through, hmmm unless Sophos doesn’t like it… From: Brent Kimberley [mailto:brent_kimberley@rogers.com] Sent: Wednesday, June 24, 2020 3:13 PM To: stunnel-users@stunnel.org Cc: teward@thomas-ward.net; Coviello, Paul; chris@christopherschultz.net Subject: winsock permissions issue (i.e. WSAEACCES 10013 / 0x271D) EXTERNAL: This email originated from outside of the organization. Do Not Click any links or open any attachments unless you trust the sender and know the content is safe. Hi Paul. With respect to your winsock permissions issue (i.e. WSAEACCES 10013 / 0x271D), did you open the port in your firewall and authorize communication via anti-virus?
Hi I have a windows 10 machine that I?ve got this running on, and the
screen shot below is what I keep getting and I am unable to find the issue,
Can someone please shed some light as to what is wrong? And what else you may need.
Maybe, I also just found out that the port it goes out is not what I thought it was. It’s a random port. Not sure if it’s doable now. Thanks for your help From: Thomas Ward [mailto:teward@thomas-ward.net] Sent: Wednesday, June 24, 2020 3:52 PM To: Coviello, Paul; Brent Kimberley; stunnel-users@stunnel.org Cc: chris@christopherschultz.net Subject: RE: winsock permissions issue (i.e. WSAEACCES 10013 / 0x271D) EXTERNAL: This email originated from outside of the organization. Do Not Click any links or open any attachments unless you trust the sender and know the content is safe. Windows has its own Firewall that may interfere. Also Sophos might detect it as a disallowed app category and block it, which requires altering of the Sophos policies to permit it. Sent from my Sprint Samsung Galaxy Note10+. -------- Original message -------- From: "Coviello, Paul" <pcoviello@ccsusa.com> Date: 6/24/20 15:30 (GMT-05:00) To: Brent Kimberley <brent_kimberley@rogers.com>, stunnel-users@stunnel.org Cc: teward@thomas-ward.net, chris@christopherschultz.net Subject: RE: winsock permissions issue (i.e. WSAEACCES 10013 / 0x271D) It’s an internal connection to our database server, no firewall to go through, hmmm unless Sophos doesn’t like it… From: Brent Kimberley [mailto:brent_kimberley@rogers.com] Sent: Wednesday, June 24, 2020 3:13 PM To: stunnel-users@stunnel.org Cc: teward@thomas-ward.net; Coviello, Paul; chris@christopherschultz.net Subject: winsock permissions issue (i.e. WSAEACCES 10013 / 0x271D) EXTERNAL: This email originated from outside of the organization. Do Not Click any links or open any attachments unless you trust the sender and know the content is safe. Hi Paul. With respect to your winsock permissions issue (i.e. WSAEACCES 10013 / 0x271D), did you open the port in your firewall and authorize communication via anti-virus?
Hi I have a windows 10 machine that I?ve got this running on, and the screen shot below is what I keep getting and I am unable to find the issue,
Can someone please shed some light as to what is wrong? And what else you may need.
What are you trying to accomplish? I.e. Is TLS the best wrapper for the job? (i.e. TCP over TCP.) On Thursday, June 25, 2020, 11:44:38 a.m. EDT, Coviello, Paul <pcoviello@ccsusa.com> wrote: Maybe, I also just found out that the port it goes out is not what I thought it was. It’s a random port. Not sure if it’s doable now. Thanks for your help
participants (3)
-
Brent Kimberley -
Coviello, Paul -
Thomas Ward