TOPIC:

I have a kind of a sprawling home, and for reasons I won't get into here, the number of places where there are both AC mains and a wired Ethernet connection are limited. I tried to connect two PWR-ICE250 amps at two different locations. One would work perfectly; the the other would recognize the amp by name, but not connect to the DSP 'System' -- at least, not on the three allowed retries.

After some sleuthing, I figured out that the first amp was physically connected to the same router as my PC; while the second amp was connected to a second Asus router set up in Access Point (AP) mode.

PC ---> Asus RT-66N <----> RT-66N #2 (as AP) <--- PWR-ICE #2
PWR-ICE #1 --^

Moving the 2nd PWR-ICE fixed things up -- although it isn't the most ideal location for the 2nd amp.

Can anyone explain why the network could see the second amp, but not attach to it? Or am I on the wrong track?

TIA,
-Bruce

@Bruce

Not sure of the reason but it's maybe because you're on another subnet on that second AP? Is that possible?
More information on your network would help as there are thousand of potential reason a packet is not discovered.
Our amps are discovered by UDP (broadcast) but then connecting via TCP. Sometimes that's the issue that some ports are blocked or using different subnets.

DevTeam

Thanks for the reply. I only have one /24 subnet defined, so that can't be the issue. It was a very strange situation, but quite repeatable: the app would find the amp, then try to connect multiple (3?) times, then give up and report the error. Of course, there are other variables such as cabling, but as soon as I moved the cable to the 'main' router, everything popped right up.

Regards,
-BW