This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.
Quotemy netcat rule . defined that it can connect all the public , private , domainsWhat I mean when saying "scope" is if the "Remote Address" for rule "Netcat" and for both the other "nc.exe" rules is "Any address" or just "local subnet". It should be "Any address" if it shall be reachable from the Internet.
my netcat rule . defined that it can connect all the public , private , domains
Btw. How do you test if it works from the Internet?[1] From a client really sitting in the Internet?[2] Or from a client inside your LAN that connects to your external IP 175.101.67.138:9891?[2] might not work, if your DIR-600L doesn't support "Hairpinning".
u]PC 3rd Party Security Software Configurations[/u]Turn off all anti virus and firewall programs on PC while testing. 3rd party firewalls are not generally needed when using routers as they are effective on blocking malicious inbound traffic.
Just to be sure it is not the Windows firewall causing the problems, you could switch it temporarily off and test if the nc connection works in this case.
Instead of PORT FORWARDING you could try "VIRTUAL SERVER"
Sorry, you are right - VIRTUAL SERVER is not available for DIR-600L.But, since you do not really have a port range but a single port only, maybe you have to express this by writing 9891 ~ ____instead of 9891 ~ 9891Just a last stupid idea ...
Look at ADVANCED | Firewall & DMZ !It provides the opportunity to configure firewall rules. I guess you have to specify one for inbound TCP port 9891 (Source WAN 0.0.0.0 - 255.255.255.255, Dest LAN 192.168.0.101 port 9891, proto TCP --- or perhaps "Dest LAN 175.101.67.138 port 9891, proto TCP" if the rule is effective before NAT is done)
Try 0.0.0.1