Still No G4 Web Control

TurnipTruck

Greetings, I realize that this has been discussed at great length previously. After viewing some previous threads, I am still having trouble connecting to a panel. All I get is the "No connection to server" message then IE locks up and shuts down.

Here is what I have:

NXC-ME with latest firmware at remote site
NXD-CV10 with latest firmware at remote site
The router at the remote site has 80 and 1319 forwarded to the master, ICSP and master http traffic works fine.
Port 5800 at the remote site is forwarded to the NXD-CV10's static LAN address with TCP and UDP allowed.
Fort 5900 at the remote site is forwarded to the NXD-CV10's static LAN address with TCP and UDP allowed
The panel has G4WC enabled and the port selected is 5900.
The following is in the code:
DEFINE_START
SEND_COMMAND 0:1:7,'G4WC "Living Room TP Remote",10.0.0.22,5900,1'

10.0.0.22 is the static LAN address of the panel.

The "Living Room TP Remote" link comes up on the master's web page, but no connection is ultimately made to the panel after clicking the link.

I CAN view the panel remotely via Real VNC viewer.

Thanks in advance!!

Hedberg

SEND_COMMAND 0:1:7,'G4WC "Living Room TP Remote",10.0.0.22,5900,1'

10.0.0.22 is the static LAN address of the panel.

My understanding is that the IP address you put there needs to be "The external resolvable IP address of the router. This may be replaced by a URL." (from TN 669) If you are getting Real VNC viewer to work, then you must have the WAN IP address (or URL) of the router -- try this instead of "10.0.0.22"

DHawthorne

I only use the browser based web control locally. For remote access I forward port 5900 to that panel and use a VNC client. If access to multiple panels is required, I set up a VPN, in which case the web control page becomes, in effect, local to the connection.

TurnipTruck

My mistake. I put the LAN IP address of the TP in the SEND_COMMAND rather than the public IP of the system. Works fine now.

Real VNC seems to do a better job viewing the panel than does IE when clicking the link.

pdabrowski

TurnipTruck wrote:

Real VNC seems to do a better job viewing the panel than does IE when clicking the link.

because the VNC web interface is a java applet that does the same job as a local vnc viewer process.

I always prefer to use a local vnc viewer over the browser based java applet (plus you aren't relying on making sure that the java runtime environment works properly!)

Denis

Similar problem

Hedberg wrote:

My understanding is that the IP address you put there needs to be "The external resolvable IP address of the router. This may be replaced by a URL." (from TN 669) If you are getting Real VNC viewer to work, then you must have the WAN IP address (or URL) of the router -- try this instead of "10.0.0.22"

To resolve my problem,

If my understanding is good, the resolvable IP address is the IP address from the ISP, wich I can replace by an URL if I use a service similar as no-ip

Sorry but I don't understand what the TN (or you) want mean by resolvable or not resolvable IP address ( sorry for my poor english language)

Hedberg

To resolve my problem,

If my understanding is good, the resolvable IP address is the IP address from the ISP, wich I can replace by an URL if I use a service similar as no-ip

I think that you understand it correctly. What the TN means by "resolvable" is that the IP address can be accessed on the internet. It is the IP address assigned by the ISP (or otherwise assigned). You are also correct that you can use a service (dyndns.org is another one) to update the DNS system so that you can use a URL instead of the IP address. That URL will remain good even when the ISP changes your IP address. Probably you could use the external IP addres/url from inside your network though I think I have had trouble doing this.

Of course, this applies to connecting to your TP from outside your LAN, on the Internet/web. If the computer and touch panel are on the same local network, you would want the local/private IP address (probably something like 192.168.1.n or 172.0.16.n or another IP range commonly used for private networks).

dyndns.org is pretty cool. You can get a free service with one of their domains (you might end up being something like denis.ath.cx) and they provide a small program which will periodically determine your current assigned IP address and update the dyndns.org DNServers if it has changed. The updates take effect real fast

Denis

Thanks!

Thanks Harold. Now it's works fine.

I did a mistake in code, unfortunately, I has put a space between " and , (between panel name and IP address).
Now it's works.

Only one thing, my ISP is blokcing port 80, when I use a PC with an another ISP, the browser dosen't find my Netlinx server, I will have to do a redirection to another port. (I suppose that it will work)

Thanks for your help

Regards