We have been purchasing and deploying R-200 routers since they were introduced.
We have a configuration file (using NAT and static WAN AP's) saved on one of our PC's that we use to upload to each R-200 new router before it is deployed.
After we upload our saved configuration file, we change the static IP address for the WAN, the wireless name and password in the new R-200 router, reboot and test the router for proper operation - then install the new router at the customer's location.
The last batch of routers that we received (and have been trying to configure by the same method for several hours) will not pass data in the NAT mode after being configured.
In addition:
You also cannot ping any WAN addresses using the Ping function on the Administration, Device page.
You can communicate with the router via a LAN PC.
You can communicate with the router via the 2.4 Ghz Wireless.
You can ping the router from the WAN.
You cannot log into the browser via the WAN.
On the Network WAN page on the new R-200 routers, there are Port Binding items that show up on the bottom of the page.
Those settings are not there on the bottom of same screen of the earlier R-200 routers.
Firmware is the same in both routers - latest firmware Version 4.2.3-R4
Shown below is the pertinent information from both the old Router and the new Router.
Older R-200 Routers
Hardware Version V1.2
Loader Version V3.07(Aug 20 2015 17:38:07)
Firmware Version 4.2.3-R4(201606031245)
Device-Agent Version 2.36
New R-200 Routers
Hardware Version V1.2
Loader Version V3.08 (June 16 2016 15:58:44)
Firmware Version 4.2.3-R4(201606031245)
Device-Agent Version 2.36
Why are we having problems configurating the new routers?
In my opinion, with the same firmware version loaded in the two R-200 routers, the two Network WAN screens should look the same. Why are they different?
Is the difference in the Loader Versions causing the configuration problem and the difference in the two Network WAN screens?