Cannot Access Web Admin from Internet

[UncleJohnsBand]

Hi, thanks for replies.

Yes, that's correct. I can access EWA using localhost or "locally" typing host's IP (in this case 192.168.0.101) into the address field of the browser.

Sorry, by that I meant WAN IP (as x.x.x.x, not host's LAN IP.


Yes, I understand that. What I tried to say, is that if try to access EWA from a different PC on the home network (say, 192.168.0.102) by typing GBPVR's host LAN IP (192.168.0.101), it then won't connect. I will get timeout error.
I can access stream itself from any system on the network, through either typing host's LAN IP or my WAN IP. So, port forwarding definitely works. Just not for web interface.

Port Forwarding seems to be set up correctly - see attachment. I can access BeyondTV's web interface using localhost, or from any other PC on the network or WAN IP (Internet) or my smartphone.
As you can see GBPVR is set up exactly the same, yet I have the problem with accessing the interface from any other location, except for host PC.

Sorry for my rush post, that became confusing in details.

Thank you for your time trying to help me!

Ok....Have you simply tried stopping and re-starting the gbpvrrecording service on the GBPVR host PC? There are some (including myslef) that have to restart the recording service everyday because of some sort of hang issue that occurs in the web server that runs out of that service.

[globaltrasher]

Ok....Have you simply tried stopping and re-starting the gbpvrrecording service on the GBPVR host PC? There are some (including myslef) that have to restart the recording service everyday because of some sort of hang issue that occurs in the web server that runs out of that service.

Hate to say it but yes, I've been through that, adn reinstalling the plug-in, etc. I've been fighting with this issue whole weekend, and can't figure out how to make it work...

I even changed the port to 8129 (as BeyondTV), but that makes no difference, so I assumed it can't be the router. It's got to be something with the EWA, right? Or there is something else I can try? I'm out of ideas myself

[UncleJohnsBand]

Hate to say it but yes, I've been through that, adn reinstalling the plug-in, etc. I've been fighting with this issue whole weekend, and can't figure out how to make it work...

I even changed the port to 8129 (as BeyondTV), but that makes no difference, so I assumed it can't be the router. It's got to be something with the EWA, right? Or there is something else I can try? I'm out of ideas myself

Ok...have you tried the simple external port check tool to see if your port is visible externally?

Also...is there anything in the Logs from EWA? You can view them from the statistics tab.
[URL="http://www.yougetsignal.com/tools/open-ports/"]
[/URL]

[globaltrasher]

Ok...have you tried the simple external port check tool to see if your port is visible externally?

Also...is there anything in the Logs from EWA? You can view them from the statistics tab.
[URL="http://www.yougetsignal.com/tools/open-ports/"]
[/URL]

Hmm... According to this tool, 7647 is closed and 8129 is open. Yet, as I mentioned above even if I configure EWA to be accessible through 8129, it still doesn't work... On top of that, even if I set the port forwarding to any other port, e.g. 8128 or 8120, the tool would still say that those ports are closed, but 8129 is always "magically" open... Man, this is getting weird...

I looked over the log, and nothing sticks out...

[UncleJohnsBand]

Hmm... According to this tool, 7647 is closed and 8129 is open. Yet, as I mentioned above even if I configure EWA to be accessible through 8129, it still doesn't work... On top of that, even if I set the port forwarding to any other port, e.g. 8128 or 8120, the tool would still say that those ports are closed, but 8129 is always "magically" open... Man, this is getting weird...

I looked over the log, and nothing sticks out...

Are you sure you opened those ports on the local firewall on the GBPVR host PC? Double check.....I have seen them get closed on the local machine.

You would need to shut down your other app running on 8129 since it is probably picking up the incomming call on that port rather than EWA.