The problem is that iLive Editor hangs while trying to connect to the iDR-32 no matter which version of the software is used Windows or Linux.
Resetting network card with 15 second switch doesn’t help.
I have no idea, if it is iLive Editor software problem, MixRack hardware problem or MixRack firmware problem. It could be that the iDR-32 firmware is too old, and no version of available iLive Editor are able to communicate with that. But I am speculating. It would be nice to be able to diagnose what is wrong with this MixRack (or not) step by step.
Are you connecting a computer directly to the network port on the iLive, or are you connecting these devices to a larger network with a router and network switch?
I only ask because the most common consumer grade router address is 192.168.1.1 which would cause a conflict with the iLive’s default address of 192.168.1.1. You may need to change the router’s default network address in this case.
If you are connecting the computer directly to the iLive’s network port, are you manually assigning a static IP address for the computer’s network port? Computer network ports are typically set to DHCP by default and if this is the case, without a router/DHCP service running on this simple network, the computer is going to default to a 169.254.x.x network address. If this happens, the computer and the iLive are not on the same network segment which would easily explain why the software cannot connect with the iLive. Assigning the computer a static IP address in the 192.168.1.X with a 255.255.255.0 subnet mask (but not 192.168.1.1 because that is used by the iLive) should solve your connection issues.
I beleive if the software can establish a connection with the iLive, it will tell you if there is a firmware mismatch. I believe it also will tell you what the current iLive firmware version is so that you can correct the mismatch. (I have an iLive, but it’s been so long since I set up the network, or changed the firmware that I am a little foggy on the exact operation/functionality).
If I could have a script that does firmware check, all these misconfiguration issues and version mismatches could be ruled out. I am pretty sure there is a packet coming back from the MixRack, and the control port 51321 is open there.
Mixingstation is way easier to try and should connect to most versions and give you an error if it cant.
Its possible the DSP is toast. Theres a common failure there was a service bulletin to isolate the 24V supply from the other voltage supplies. If that wasnt done and it got humid and dusty its likely the higher voltage flashed over and killed the DSP.
If you type the mixrack IP in a browser you should get a 404 page that says “iDRLive HTTP Server Error” that will confirm you have the mixrack IP correct.
Connecting to http://192.168.1.1 through a browser just made the browser hang connecting. I am going to try it again to see if it the browser fails with connection time out after 90 seconds like it happens when IP:Port doesn’t exist. Need to try http://192.168.1.1/Setup.html as well.
If everything above fails (after going through cycles of power off, power on and waiting at least 2 minutes before try) I also want to scan open ports with nmap.
Tried different combinations, this is the last one. It would be nice to get some manual, or another way to confirm that these steps should do something.
Is it dead CPU or could it be damaged firmware chip? Something initializes network card and makes it accept connections. I guess that without CPU nothing will accept TCP connections, and there are 3 ports open.
❯ sudo nmap -sS -p- 192.168.1.1
Starting Nmap 7.99 ( https://nmap.org ) at 2026-07-04 23:02 +0300
Nmap scan report for 192.168.1.1
Host is up (0.0022s latency).
Not shown: 65532 closed tcp ports (reset)
PORT STATE SERVICE
80/tcp open http
51321/tcp open unknown
51325/tcp open unknown
MAC Address: 00:04:C4:01:4C:16 (Audiotonix Group Limited)
Nmap done: 1 IP address (1 host up) scanned in 40.43 seconds
Connecting to 51325 hangs too, but connecting to 51321 spits out some data. So something is alive there.
I had to reset the network settings in my iLive this weekend before a gig, so the process is fresh in my mind!
Just to triple check - you are turning off the iLive, then pressing the network reset button (the small hole with the recessed button near the network ports) and holding that button in while you turn the Mixrack back on, and continue holding the button in for at least 15 seconds after reapplying power?
If so, and the Mixrack (at ip 192.168.1.1 after the reset) is still no responding to connection attempts from the iLive Editor, or Mixing Station, then I agree that something has failed in the unit that is preventing the connection from being established.
The connection is established as shown by curl earlier, so network card seems to work perfectly. But there should be something beyond network card to send reply over the connection, and it is not clear what it is.
