Seems this is now the place for all M-Class discussion. I have taken the slightly unusual step of upgrading to an M300, unusual because I don't have the capability to import BR content into my Kaleidescape system (I'm waiting on the IDV, early next year, and hopefully it will decode to LPCM!).
My reason for posting is to describe my M300 install, which was problematic, and to wave the flag for Kaleidescape Tech support who were great in getting me up and running.
After hooking up the new M300 I couldn't see it in my components tab of the installer UI, nor could I see it at my-kaleidescape/lskd.html. Basically I couldn't see the player on my network, but I knew it was talking to something because its green ethernet LED was blinking away. I thought maybe it had shipped with an incompatible static IP, but if it had then it should still show up using /lskd.html given the player was connected to the same switch as the server. The player seemed happy enough because its faceplate LED was blue. Next thought was to force it a static IP using a PC and Hyperterminal, but unknown to me the mini-players don't have RS-232 ports. Having then ran out of ideas I called the forever reliable Kaleidescape Tech support for help.
Sure enough the M300 was indeed trying to call home, was set to DHCP, however couldn't get an IP from the DHCP server on my network (which in my case is a DLINK modem/router). Also, the server was seen to be doing weird things on the network. Restarting the player and the server didn't solve the problem. Restarting the modem/router did. From that point the M300 appeared in my components tab, having been assigned a dynamic IP. I could then give it a sensible static IP, and all was well. Or so I thought.
I reconfigured my Pronto remote, which just requires changing the player IP in the parameters tab of the Pronto module, but no luck. Pronto couldn't talk to M300. So at that point I decided to abandon further efforts and go back to my MP2. I unplugged the HDMI cable from the M300 back into the MP2, but then I was confronted with an audio problem, a terrible pink noise like hissing sound during movie playback (but normal audio during music playback). That required another call to Kaleidescape Tech support. At their suggestion, through trial and error with cable swapping, the audio problem was isolated to my Lumagen video processor. It seems that hot-swapping out the M300 for the MP2 on the same Lumagen HDMI input sent the audio side of things crazy. Fortunately rebooting the Lumagen resolved the problem.
So after all this grief, solved by 2 simple reboots, I'm back to square one and using the MP2 (M300 is back in the box for the time being). Lessons learned: try all the simple and obvious things first! I guess I was lulled into a false assumption that just because a Kaleidescape component faceplate is blue, doesn't necessarily mean it's happy on the network. A simple reboot of the modem/router is always worth a try when components aren't talking to each other as expected. When the audio gets all screwed up, look outside the Kaleidescape environment for a solution. A simple reboot of the device doing the audio switching is always worth a try!
It's just that the simple things sometimes aren't obvious until you've had the benefit of hindsight.
Next step is to work out why the Pronto can't talk to the M300, and unfortunately my hindsight is lacking there as well. But I'm in no hurry, not until the IDV becomes available early next year (subject of course to it being at an affordable price point!).
BTW. Thanks Tech support, you're the best! (I know you monitor the forum in silence here).