url for remote panels

[pwalsh]

Hello,

I've got my remote panels working with computers that are both behind a router.  But when I try to use the url on a computer which is connected to the internet, it doesn't find the server.  I'm pretty sure my problem is that I'm running the LV Server on a computer that is connected through router.  So the router assigns IP addresses to the computer.  If I use the IP address of the router in the url, it still doesn't work.  Does anyone know how to set up a url that will access a server that is connected through a router?

Thanks,

Pat

[chilly_charly]

I'm not a network expert, but I believe that the only way to allow an external connection to a given PC behind a router is to specifically configure the router to redirect the incoming traffic on certain ports to the given PC.
You should discuss this with your network administrator, or if you are using a personal router, you should search the manual for "virtual server".

[altenbach]

---

pwalsh wrote:

I've got my remote panels working with computers that are both behind a router.  But when I try to use the url on a computer which is connected to the internet, it doesn't find the server.  I'm pretty sure my problem is that I'm running the LV Server on a computer that is connected through router.  So the router assigns IP addresses to the computer.  If I use the IP address of the router in the url, it still doesn't work.  Does anyone know how to set up a url that will access a server that is connected through a router?

---

Your problem is not the presence of a router (there are typically tens of routers between any two points on the internet ;)), but the fact that your router is doing NAT.

With the typical M-1 NAT used in home routers, the LAN behind the router contains a subbnet of dedicated private IP addresses, all hiding behind a single public IP address on the WAN side of the NAT router.

For any outgoing connection established from the LAN side, the router creates a NAT session entry and forwards the packet to the WAN using its public IP address as source. Returning packets arriving at the public side are matched with sessions in the table so the packets can be sent to the correct LAN computer that requested it. Of course this poses a problem if you are running a server, because the router has no idea where unsolicited incoming packets should go and needs your help. Go to the router configuration page and look for a menu for port forwarding or similar. Basically you need to instruct the router that unsolicited packets arriving at the public IP with a certain destination port should go to a specific LAN IP address.

Once the port is forwarded, outsiders need to contact the public IP address of the router (remember, private addresses have no meaning on the outside!).