Page 1 of 1

Artnet binding problem (failed to bind sockets on ArtNet port)

Posted: Sun Jun 12, 2022 1:52 am
by oharding
Hi!

When I try to choose my ethernet port as artnet output to control LED pixels it gives an error saying: Madmapper failed to open port on selected network interface (...). Either the network is not available or another application opened the ArtNet port exclusively. (Put the text here for people troubleshooting the same problem.) What could be the issue? The problem occurred with Madmapper 5.0.0.
The only thing I changed with my computer since last successful use of the pixels was downloading Madmapper 5.1.3 and uninstalling an old 4.something version I had on my computer. In 5.1.3 the ethernet port is not visible at all and the list of ports is smaller than in Madmapper 5.0.0.

Thanks in advance.

Re: Artnet binding problem (failed to bind sockets on ArtNet port)

Posted: Sun Jun 12, 2022 8:28 pm
by mad-matt
Strange. Could you send:
- a screenshot of the list of network interfaces you see in MadMapper / Preferences / DMX Output ?
- a copy / paste of the output of command line (cmd.exe) "ipconfig"

Re: Artnet binding problem (failed to bind sockets on ArtNet port)

Posted: Mon Jun 13, 2022 4:19 pm
by oharding
Strange. Could you send:
- a screenshot of the list of network interfaces you see in MadMapper / Preferences / DMX Output ?
- a copy / paste of the output of command line (cmd.exe) "ipconfig"
Here you go. One screenshot is of Madmapper 5.0.7 and 5.1.3 output list. It's the same across these two versions. The other screenshot is 4.2.1. output. I installed three of the newest versions for troubleshooting.

Here's the output of ipconfig concerning this ethernet adapter. I don't have the LEDs connected right now.

Windows IP Configuration

Ethernet adapter Ethernet 1:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :