Serviio

I am having a problem with remote access. My internet is through a "mom and pop" kind of place since I'm in the country. Anyway from my router it goes to other routers outside of my control. Previously I had WHS 2011 and my ISP forwarded ports 4125,80,443 for me to get that to work however WHS 2011 crashes all the time so what I have done is install Windows 7 Pro and Serviio fresh on a machine and that's it. Now how I went about setting up remote access was I set my computer on a static IP then I went into my routers settings (Linksys WRT1900AC) and manually forwarded all those ports 4125,80,443 from external to the internal port of 23424 using TCP and pointing to the static IP however this is still not working. I also have UPnP enabled. Any ideas???

23424 is the only port I have forwarded. I can open it from my iPad with no issues, although its 3G connection is so pathetic I have to connect it to my MiFi to ever hope loading a video to watch. UPnP does nothing outside your firewall/router.

Also remember that you need to use more than a basic URL. It has to have the complete path, including port: http://your_public_ip_address_or_FQDN_h ... diabrowser

What address are you using when trying to access it remotely? You don't need to include your IP or FQDN if you don't want to publicize it. You aren't trying to use your internal IP address, right?

No, I have a web address like www.blablabla.com and where I got that I have it pointed to what is supposed to be my public IP and with WHS 2011 that worked just fine. and I have 23424 forwarded in my router and going to my static IP of my server. HOWEVER when I check my IP on google or see it in Serviio it's not what my ISP told me my public IP was nor is it the one I have www.blablabla.com pointing to. I also went to checkmyopenports.com and I only have 4125 open so I even tried to forward external 4125 to 23424 inside my router. I'm stuck now????

If I'm understanding your network layout correctly, the "public" IP address at your router is not the real public IP. Since I don't know what DDNS service you are using, I can't make a specific recommendation. I use DNSEXIT.com, and the client I run on my server reads my actual public IP address and sets it in the public DNS servers.

Does your ISP give you a static public IP address? If so, it sounds like it may have changed. Use www.whatismyupaddress.com to see what it really is, and compare it to the address you were told. If they match, then ping your FQDN and see if the same IP comes back. If they don't match, then you have a DNS issue that has to be resolved by whoever assigned your FQDN.

No they do not match and from what I found out I have a double NAT set up.

Yep, you have a DNS issue. Get that resolved and you should be good to go.

Yep, that's why I posted this. HELP! LOL

Dear freind

At the fisrt you neet to go in the firewall of your modem check SPI -------> Disable
after go to your modem NAT menu add a virtual server to forward the port 23424 to the adress of you wan router maybe 192.168.1.2 , you can check this adress in your router (wan adress). MODEM ----> NAT ----> PORT 23424 ---- > IP WAN ROUTER
After that open the port 23424 ----> IP SEVEUR SERVIOO or check if UPNP is activate in your router and selected on servio. ROUTEUR ----> PORT FORWARDING ----> PORT 23424 ----> IP SERVEUR SERVIIO.

100 % WORK

if you have any trouble try to check you PC firewall

Good luck.

Mr Firewall, he already has the port forwarded. His issue is because of double NAT. Checking for SPI may be worthwhile, but I think your suggestion would complicate his matter more.

Zombie, sorry I overlooked your thread and haven't responded.

Now, with your layout, I'm not certain what we can do about it, unless your ISP is willing to add an A record to their internal DNS servers that points your public FQDN to your ISP assigned public IP.

So, for Serviio to work, you need your public FQDN to point to your ISP public IP address, then the ISP needs to direct that same address to the IP address they provide you. Then your router takes it and sends it to your Serviio computer. The only port you need forwarded for Serviio is 23424.

Are you running the 10.114.159.x address block on your internal network? That's an odd choice. Just want to make sure your forwarding settings are correct. You sure your internal addresses aren't in the 192.168.x.x block? Virtually all routers for home use are in this address range.

If 10.114.159.x is NOT your internal address range, then we have discovered the problem. So, just to be sure, check the IP address on your Serviio computer and post it here. Don't worry about someone connecting remotely and hacking you, Internal IP addresses will not route across the Internet. That's why there are specific IP addresses for networks inside the firewall.