Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[AustinBike]

Having trouble getting the webgizmo working on my server.  

Initially I was having problems getting it to work inside or outside the network.  Then I loaded the most recent update and now it works internally.  So this tells me that this functionality is working.  So it is not an application issue.

I am running on Windows Home Server 2011.  I know that the firewall can speak to the server because I can do a remote login and access the server remotely over the web.  So clearly I have a problem opening up the right port.

I went into port forwarding and have a JR setting to open up 52199 (both TCP and UDP) that point back to the server IP.
I use static IPs
When I go to the JR site and put in my 6-digit code if I say I am in the network, it accesses fine.   Outside of the network it will not access it.  It does pull the proper IP address.  If I type in external IP address (216.188.x.x) with :52199 I get nothing.  If I put in :80, I get the remote access.

Any thoughts?

[JimH]

I had a similar problem, and it turned out port forwarding wasn't enough.  I had to enter the ports in something called "Port Trigger".

[AustinBike]

Thanks.

Setting the port triggering is done and now, from a 404 error, I get a timeout error and a 404 error.  This is pretty frustrating, the remote access was the key feature that I wanted for MC, that allows me to not have to use some cloud service to hear my music when I am at the office.

[JimH]

Try opening (in port triggers) 52190 through 52199.

Please report your frustration somewhere else.  It doesn't add anything here.

[AustinBike]

52190-52199 are all forwarded
52190-52199 are all triggered

Still get nothing outside of the network, can access it from within the network.

[JimH]

The forwarding isn't required inside your network.

The wiki has a topic called "Network Access".  You might find something there.  Your router manufacturer's site might also help.

[InflatableMouse]

Take a look here.

This is not a problem with JRiver but with your router and possibly your pc and its local firewall.

[AustinBike]

The answer was nuclear.

Rest to factory settings.

Then, on a DIR-655, go into virtual server ONLY.  Don't touch port forwarding or application (port triggering).  That has it working now.

Now all I need to do is go back and reset all of my other settings.  Hopefully none of those was the culprit.  At least now that I know it works I can troubleshoot a change.

[UltraMagnus0001]

I have these ports open 52199, 1900, 52100-52107