Meridian Unplugged - Powered by MrTechGuy.co.uk Forums Discussion Meridian - Streaming Sooloos 2.527

In my case I think the problem may be something to do with interconnection through the router. Having thought that everything was sorted out with Russ's help, I'm now finding that when I turn on my computer I am unable to open Control:PC. I need to re-boot my router to get things to work. I have double-checked this by repeating the sequence. My iPad functions satisfactorily.

Prior to updating to Sooloos 2.527 I have not experienced any router-related problems. Anyone got any ideas / suggestions? Thanks - Jeremy

It is always best to have just a single connection to the main ISP connection router and to use a separate switch for your local network. If you have not already done so, I would recommend going the separate switch route - simple unmanaged switches are very cheap even from the better manufacturers.

John

Thanks John. I appreciate your advice but it does seem strange that I have experienced no router-related problems before the Sooloos update.

I am not at all knowledgeable about router connections. Are you suggesting that I use only one of the Ethernet sockets on the back of the router and connect that to a network switch of some type?

Can you guide me to a link to a simple unmanaged switch of good quality?

Jeremy

These TP-LINK switches work well for me

These Netgear unmanaged Gigabit switches are pretty good too (and cheap): I have the 16-port version.

Exactly, I am sure the other linked switch will work fine, I tend to go for Netgear as being at suitable quality/price position for home use. e.g. a GS108.

John

I had zero issues with MC200 and the following network equipment:
TP-Link AC-3150 fast wifi router
Asus XG-U2008 10Gbit switch (fanless)

I also use a basic switch connected to the router.

I have not updated yet based on some of the problems people were reporting. System works perfectly with the previous version. I wanted to see if any folks had issues with MC600 specifically.

I have running the new software since it was released without any problems. But today I got the same problem as Xanavi. I Think ther must be a bug in the latest release. I followed the guide in this thread and got the system in operation again. But when I should turn of my MD600 it seems to be completely locked. I had to make hard shut down via the Power switch.

Thanks everyone for your helpful comments. Whilst acknowledging that a separate switch for my local network may be a sensible option, I'm slightly puzzled as to why a Sooloos update should affect a router network that was functioning perfectly well beforehand.

I am using a ZyXEL VMG8924-B10A Router with 4 LAN ports. One was connected to my PC, and the other 3 to a NAS, my MS600 and a TP-LINK TL-SF1005D 5-Port 10/100 Mbps Unmanaged Desktop Switch (Extender hub).

The extender hub was connected to my MD600 and to a TP-LINK WPA281KIT V3 AV200 Powerline 300 M Wi-Fi Extender.

I'm guessing that my extender hub is similar to what is being recommended by you folks? I wondered if maybe I was confusing things by having my MS600 connected directly to the router and the MD600 connected to the extender, so I reconfigured the Ethernet cables so that the MD600 and MS600 both connect to the extender hub? Unfortunately this didn't change anything. It is still necessary to re-boot the router after firing up my PC. Any other thoughts? Is there a possibility that I need to reconfigure something in my router setup?

Jeremy

PS. I should also point out that in Sooloos Configure I only see Control:PC. No sign of my MD600 or MS600

PPS. I have just found out that my partner's laptop, which is connected wirelessly into the network, can open Control:PC without any problem - i.e. it isn't necessary to re-boot the router. My PC is hard-wired to the router and I have to re-boot the router to access Control:PC. I don't know if this information will enable anyone to give me any hints?

A long shot, but how old is your powerline kit? I had weird, inconsistent problems with a domestic network and it turned out the WPA281 kit had aged and was causing what can best be described as interference. When removed everything was fine (try that yourself). The better news was that TP-Link replaced it under their 3 year warranty (had to take it to their office though).