Cannot ping ER605 from outside network
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi There,
I've been having problems being able to connect to my business network from outside the office, and as far as I can tell it is ever since I applied a dual WAN (load balanced).
This is on anER605 V2.0 running 2.1.4 Build 20230727 Rel.40308 directly connected to 2 operational WANs. I am not using Omada.
I thought this might be a bug as mentioned on the forums: https://community.tp-link.com/en/business/forum/topic/602186 (As I could not port forward any more)
But it turns out even with the beta firmware installed I cannot ping my network at all, let alone apply a port forward rule that used to work perfectly fine a couple of weeks ago.
Just to be clear, no configuration has changed from what was working perfectly fine prior, apart from applying a second WAN, (with load balancing), and then the beta firmware update to no avail. I have some Cisco rack switches on the network which I don't believe is relevant as this was all working perfectly fine prior to applying the dual WAN.
I've applied a rule to force my server PC to use only one of the WAN's per here: https://community.tp-link.com/en/business/forum/topic/582470
but this has made no difference to pinging or port forwarding ability.
www.whatismyip.com gives me my device public IP, which used to work perfectly fine for pinging and port forwarding before I applied the dual WAN, but now I can't even ping that IP externally. Same applies for the second (new) WAN.
My WANs are (Aussie) NBN and Starlink.
What's most interesting is that the Starlink IP shown on the ER605 status page does not actually match what is shown in www.whatismyip.com from a Starlink connected device, whereas the NBN WAN correctly reports the IP address in the settings. Is this part of the problem? This seems really strange to me.
I've applied matching Google/Cloudflare DNS to each WAN so as to skip the ISP settings, also making no difference,
Does anyone have any clever ideas?
This is forcing my team to not work from home properly as I can't get them connected to the server software they need without the port forwarding in place!
Also, anecdotally, a member of my team thinks they can intermittently (but rarely, like once every 30 minutes or so) connect to the server properly for a very short while, before the connection goes dead. I'm not sure if this actually is true or makes sense... but...shrug??
Thanks for helping!
1. Port forward settings are here (unchanged from working setup):
Macbinds here if needed:
I verify the port forwarding by attempting to connect externally via my CAD software, which used to work perfectly fine but since dual-WAN does not.
2. No firewall settings changed, but admittedly before this problem occurred I had not attempted to ping the server externally before. I've now updated that firewall setting you recommended and I can now ping the server... Thanks! I also relaxed the server firewall ICMP settings but this didn't seem to make a difference.
3. OK understood. I suspect the Starlink is behind a double NAT! Nonetheless I can't seem to do anything about that. The Starlink is woeful anyway but 'higher-ups' put that in place.
Nonetheless, as far as I can tell within my office just now (using mobile hotspot on a laptop instead of internal network) I can now connect to the server via the port forwards.
I will properly check this later from home to ensure the system is working correctly.
I'm unsure why that simple ping firewall setting would have stopped port forwards from going through, but nonetheless if that's all it was, so be it and thank you!