Re: [sc-users] error message: SC_UdpInPort: received error - An existing connection was forcibly closed by the remote host

Hello, I'm currently migrating some code from OSX to Win 10 and have run into the same error message, but only when I try to send OSC to a port that is not currently open (given the nature of the project, I can't guarantee that the port will be open always, it should fail silently if it's not). I've enclosed the code in a try {} block, which has no effect in catching the error. Turning off IPv6 in windows network settings reduces the number of error messages from roughly a bazillion down to one, which is a positive step.

Just wanted to bump this thread in case anyone has found a solution to this, since it really makes it hard to see what else is going on in the post window :)

On Fri, Jan 4, 2019 at 6:34 AM <postmaster@xxxxxxxxxxxxxxxxx> wrote:

Hi all,

I'm migrating some projects from OSX to Windows 10 and I ran into an unexpected problem when making SC communicate with Unity via OSC.

I keep getting the following message which clutters my post window:

SC_UdpInPort: received error - An existing connection was forcibly closed by the remote host

This happens whenever I send and OSC message from an OSCReceive function. In this particular case I'm reading messages that are received by a Synth that uses the SendTrig Ugen. When certain conditions are met osc messages are sent on to Unity and this is the moment when the errors occur. These errors occur regardless whether Unity is running or not.

Since this code worked without flaws on OSX I'm quite certain that it's not a coding error in SC. I'm suspecting it might be related to security settings in Windows. I already granted access to sclang and scsynth (and Unity) through the private and public firewalls of the Windows Defender Firewall, though. Has anybody had similar issues and found a way to solve it?

Thanks,

Marko