True'S Nlink Modem/Router Cannot Open Port To Remote View Cctv Dvr

[tangcoral]

I know the Nlink is not very good but I dont want to have to buy another modem/router if I dont have to.

I am trying to view my cctv unit remotely.

I logged onto the Nlink admin page and set the virtual server (port forwarding is it?) as shown below.

WAN Port 80 Server Host Port 6000 Server IP Address 192.168.1.15

Name: AUTH Protocol:TCP

When using my iphone to log into the cctv dvr I get mesaage "not allowed use restricted network port"

or from a remote computer using chrome browser "Error 312 (net::ERR_UNSAFE_PORT): Unknown error."

I utilized a site that had a open port checker and only port 80 is open while port 6000 and pretty much every other port is closed

Am I suppose to fiddle with the IP address mapping or DMZ or anything else?

Maybe the setting on the DVR network is incorrect like the DNS server but I dont think it is incorrect

Hopefully I'm doing something wrong here and not the modem/router's fault

side note: using dyndns to combat dynamic ip

I have True internet

I set the Firewall on the router to allow both "incoming and outgoing action"

Let me know what other info I fail to mention.

Lastly any cctv expert that I can ask for dvr recommendations like dahua or hikvision sold at pantip in bangkok.

[Dork]

You need to set the external port (or WAN port) to 6000 as well. Don't use port 80. Then to access from the internet enter :6000 after your DYN domain name (eg http://abc.dyndns.org:6000)

[tangcoral]

I tried that way before and still a no go..

does using 6000 have anything to do with the issue? Should i use a higher value like 40000 or 55000

[Dork]

No, the port number doesn't matter as long as it isn't one of the few "common ports" especailly port 80 which is for "http". Port 6000 will be fine.

You need to trace the fault methodically. I doubt that there is anything wrong with the router. The logical order is to know the CCTV's internal IP address and port number that it listens on. Then the router has to map that internal IP address and port number to the external (WAN) interface and port number. Then DYNDNS points your domain name (eg. abc.dyndns.org) to the dynamic IP address currently assigned to your router by your ISP.

1) You said that the LAN address of the CCTV unit is 192.168.1.115 and it's host port is 6000. Are you sure this is correct? From your PC on the LAN, if you type 192.168.1.115:6000 into your web browser, does it work? If yes, continue.

2) In the port forwarding section of your router enter the following. The terminology can vary from router to router but you can figure that out.

Name of service or application:CCTV

WAN (external) port: 6000

Protocol: TCP/UDP

LAN (internal) ip address: 192.168.1.115

LAN (internal) port: 6000

Enable: Yes

3) In the DDNS section of your router, make sure all your DYNDNS info is correct. There should be some kind of message telling you that it is updating ok. From another internet connection (not the one you are using) can you "ping" your DYNDNS domain name and does it come back with the correct IP address which is the WAN IP address your router says that it has been assigned by your ISP.

If all the above are ok, it should work. It has nothing to do with the firewall on your PC. Also try a different web browser - IE, Firefox, Chrome or whatever.

Look forward to hearing the result.

Cheers

[Dork]

One more thing. If you have been playing around with other settings on the router trying to get it to work, it might pay to reset the router to factory and start from scratch. It is easy to inadvertantly do something wrong. Don't touch network mappings or DMZ. Leave them at the default setting.

[tangcoral]

Thank you dork for the thorough step by step explanation.

Whats perplexing is that I have done this to 3 other remote computers in US and thailand without a hitch.

By no means I am an expert but am semi comfortable enabling this feature.

I did all the basics steps you have listed again with restart to default on modem and still having the closed port issue.

I swear it might be an issue with True blocking ports but heard somewhere they dont block.

Or its got to be my router or other hardware...networking can be a bit frustrating if your not an expert.

Anyhow I'll figure this out somehow and post my results when I succeed..thank you again all!

[Dork]

Thank you dork for the thorough step by step explanation.

Whats perplexing is that I have done this to 3 other remote computers in US and thailand without a hitch.

By no means I am an expert but am semi comfortable enabling this feature.

I did all the basics steps you have listed again with restart to default on modem and still having the closed port issue.

I swear it might be an issue with True blocking ports but heard somewhere they dont block.

Or its got to be my router or other hardware...networking can be a bit frustrating if your not an expert.

Anyhow I'll figure this out somehow and post my results when I succeed..thank you again all!

I'm sure it's not TRUE blocking ports. I've had various TRUE ADSL connections for years and I've never seen that.

I recall once having a similar frustration to yours and it turned out to be that the DYNDNS address wasn't being updated even though the router said that it was.. You could try checking that by entering "what is my ip" into google from a PC inside your LAN. Then take that IP address, add the suffix :6000 and enter it into a web browser from somewhere outside your LAN (eg 125.25.132.93:6000)

[tangcoral]

Yeah I by passed using the dyndns url and used my current IP address with no luck. Some reason my port 6000 is not opening up.

Maybe its something as simple as ticking and option somewhere on the router gui allowing it to enable it. I dont know...en

EDIT: when I input port 6000 into the "access control management" to log on to the routers gui I am now able to see that the port is open when using canyouseeme.org

Before it kept saying port closed, but this will still do me no good since I am not attempting to log onto my router's gui.

[tangcoral]

update:

SUCCESS!!

Not sure why as I have never needed to do this with other locations but I changed the DNS primary server 1 and DNS primary sever 2 to what was listed on my routers WAN status for DNS server.And now its showing up "open" and I can remotely connect to my dvr.

Strangely I didnt have to do this with any other dvr devices but maybe this router needs this info?

hopefully this DNS sever value isnt dynamic or changes, do you know?

[Dork]

EDIT: when I input port 6000 into the "access control management" to log on to the routers gui I am now able to see that the port is open when using canyouseeme.org

Before it kept saying port closed, but this will still do me no good since I am not attempting to log onto my router's gui.

Sorry, don't quite understand what you mean. Do you mean that when you try to access from outside via port 6000 you are taken to the routers gui?

[tangcoral]

I re-read what I wrote and it sounded as if I logged on to my web gui.

Let me re write it:

I went to the "routers access service" tab and changed the ftp port to 6000 just for the heck of it.

And yes I was able to see 6000 open instead of the constant close status.

Hopefully that made better sense.

And no I didnt get the routers web gui.

After thinking about dvr's DNS server value being the issue. ..I think the problem may been that I had the dvr set in "static ip" mode instead of "dhcp ip" mode. Thus the dvr's dns server value wasnt updated automatically. I manually inputted the assigned ip value and didnt change the dns server 1 and 2 value.

[Dork]

That's great. I know how frustrating it can be. At least it works now.

Don't worry too much about TRUE's DNS servers. They're not likely to change anytime soon.

Cheers