having trouble accessing from outside

[UncleJohnsBand]

not bothering with streaming

The 7647 one says 'success, we can see your service running' etc.

Can get to this pc from others on the network now, just having trouble doing it externally... what exactly should the URL be? its really not clear...
If i try to log into my ip, i can log into my router... but redirection of ports doesnt seem to be working as expected.
Thanks for the help thus far

How is this going? elite's info below is correct on getting the correct IP to access from outside the network.

http://YOUR_EXTERNAL_IP:7647/gbpvr/index.aspx

Where 7647 is the port specified in the config app and forwarded in the router

To get your external IP visit http://www.whatsmyip.org/ or similar

Some routers do not support loopback so you may not be able to test your external connection from within your local network - set it up and try it from elsewhere...

HTH

[angusmccloud]

So I've been trying to get the webadmin working for awhile...
I can login from the local machine, but not another computer on the network, or a computer on a different network...

I have it setup going through port 7647.
I set my Linksys WRT54G to forward ports 7647 and 7648, and I believe they're both for the right machine (192.168.1.102, which is what is appearing in the network connections details for my desktop).

Then if I try to go here: http://155.48.144.19:7647/gbpvr/Login.aspx, it doesn't work... the 155.xxxx number is what I get from whatismyip.com
I know i should set up dyndns, but I want it to work period before worrying about the ip address changing...

I love this program to death, and really want to get this part working. Any help would be greatly appreciated

[UncleJohnsBand]

So I've been trying to get the webadmin working for awhile...
I can login from the local machine, but not another computer on the network, or a computer on a different network...

I have it setup going through port 7647.
I set my Linksys WRT54G to forward ports 7647 and 7648, and I believe they're both for the right machine (192.168.1.102, which is what is appearing in the network connections details for my desktop).

Then if I try to go here: http://155.48.144.19:7647/gbpvr/Login.aspx, it doesn't work... the 155.xxxx number is what I get from whatismyip.com
I know i should set up dyndns, but I want it to work period before worrying about the ip address changing...

I love this program to death, and really want to get this part working. Any help would be greatly appreciated

Did you open ports 7647 and 7649 on the PC hosting GBPVR/EWA.....you need to open these two ports in Windows Firewall or whatever firewall you are running on that host PC.

[pastro]

I have it setup going through port 7647.
I set my Linksys WRT54G to forward ports 7647 and 7648, and I believe they're both for the right machine (192.168.1.102, which is what is appearing in the network connections details for my desktop).

What UJB said about the firewall is probably the trouble. For quick tests I find it easy to just turn off the firewall so I can determine if that's the cause.

You should also be able to log from another machine into : http://192.168.1.102:7647/gbpvr/Login.aspx.

[angusmccloud]

Yeah it was the firewall...
I figured it had to be something obvious, and I was just being stupid...

Thanks!

Now I just need to setup dyndns, and VLC and I'll be all set!

[Kevina]

Just thought I would add my experience to the list in case it helps someone else. I was having the same problem as angusmccloud in that my EWA worked just fine inside my LAN, but I couldn't hit it from work. I was using the default 7647 and had everything configured correctly in my firewall and router, but no go.

After beating my head against the wall, I finally figured out that the problem was not on my end at all. They had the firewall at work configured to block almost everything but port 80 traffic. So the solution was to reconfigure my router to listed on port 80 and redirect the traffic to the internal 7647 on my GBPVR server. I had wanted to keep the obscure port for increased security (you know, security through obscurity!), but it just didn't work out that way.

After changing to port 80, all is well. I hope this helps keep someone else from pulling all their hair out!

Kevin

[UncleJohnsBand]

Just thought I would add my experience to the list in case it helps someone else. I was having the same problem as angusmccloud in that my EWA worked just fine inside my LAN, but I couldn't hit it from work. I was using the default 7647 and had everything configured correctly in my firewall and router, but no go.

After beating my head against the wall, I finally figured out that the problem was not on my end at all. They had the firewall at work configured to block almost everything but port 80 traffic. So the solution was to reconfigure my router to listed on port 80 and redirect the traffic to the internal 7647 on my GBPVR server. I had wanted to keep the obscure port for increased security (you know, security through obscurity!), but it just didn't work out that way.

After changing to port 80, all is well. I hope this helps keep someone else from pulling all their hair out!

Kevin

Thanks for the tip....I am sure people will find it helpful.....I am seeing more and more businesses block ports.....