1.5.1 and MA2 3.1.2.5 still has "Socket can't be used"

Post Reply
focus
Posts: 2
Joined: Mon Sep 21, 2015 9:17 pm

1.5.1 and MA2 3.1.2.5 still has "Socket can't be used"

Post by focus »

Running 1.5.1, with onPC 3.1.2.5 Windows 8 64bit and Command wing. Microsoft loopback adapter ip 2.255.255.10(same as onPC)

Works fine under 3.0.0.5, but on 3.1.2.5 I get nothing. When I assign a local ip in the "special" tab (2.255.255.9) I get the "Socket can't be used" error.

Am I doing something wrong here?

Also OnPC does not appear in the "found artnet box" but still connect fine in 3.0.0.5, even though I cannot see it.

Thanks!
bernd
Site Admin
Posts: 131
Joined: Tue Oct 22, 2013 9:54 am

Re: 1.5.1 and MA2 3.1.2.5 still has "Socket can't be used"

Post by bernd »

This IP 2.255.255.9 needs also assigned to your network adapter you are using.

If is not bound you get that error.

Assign Multiple IP address in Windows OS
focus
Posts: 2
Joined: Mon Sep 21, 2015 9:17 pm

Re: 1.5.1 and MA2 3.1.2.5 still has "Socket can't be used"

Post by focus »

That's what I was doing wrong. Works perfect, thanks!
Post Reply