Move from Router to Modem + Router

Keep the modem its un-bridged state, and try setting the Netgear router to Bridged instead.  Then turn off the WiFi radio on the modem.  That will allow the modem to remain the DHCP server, controlling IP addresses.

Netgear WAN port connects to modem LAN port.

This is the simplest option to try, first.

Nick

I would recommend doing what Nick says, and simply disabling WiFi on your Talktalk router, using a wired connection from there to your Netgear. 

In my experience, the real weak link in the chain is the Naim WiFi module. I would recommend disabling this and connecting another WiFi device to the Qute. Probably easiest to configure if you use the same brand (Netgear.) I did this with an Apple Airport Extreme/Airport Express setup and it worked pretty well, even streaming 24/192 on a good day. 

If you stream from a NAS, the next stage would be to connect a switch to your Qute, NAS and Airport Express (or a comparable Netgear device) so that only internet services rely on WiFi. This assumes you can put your NAS close enough to the streamer to wire them together. 

Or better still, leave the talk talk router as is, and additionally connect the Netgear device in bridge mode to act as a wifi acces point nearer your audio equipment. You can set up a seperate specific SSID on your Netgear wifi access point just for your audio equipment so it could be more responsive if you have others in your family  on your wifi 

i thought the idea here is to leave the TalkTalk router to deal with the internet connection stuff, and then the Netgear would handle the DCHP and wireless stuff?

I have have my Asset upnp server (a Windows PC) and a ND5XS wired via switches (currently) to the TalkTalk router. There isn't scope to have the Netgear near the Qute though.  If I have the Netgear handling the wireless stuff, does that present a problem for the wired ND5XS - wouldn't that then be on a different network to my wireless ipad used to control it?

As things stand currently, the Qute works very well on iRadio or upnp once it's connected, it's just that I have to re-connect the wireless network regularly.

During the modem is in bridge mode, usually ethernet port one is operating, the rest is disabled.

Gavin,

IME, on average, Internet modems usually have WiFi performance that is inferior to the best available; only occasionally have I found them to be poor DHCP servers, too.  In such a case, then I have let the inside router handle DHCP -- doing so is slightly more complex, and it invites a discussion as to whether or not to run both un-bridged, in "double-NAT" fashion, which is a dull conversation, to be avoided if possible.  

In addition to the DHCP function, it is possible sometimes to transfer all of the ISP security settings from the modem to the router, but your ISP may not support the move, or issues logging onto their service from a router they do not provide -- all of which is not to say it cannot be done, perhaps to advantage.

Nick

Guys, a modem is just that, it modulates and demodulates .. typically DSL lines. It will often convert different link and physical protocols... but this is all below IP.

so you either configure  the Talk Talk router as a modem, in which case it must connect to another router as you need at least one functioning router. 

My recommenation unless you know what you are doing is leave the Talk Talk as a router with its inbuilt modem.. there will be almost certainly advantages to this as the PPP implementation will be almost certainly optimised for the ISP. I would then use another device as the or an additional wifi access point. If it's the Netgear 'router' ensure you can configure it in bridge mode so it ceases to be a router, disable DHCP, and simply use it as wifi access point.

its important you just have a single subnet from your single router, so internal or double NAT/PAT is a definite no no, if things like UPnP discovery and update are to work

Some slightly odd behaviour last time I had my network problem which has me wondering whether there's a fault with the Qute...

As usual I got the 'Input Initialising' message on iRadio and upnp, but I also got the same message on the front panel iPod connection! Surely that has nothing to do with the network connection. It went a little further. I went through the process of re-selecting the wireless network and putting the password in, but I got a message saying it couldn't connect (possibly as a result of wrong password) but all the inputs went back to the working state.

I've emailed Support for their thoughts. Any other ideas?

Hi Gavin -

Any way you can string a long Ethernet cable through your house on the floor to see if wired vs wireless makes a difference? Any chance you're on old firmware? Can check your version in the Settings menu (wrench icon on IR remote) and compare to latest downloadable version on the site. I had a similar experience on a Qute v1 ages ago; reflashing the firmware helped and it's good to stay current as new versions are released. Couple of things to try at least. Best wishes  

Regards alan

Gavin B posted:

Some slightly odd behaviour last time I had my network problem which has me wondering whether there's a fault with the Qute...

As usual I got the 'Input Initialising' message on iRadio and upnp, but I also got the same message on the front panel iPod connection! Surely that has nothing to do with the network connection. It went a little further. I went through the process of re-selecting the wireless network and putting the password in, but I got a message saying it couldn't connect (possibly as a result of wrong password) but all the inputs went back to the working state.

I've emailed Support for their thoughts. Any other ideas?

I think the initialising message shows whatever input you have selected. It really just means "Hang on sunshine, I'm busy elsewhere right now."

If you can't log into your wireless network then this sounds like a router issue to me. So switch off your Naim unit, reboot your router and once it's restarted, switch your Naim back on.

i agree with Alan it's worth trying a lead instead of wifi (you can move the Qute to be near the router without connecting speakers to it if you just want to check if it finds the network ok).

best

David

Thanks, Alan and David. Phil H. has suggested connecting the Qute by wire to check if it holds the network. We're going away for a few days so will move it and give it a go.

I'm pretty sure I'm on the latest firmware but I'll check.

(Just got up to the Qute displaying a Fault 59 notice!)