APEX & AC3 on Actiontec modem/router

Meitzler

Member
Having a problem setting WAN (remote) access up for both of these on an Actiontec modem router on verizon. Using port 80 for one and 8080 for the other. Both work fine on the LAN. Only the AC3 will work on the WAN on port 80 or 8080. I moved the APEX to 80 and still can not get it to work. Did port forwarding for both devices. Any recommendations?
 
Just guessing here but did you change the Apex to use a static IP (the default is DHCP).
 
Once you set the AC3 and Apex to use fixed IP address you can then setup port forwarding so that both the AC3 and the Apex use Port 80.

e.g. you can forward port 80 coming into your router to the AC3 IP Port 80 and port 8080 coming into the router to the Apex port 80.

Assuming your router is not on a fixed IP address, if your router is configured to run dynamic dns - like DynaDNS - and you have port forwarding setup, you can access both the AC3 and Apex from outside your home network.

AC3 - http://yourname.homeip.net
Apex - http://yourname.homeip.net:8080

By using different ports to access your router, your router will direct the associated traffic to and from the device that that port is forwarded to.

This may seem a little confusing at first but if you have a decent router it works very nicely.


Paul
 
Please note that I confimed that DHCP is off on the APEX. Also, local access of both works fine within my LAN. Only the APEX access fail from the WAN/Internet. My router is an Actiontec GT724WGR connected to a Buffalo Ethernet Converter WLI-TX4-G54HP. Again, both work fine local, and the AC3 can be access via the Internet, but the APEX fails with a network Error (tcp_error) Connection Refused.
 
Make sure the the default gateway on the APEX is properly set to the inside (LAN) IP address of the router, and that the subnet mask is correct (usually 255.255.255.0 for home networks).

In all of your testing so far, has the APEX always been connected via the Buffalo wireless adapter? If so, try eliminating the Buffalo just for testing purposes (move the APEX or use a long CAT5 patch cable to connect it directly to the router)
 
Confirmed the subnet mask 255.255.255.0 and the IP address is 192.168.0.1 which is the router. Are the DNS IPs a factor? Will have to find a longer CAT 5/6 cable since they are too far apart.
Thanks.
 
The DNS IP addresses are used only when the controller sends email.

Something definitely doesn't add up here. Can you also post screen shots of the NetSetup pages of the AC3 & Apex, and of the router's port forwarding page, and the custom rules you created?
 
I finally did get it to work, but it is fraggle since I do not clearly understand why. I am still using port 80 and 8080. The fix was to move the APEX directly to a router ethernet plug. Then I had the router remap the network. Once that was done I could get it to work. Then I moved it back to the Buffalo Ethernet Converter and it continued to work on the wireless channel. I did not change any paramenters in the APEX, AC3, router, or Ethernet converter. Haven't had the courage to turn the power off the device and see if it will continue to work. Thanks everyone for your thoughts, since they definitely helped me get this far.
 
Back
Top