Typically you will get far more stability if you 'fix' the ip of your nas.
there are a couple of considerations,
firstly on your router settings you can establish if you can simply reserve the ip for the nas, if this is possible do that.
if not in the router settings will be the dhcp server with a range of addresses, you do not want to give your nas any in this range.
you will also need the ip of the router, the dns addresses it uses and subnetmask. The subnetmask is typically 255.255.255.0
on the nas find the network settings which will probably be set to dhcp. Set this to manual, give it an ip that was out of the dhcp range, so for instance if the range for dhcp was 192.168.0.2 to 192.168.0.200 then give the nas 192.168.0.201 on wards.
it will also ask for the subnetmask, and the mainserver/router, which is your routers ip.
finally it will require dns addresses, if your router did not supply any put in the routers address as a dns addy.
apply those settings. Because you will have changed the nases address you will need to log back into the nass at the new address you specfied.
this all seems complicated, so ideally if you can find the routers ability to reserve an ip that would be easier in which case it will present a list of connected devices, you need to determine which is the nas, (the nases network settings will show what ip its on) and reserve it.
once you have achieved one of the above methods your nas will now always be on an expected address, the upnp server will therefore be broadcasting its database (twonky) on that address and likely you want have any more issues.
you can fix the ip of the uniti as well, though this s only an issue if nstream has trouble finding it.
remember every device on your network has to have a different ip address, and if you are really not confident doing the above fi d someone that is, because when devices drop,off the network because of incorrect settings they can be a pain to refind!
