Major update to my issue (fingers crossed). My Meraki MX250 setup is still not in production, as I really can't move it there until I get this particular issue with 1:1 NATs fixed. I was starting to think the issue was based on 1:1 NAT problems. A Meraki engineer found that my internal server was not showing up on the ARP table (this was a day after the last test hour I used to fix this.) And, stated that a 1:1 NAT won't even try to work unless the destination is in the ARP table. I'm wondering if there is a length of time needed for some machines to properly be entered into the ARP table on the Meraki? I usually only have about 1 hour of time for testing production equipment (i.e. allowed down time) and within that time my testing of the final production destination machine never answered calls. However, I put a simple IOT device into the test environment that the Meraki is currently in, and it also failed 1:1 NAT setup calls to port 80 and 443 initially. But, I left it there and after 24 hours I tried again and it worked. I can't say the amount of happiness of this discovery is overcoming the frustration in getting to this point is a positive for me yet. But, hopefully I can find a way to setup my Meraki into production with the final destination in place and working. I just don't know 1. why the machine didn't show in the ARP table within the 1 hour, and 2. how long should it take?
... View more
