Streaming connection routes

Have changed BT Home Hub for a Belkin one I had lying around.

Wireless of, and set up as before.

Has dropped twice, once after playing for a while, when I changed tracks on the Qute, the other quite random, so seems much better than before.

Fingers well and truly crossed and some more options from Simon should this not work.

PG - how's it going now?

One thing that occurred to me - when using my Sonos I have experienced dropouts when I've been doing big write jobs on the NAS. The Sonos is just reading the files off the NAS (I.e. Its the Sonos component which you hard wire to your router which acts as the server, so it's just reading off the NAS, not using upnp), so not sure if you would be affected when using a upnp server which is running on the NAS itself, but it's just a thought.

If everything is wired together now, the NAS and qute are on the same switch, IPs fixed, and NAS only being asked to serve the music - then if you're still getting any drops outs, I'd start thinking about a component or cable being faulty.

Dan

If the drop outs occur  and the buffer shows empty at the time of the dropout,and then restores a moment later, it is nothing to do with using static IP addresses or DHCP. If its DHCP related with regard to the Naim component, it will be stuck on network initialising or stop working a day or other large period after a reset.

If you have slightly unreliable wireless components or signal strength, the layer 2 network (MAC) address  (not to be confused with layer 3 IP address) discovery for the control point can fail to work reliably, and can be helped by fixing the IP address, (but this is not an issue with DHCP which is used for IP address assignment not network address discovery)

Simon

Morning all

Since changing to the Belkin for connecting to the internet (wireless off) things are much better.

On Sunday once it had settled in, it played almost flawlessly.

Yesterday was the same, except for when I skipped tracks (quite quickly) and it stopped, this I suspect is just trying to play catch up, a bit like clicking a mouse too much.

I get what Simon is saying, in that the earlier issues were when it was initialising the input. Now it stops when skipping through tracks and when it can't read the file (just wish it would show the file so it can be deleted) I can live with that.

Everything Naim/NAS is wired now, no power line adapters and no BT home hub. The IPs are leased forever, couldn't find how to fix them.

So I am hopeful all is OK. Additionally I left the Qute powered up yesterday and it sounded great and worked fine, where previously it dropped even more when left on.

Once again thanks for all the help and support. 

Spoke too soon, dropping connection after 5 mins, with a screen saying ...connecting....please wait.

Never goes any further and have to swap between inputs.

An update & hopefully not speaking too soon.

Yesterday after drilling holes in walls and in an old house you can imagine bits of plaster falling off, I had the whole system set up with the end results as per my last post.

In the afternoon I went out and bought a Netgear switch, got home and connected that as per Simon's earlier thread. I had some Airport Expresses lying around!!!

Set up was Belkin modem/router for internet, wireless off.

Links into AIrport Extreme for general wireless, which goes to Airport Express, where the ethernet port is linked to the Newtgear switch, which links to the Qute and NAS.

After some mucking about with the expresses (one g one n) it was up and running.

All seemed fine, but when connecting to internet radio, it took ages and froze. Going back to streaming from the NAS and on the whole all was OK until hoping from one track to another, then it would cut out.

So late last night I swapped the Belkin (never has been reliable) for the BT Home hub.

Today, from 0845 I have been listening to internet radio, then the NAS for 30 mins, before going out and leaving it running, I got back in at 1115 and it was still playing and at this moment.....it still is.....

The upshot is 2 holes in walls that didn't need to be drilled, a very long ethernet cable that wasn't needed, and let's not mention the switch I had to buy after selling my last one on ebay......but hey...as long as it works.

FINGERS AND TOES CROSSED.......

Yep, spoke too soon, stopped twice after two songs......

I had similar issues which I posted in another thread. I got the advice to use Airport Extreme to Airport Express (using N not G) and then a short Cat5 to my ND5 XS. No switch between Express and ND5. I have been running this setup for a few weeks now without any dropout or stop. Rock solid.

When you say one g one n, are you using n now? That should be better than using g.

Have you updated Express and Extreme with latest FW 7.6.1?

What about removing the switch and the NAS, using N and internet radio just as a test to see if this works?

Interesting it has just stopped after working since my last post and this time the display was on and showed buffering had gone down by 1 bar and then went to initialising input....

Thanks Ollie will try your suggestion.

Switch is connected to the N one.