N-stream/Qute issue

you mean n-Stream can't find Qute? I'm using my Qute only wired and it works ok, but consider that wired / wireless means completely different network interfaces, MAC addresses, etc. Moreover you'll need some authentication with WLAN - may be check of the Network Settings on Qute, if they are ok, will help. If nothing else helps I'd "reboot" Qute turning it off and then on with the rear panel switch (MS trick, which (un)fortunately can help :-(...)

quote:

Originally posted by okli:
you mean n-Stream can't find Qute? I'm using my Qute only wired and it works ok, but consider that wired / wireless means completely different network interfaces, MAC addresses, etc. Moreover you'll need some authentication with WLAN - may be check of the Network Settings on Qute, if they are ok, will help. If nothing else helps I'd "reboot" Qute turning it off and then on with the rear panel switch (MS trick, which (un)fortunately can help :-(...)

Ok - need to check the Qute and streamer are on the same subnet now that you are using a wired connection. You mention you are using a router - if you really mean a router and not using a switch then that will be most probably be your problem. Routers route traffic between different subnets. Streamers and receivers - especially uPNP, Apple etc need to be in the same subnet - unless involved broadcast packet forwarding is enabled.

To confirm whether streamer and Qute are now on same subnet can you please post IP address and Subnet mask for the Qute when working on wireless - any device on that wireless with the same wireless name (SSID) will do, and the IP address and subnet mask when you connect the Qute via wired ethernet. I can aadvise you whether you are on the same subnet or not. Also just worth while confirming IP address and subnet for the device runnibg n-Stream.

Simon

Thanks folks, that all sounds helpful and potentially to have flagged my problem. I'm away from my home office for now though and will not be able to post settings and look into this until Sat pm at the earliest.

I have tried the switch off/on incidentally-that is where my computer knowledge usually starst- and ends!

Bruce

Bruce

You indicated in another thread that you have also changed networks - it may alternately be the case that your current (second) network has TCP ports blocked (intentionally, a corporate network) which will affect broadcast device discovery messages.