Synology streaming problem (also minimserver)

The SSDP has nothing much to with this, mine is set at 600

What is the rest of your system, what is the wireless router, is the system wired or wireless & have you got everything in the system set for DHCP

My vdsl2 modem/router is a bbox3 (Belgium). The Synology NAS is connected with a wire to the router and has a fix IP address. My Naim UnitiLite is wireless and also has a fix IP addess.

DHCP is running for the other devices.

I use the same router and a Synology nas too (212+) with minimserver without any problem... Are you sure minimserver is activated on the NAS? When the firmware on the NAS is automatically updated, minimserver is disabled so you have to activate it again.

Minimserver is running.I can see it in nStream when i do a "rescan" in the minimserver or when i restart the minimserver. But minimserver disappears when my Android tablet goes into standby.

And i had the same problem with the Synology server. But this was 'solved' by lowering the SSDP setting.

First step is to change everything to DHCP,  UnitiLite, Synology & anything else.    

DHCP is designed for simple easy to use home LAN systems & it is more or less foolproof.  Having fixed IP addresses is fine if you know what you are doing, problem is a minor error can cause it to go wrong & its really not worth it in a small home set up.

The router is the DHCP manager - & I am sorry I am not familiar with your bbox3 - but here is were the automatic DHCP IP addresses are located & were you also need to set each unit to DHCP .  

After all the units are reset to DHCP,  then switch them all off - including the nStream

First start the wireless router & let it finish the start procedure.

Next the NAS

Next the UnitiLite

Finally - delete & then reinstall the nStream

Thats it,  no reason why it should not work OK

It did not work with everything DHCP. That is why i gave the UnitiLite and the Synology a fixed address.

That does not make sense, unless the router is not managing DHCP correctly - or its not correctly set to manage DHCP.

It seems minimserver is only sending an SSDP message when it starts/restarts. After that, minimserver sends a multicast "alive" message at least once every 15 minutes, as recommended by the UPnP specification.

I don't think fixed or DHCP assigned addresses can make a difference. I only gave the UnitiLite and Synology a fixed (different) address.

  OK I hear ya,  but I disagree & still believe something in the IP address management is the problem. 

Lets just leave it all as is but run a complete system reboot as I listed in my previous post

- Switch them all off - including the nStream
- First start the wireless router & let it finish the start procedure.
- Next the NAS
- Next the UnitiLite
- Finally - delete & then reinstall the nStream

To get back to SSDP time,   5 seconds is OK but it really is not the route cause of the problem,  I messed around with mine for a while & now have it set to 600

I already did the above steps except deleting and reinstalling nStream.

I just do not understand why all other mediaservers pop up immediately in nStream. It are only the servers on the Synology that have a problem.

I agree that lowering SSDP is only a workaround and not a fix.

I'm sticking with IP address problems & my solution is to revert to all DHCP.

After that,  if it is a still a problem, then at least that question is eliminated & something else can be investigated - but please keep it on DHCP. 

Ok, i will try.

Don't forget that part of the reset process is to reboot everything - as per my first post

Also don't forget that to *PROPERLY* reboot everything you should...

1) Shut down everything that is related to your network - phones, TVs, NASs, streamers etc.

2) Leave your router *OFF* for 15 minutes (this allows the ISPs hardware to recognise that your router has gone offline).

3) Power up your router and leave it for 5-10 minutes to fully come up and reconnect to the ISP.

4) Power up your network devices.

So many people just reboot one thing at a time and this can leave a pretty badly fragmented network ...

Phil

All my problems are solved by using my old Linksys router and not my ISP provided router.

Thanks Naim for the useful info on the streaming forum.

Good to hear the news Erwin.  

Changing to another router indicates a DHCP management problem on the ISP unit.

How did you set up the Linksys,  static IP or dynamic DHCP controlled IP ?.

The Linksys has a static IP. But it is still the ISP router doing DHCP.

I just connected the Synology to the Linksys and used the wifi from the Synology for the UnitiLite and my tablet. That solved my discovery problems with Minimserver and the Synology streaming software. It also solved my frequent "no network" problem.

I connected a LAN port of the ISP router to a LAN port of my Linksys and connected the Synology to a LAN  port of the Linksys.

I just got to this thread.

I had a similar problem with poor discovery performance.  I found it was the firewall rules in my wireless broadband router that was interfering with the discovery process - tweaking the rules (then re-booting everything) solved it.

Hmmm ... If you have the LAN port of a router connected to the LAN port of another router then you almost certainly have two DHCP servers on the same network (unless you have manually disabled one) which is a big no-no.

If you are nesting one router inside another then you should be using a cable router as the 'inside' router and connecting its *WAN* port to a *LAN* port on the ISPs router - you should also ensure that the two routers are on different subnets - so if the ISP router is doing DHCP on 192.168.1.x then then your cable router should be set to do DHCP on 192.168.y.x where y is 0 or 2-255.

(Yes, I am aware that you could also use 10. and 172-16 - 172.31 as ranges too but I'm trying to keep things simple here and not confuse anyone unnecessarily...)

Phil

I disabled DHCP on the Linksys and use it in bridge mode. It works without a problem.

The Linksys also creates a new wireless network that i use for my Naim setup.

When using the Linksys in bridge mode you should connect a LAN port of the Linksys to a LAN port of the ISP router imo.

There is no need for me to use the WAN port on the Linksys. In that case you also use the Linksys to connect to the internet and that i do not want.

On the contrary I assign fixed IPs to all the stationary network equipment at home, including the NDS and NASs, for easier management especially when I need to get into the equipment to troubleshoot. No need to look at the IP table every time and guess which is which when times routers/DHCP servers can't recognize the equipment's name tag. In my case, this also makes it easier for the NDS and NASs to communicate with each other because of confusion in IP changes done by the DHCP server. I ask the DHCP server in my router to assign IP to all my mobile device only.

Most of the time clashed IPs can be resolved by restarting the DHCP server, following the instructions given by Phil and Mike-B.

Agreed static IP addresses are a good thing to have IF you get it right.  But its a bad place to be if something is not correct with discovery & connection issues as in this (& other) case.   I always advise to go back to full DHCP (KIS) & let the wireless routers DHCP management sort it out,  that way you have eliminated a potential problem & if a problem is still around then the IP address issue is not in question.

BTW -  I set "reserved" (fixed) IP numbers in my router for my player, server & control, the numbers are within the ISP licence number range to avoid re-licencing.  However the player, server & control remain set on DHCP.  Its given 100% rock solid no problem discovery reconnects with quite a few power off/on's in well over 1 year.