What I’ve found is the Enable DHCP can be confusing. If the “Enable” is green and highlighted it’s not on. If you press apply and it says"Disabled" in gray, it is on now locked on to the IP address with the router. This has caused drop outs and craziness with iPads.
I’ve got the exact same problem here. did you ever get this resolved?
I did, after they replaced my console. I’m convinced the network card was defective.
Well now I am faced with this problem. On a QU-24 I just installed. I tried everything I can do. Taking my QU16 to the church tomorrow to see if it works. After upgrade to 1.82 it didn’t want to work at first but finally did. Have never had that problem with it in 3 years.
Had some back and forth with AMS today but nothing firm. I am requesting an advanced replacement since I just opened it although have had it for over a month waiting building completion. Now their opening is next week. I can’t wait for an exchange or repair.
I am having this same issue with my QU32. Everything has worked flawlessly since I got this console for the last 2 weeks and now suddenly (just before sound check) the network port decides it doesn’t want to work. No light on… No nothing.
bummer…
Mine turned out to presumably be a network port or card problem. A new console is on its way to me. Shipping this one back. I hooked up a QU16 to the router and it worked fine. 24 won’t. Only one I have had problems with.
Has anyone one with this issue been able to replace the internal network cable and everything was good? Or generally did these problems result in desks being replaced?
I can only speak from my experience with the Qu-32, and that had to be replaced.
My Qu-16 and Qu-24 have been fine.
Hi guys,
If you’re still having issues can I ask you to check a couple of things:
-
Is there LED activity on the LAN port on the back of the Qu, if so then this suggests the devices can see each other.
-
Check the IP address of the iPad and the IP address of Qu. The Qu IP can be found under Setup > Utility > Diagnostics
The only IP address variable should be the last entry, 192.168.1.xx
Drop me a line support@allen-heath.com if you still have issues.
Regards
Mike
I am pretty sure it is not a router/ip address issue. I initially can connect normally, soon after that, the connection is dropped, no activity on the lan port. I simply unplug the cable, plug it back in (sometimes i have to do this twice.) The activity light comes back on and im back in business, but for how long? 1-5 minutes, maybe 20 if i’m lucky and i’m repeating this process again.
@Dave, have you experienced this problem with one router or have you experienced it with multiple routers?
Multiple routers, i initially switched to the airport express because that was what AH said they used in house and tested with.
A big thank you to the anonymous poster who suggested a bent pin in the network socket due to accidentally plugging a USB B plug in there. I cam to this thread through a search because I’d lost network connectivity with my QU-24 after moving it - again, like Rob experienced.
The post jogged my memory and I vaguely remembered plugging the USB in wrongly.
A close look with good light and I could see that pin 3 was bent over and touching pin 2. I teased it back over with a sharp screwdriver and hey presto, everything’s back to where it should be.
THANK YOU!
Hello Friend!
I have a problem
I have a QU - 32, there are days I am trying to connect my android in it to be able to move, but every time I try the connection is not right, the application finds the table, but says that the connection fails. please, could you help me ?
Try setting your router to a different channel. You may be experiencing interference from nearby routers using the same channel.
I’m very late to the party on this thread, but I thought I’d post my experience with a similar issue in case someone is searching the forums for a solution.
My QU 16 is not connecting to DHCP. After several days of troubleshooting I realized that the NETWORK port could be defective. I’ve never plugged anything into it, in the first two years or so of ownership, as I had no need to do so. So it was in the same condition as it left the factory, I’m certain.
I have a simple continuity tester, and should have done this first, but even the cheapest devices rarely have this kind of problem. Never would have guessed this otherwise wonderful board could have a workmanship issue like this. Sure enough, only a few of the tines of the Cat5 cable showed presence of continuity.
I can get connectivity if I force pressure on the cat5 cable, which seems to complete contact. Of course, I’m not going to be able to hold that while we work.
Reading through the threads, and other forum-style sources on the web, I see several similar issues with the board from the same time period, including the one that Rob @Hobsound discussed in this thread.
First thing to do is to check that RJ45 port. Ensure the tines of the receiving jack are aligned, and positioned in a manner that ensures solid contact on all the twisted pairs of cat5 cable.
I would also add that at first, the light for the Network jack would not light under any circumstances, including looping from the d-snake jack to the network jack. The expected result of that loop (I assume) is that both would flash consistently to indicate signal presence. On a whim, I reset (soft reset, from the scenes panel) and behold, the network jack began to flash, though still would not populate an IP address, so still not working. But a soft, or hard reset may recover a sleeping RJ45 port, I suppose. But each tine has to connect solidly for it to acquire an IP address.
SO frustrating. This clearly left the factory in that condition, which means someone did not test this product sufficiently. Now, I have a problem jack, and I have to figure out where to get the part. I certainly hope it’s plug-in and not soldered. That would be a major hassle. Does anyone know how to get parts?
Mike Carr
Hi Mike.
I thought this had happened to me but what had damaged the ethernet socket was me accidentally plugging the USB-B plug into it! The USB socket is next to it on my Qu-24. It’s easy done.
So not a manufacturing fault but user error.
It’s possible that the same thing happened to yours.
Straightening the pins carefully has sorted it and it’s rock solid now.
Always fun posting to 10 year old threads…
In case anyone has the same issue I had, on my Qu-32 the IP Subnet must be 192.168.1.x
I was using 192.168.106.x and nogo with Qu-You.
This is the case with DHCP enabled or using a Static IP.
Did not test with Qu-Pad but I suspect the same may be true.
LOVE the old Qu, I’m sure the new series will be top shelf!