Serviio stops working after router upgrade

Little confused about the source, destination, and the IP ranage. Thanks

snowflake7 wrote:Not sure of your configuration, or which functionality you are referring to. If you are attempting to use the media browser or any connection that relies on ports being open (specifically 23424) you may have had a port forwarded on your old router. The new router may not have the port forwarded and/or the ip address of the serviio host assigned by the new router may not be correct in the forwarding table on the new router. (See http://serviio.org/component/content/article/10-uncategorised/59-mediabrowser for general guidance.) You can rule out the firewall by connecting via the "localhost" method on the serviio host computer. If you can't connect that way it is not a firewall issue.
Generally speaking, I disable the firewall on my consumer based routers and disable upnp except when configuring a new app or device. I then manage the ports I want open manually through forwarding rules. I find that software firewalls are much easier to manage and I have been surprised too many times by what ports upnp opens.
DenyAll wrote:It's a little unclear of where you are experiencing your problem:If access internally is a problem then (work down this list, testing at each point):
- If it is trying to access Serviio from outside of your network (away from home), then as snowflake7 has stated that it is likely a port forwarding and/or firewall issue.
- If it is trying to access from inside your home network, then it is will not likely be related to port forwarding (port forwarding enables external traffic to get into your network, and doesn't normally affect internal network traffic).
If still not working, post a detailed log and we can see if that helps uncover the problem.
- Ensure your router firmware is up-to-date. The latest WD 750 firmware (http://www.wd.com/wdproducts/updates/?f ... fmynetn750) has some fixes effecting DLNA support (seems to be for their own internal server, but may be relevant);
- Turn off all firewalls for now - both on your router and on your server (the PC serviio is loaded on);
- Are all devices on the same router (there are no other switches or routers on your network)? If not, try putting everything on the same device (as a test -we can come back to it);
- Are all devices on the same transmission media (are all wireless, or all ethernet cable) ? If not, try putting everything on the same media (once again, as a test - we can come back to it);
- Try changing the state of the following in your router (if off, try turning on and visa versa) - you may not have options for the last two:
- UPNP
- IGMP Proxy
- IPV6 Multicast
- IPV4 Multicast
- Has Serviio detected your devices (on the status tab). If these were already there before changing router, try deleting one and seeing if it gets redetected.
snowflake7 wrote:I am assuming that you are attempting to access serviio remotely.
What is the IP address of the "dlna media server" In the user manual for your router there is a section "enabling port forwarding" under advanced tasks. You need to be sure that a rule is created to forward port 23424 to the IP address of your dlna server. beginning and ending ports are 23424 and TCP should be sufficient. I don't think you have a firewall issue.
As I stated b4 I don't use upnp. If it is enabled on your router servio may automatically assign the port to the IP address. That is a question someone else may have a stronger knowledge.
If you are connecting from outside, your router needs to know what IP address on the subnet is going to answer to a request for the specific port. A port forwarding rule will establish the road map.
Return to Serviio Support & Help
Users browsing this forum: Google [Bot] and 31 guests