After some careful looking into, I perceive a pair of faults on the
software and hardware:

The unit sends a DHCP too fast for 8 of 9 managed hubs and
switches I tested this morning. Without a second try for
a DHCP the unit always defaults the IP and then once the
server is contacted is useless. Fix would be a slight delay
on the initial packet send or a repeat of the DHCP after a
timeout, before the SSDP attempt.

This is based on "default" prom loads on these products.
I was able to get the receiver working on 5 of them but
haven't got the other 4 figured out yet. Its not a question of
the timing "to 10mbs" as someone suggested, but just plain
in the forwarding timing of the ports themselves. Some
devices can attempt to make this "near instant" or "fast
forwarding".

Second, the log is not near elaborate enough about what the
server is actually doing. Perhaps this is by design and it
has various levels of timing and verbosity? If not, more
info on detecting and contacting units should be added.
It was a bit frustrating to always see it pop up on the server list
but never in the logs.

Once working its a nifty product, save for the tiny tiny
text.

Hopefully someone can condense this and add an FAQ entry
on managed switches/hubs to help out others in the future.

Ed