@dwalsh62 

Omada, the whole series does not have an option to turn on NAT loopback(AKA hairpin). It's automatically working without a config. 

ER605 V1 has ended its support, but it should still work for NAT loopback. 

The community does not have private support. If you need to contact the email or chat support, go to the official website and seek the support help from the proper portal. 

  @Clive_A  if you say it is always enabled then my device must be defective because i can ping 192.168.0.20 and it works but if I ping the NAT'd address (97.100.200.60) it times out and has 100% packet failure.

You claim it is always enabled and I don't need to do anything but from my perspective, I don't see it working which is why I am frustrated.

Can you tell me another (non wifi) model that has the same functionality where I can add the NAT's and hairpin/loopback just works?

Another thing I noticed when I changed the default DHCP LAN IP to 10.1.100.1 in windows 7 ipconfig shows the assigned new IP in the 10.1.100.xxx range but the reported gateway show 192.168.0.1, if it's just a windows 7 bug I can ignore it but if you say it isn't then I need to address this issue as well.

  @dwalsh62 

dwalsh62 wrote

  @Clive_A  if you say it is always enabled then my device must be defective because i can ping 192.168.0.20 and it works but if I ping the NAT'd address (97.100.200.60) it times out and has 100% packet failure.

 

You claim it is always enabled and I don't need to do anything but from my perspective, I don't see it working which is why I am frustrated.

 

Can you tell me another (non wifi) model that has the same functionality where I can add the NAT's and hairpin/loopback just works?

 

Another thing I noticed when I changed the default DHCP LAN IP to 10.1.100.1 in windows 7 ipconfig shows the assigned new IP in the 10.1.100.xxx range but the reported gateway show 192.168.0.1, if it's just a windows 7 bug I can ignore it but if you say it isn't then I need to address this issue as well.

Firewall settings got a feature called "block ping from WAN". Disable it and try again on that part. I am not sure if that would affect the NAT loopback. I think that's worth a try. 

You wanna test a domain or some kind of web service and you try to access it from the LAN. And use Wireshark or monitor your access log from your web server, see where that connection request comes from. If it comes from the LAN, that means the access is working.

Telnet to test this would be the same way. 

  @Clive_A  I only have one rule in firewall, allow from any to any TCP/UDP 1-65535 and nothing else.

I don't care about blocking or denying anything until I can confirm it (loopback/hairpin) works and can put it into service, so far it doesn't work which is what frustrates me.

Using telnet SMTP into the public IP fails but telnet SMTP into the private IP works.

Without loopback/hairpin functioning putting into real service would be a fatal mistake.because it doesn't function as needed, loopback/hairpin has to work for it to go into service and claiming that the device automaticvally enables it and is functionaing means this can't be true if there is no evidence of it working, this is a logic based conclusion from current testing.

Someone suggested that it needs to be live to work so I installed it, restarted the MODEM and started the TP-Link when it came up and no functioning loopback.

While I was using ping and telnet to test loopback it never works using the public IP's and while it was in a live installation and the machines connected by their static IP's, I did notice that none of the machines could access the admin interface when assigned one of the private IP's but when I changed it to DHCP and it assigned an IP it would access the admin interface.

While I had assigned NAT's for the server IP's, assigning them to the servers showed that I could access the private IP's of all the machines but not one of the public IP's was accessible and oddly not of machines configured with a static private IP could access the admin interface.

This is taking considerable time and guessing on things to try wasting my time and I feel I have been misled into purchasing a device that clearly doesn't work and is not capable of doing what it should be doing as recommended by TP-Link..

Surely their has to be someone in the USA (Florida) who is intimate with these devices and knows how to properly program them without offering guesses I can send it to who can program it, confirm it works and return it for a small fee?

  @Clive_A  So basically it doesn't work, I tried everything you said, from inside the network I am unable to access any of the servers so clearly the ER605 is not capable of hairpin/loopback and it appearts that assing DHCP from 100-199 and configuring 2-99 as static lan IP's doesn't appear to work, not only can't i access the administration interface i can't access anything.

Now i ask again, can someone recommend a device that will work when entering the associated NAT's cause I'm getting tired of devices that don't work?

I've tried a SonicWall TZ-170 and it works (hairpin/loopback) however, it has only 10/100 ports and I need 10/100/1000 or 100/1000 ports, I tried a SonicWall TZ-310 but they changed the firmware and now you have to manually configure everything and they don't give a live example to work from and everyone at dell expects you to buy a $1K service plan (nonsense) to get support so its a no go.

Whatever it is, it has to be easy to configure and it has to work and so far, I've tried several TP-Link products including the recommended ER605 and not one of them works.

If someone in the US can make the ER605 work, I would be happy to ship it to you to configure and pay for the service, I just need a working solution that wont put me in the poor house and is easy to maintain,