The specific repro instructions are:

1) try to set up Jive and Ray on a network with no DHCP (I'm using a windows ad-hoc network, but any net with no DHCP should do)
2) allow Jive to self-assign addresses.
3) Note the process seems to proceed okay all the way to the point where it asks you to select a music source.
At this point Jive is showing a white power-bar indicator because it's on the network and Ray is showing a blue LED because it's on the network but not connected to the server.
However, no server name appears on the screen.  In addition, due to bug 6303, there is no workaround.

Both Jive and Ray are pingable from the slimserver PC at this point and appear to have typical self-assigned addresses according to arp.

I experience the same for all ray jive configurations that uses or requires a self assigned IP address.  I did find a workaround of sorts with Chris's help.

Steps to reproduce:
1 Setup a configuration that uses or requires a self assigned IP address
2 Factory reset your jive and ray
3 Select your network on jive then choose Self-assign after timeout
4 Select your ray and notice that ray gets to blue and jive times out
5 At this point power cycle jive with the power button
6 When jive comes back up select your language, region and then the same network as before
7 Select set up player and choose your ray again
8 You should now be able to choose your music source on jive
9 Notice ray and jive will now work

Another thing I noticed is that I was not asked to do a software update on the jive nor could I do a software update by choosing Network update from the jive menu otherwise it seemed to work fine.

This was with ray_18, jive MP candidate v5 and SC 7.0 - 15353

> Another thing I noticed is that I was not asked to do a software update on the
> jive nor could I do a software update by choosing Network update from the jive
> menu otherwise it seemed to work fine.

I realize now with this config I do not have a valid internet connection thus I did not get a new jive firmware, duh ;)

I am nearly sure this is a Jive software bug because if you power-off and back on the Jive, Squeezecenter is now visible in the Jive display.

Is this appropriately assigned to felix?

Sorry about that. 

Partial fix in r1536. This fixes the problem reported by Steven, but the that seen by Chris.

The udap and slim discovery udp packets don't appear to be working. A wireless network sniff is needed showing this failing to determine where the problem is.

Richard: Do you need help from Ross to get this sniff?

I did some setup testing today and it worked 5 out of 5 times. Before each attempt I factory reset Jive and Ray.

Setup:
- Mac with self assigned ip, running SC (rev 17009) and wired to AP
- Jive (fw 21) connected to AP, self assigned ip
- Ray (7.0 r1658M) connected to AP, self assigned ip

Steps:
1. Jive: Select Language and Region
2. Jive: Choose AP from list
3. Jive: After timeout, choose self assigned ip
4. Jive: Choose Ray to setup
5. Ray: Reboots and get to blue (with self assigned ip)
6. Jive: Choose Music Source
7. Ray: Connects to SC
8. Jive: Connects to Ray

Richard: Why would the scenario described by Chris be different from what Steven wrote? Do you think the wireless sniff is still needed? What did I miss?

Felix thanks for looking at this.

In Steven's case Jive failed to reach the music source screen. In Chris's case the music source had been selected but Ray was stuck on blue. I had fixed the first problem, but could recreate the second one easily last time i checked.

As you think this is now ok qa should try again, just in case there network setup is somehow different.

Works great now! I used a D-link router and disabled DHCP, pc self assigned then Jive and Ray self assigned exactly as Felix says in comment #10. 

This bug has recently been fixed in the latest release of SqueezeCenter 7.0.1

Please try that version, if you still see the error, then reopen this bug.

To download this version, please navigate to: http://www.slimdevices.com/su_downloads.html