TX-NR509 & streaming=error msg

I want to stream digital audio from Windows 7 PC to 509. From Windows Media 12 > Play > Play To, I select the 509. I get this error msg:

TX-NR509
Device cannot be controlled. Your device is currently locked by another user or device. Please try again later.
HRESULT: 0x80040369
UPnP Error 705

I do get 509 menus for internet radio so there is network connection. Tried toggling a port On but no joy.

What am I doing wrong? I have followed the manual to the best of my understanding.

Thank you.

Hi foolofgrace,

Try rebooting your router and make sure that you have nothing else playing at the same time.

Those fixes didn't work, same error message. I don't suppose there's an error code reference that would tell me what UPnP 705 error means.

Am trying various workarounds to get me what I want -- streaming pc to 509, I don't much care how it happens. Have tried going thru my Roku using various servers like ro-connect but still problems. Have to reinstall OS on my PC this weekend, so won't be able to try more things until that's done.

I really really want this to work; it's the main reason I purchased this unit a few days ago. I will report back after the OS drama with more results. Thank you SO MUCH for actually caring and trying to help me, folks rarely get this level of service anymore.

ttyl!

Hi foolofgrace,

That error message is being generated by the computer and not the receiver so any error reference lists or tables will need to be found on their website or in their manual.
Have you updated to the latest firmware on the 509 yet?

My solution for the UPnP Error 705: It’s taken me more than a year of research and experiments but had my light bulb moment. Here’s what ended up working. FIRST, you select Net -> DLNA -> <mycomputer> -- but you stop before you get to the part where you’re controlling the computer from the 509. And THEN you try to play to the 509 thru Windows Media. It makes logical sense, in retrospect... if its on TUN or CBL, of course "the device is locked by another user or device'. I hope this proves helpful to you.

I should mention that I'd tried a already tried a bunch of 'fixes' already, the latest of which was to assign port 3609 or something, and i don't know if that plays any part in the fix.