AC3 access from Internet

[EmDy]

Hello guys, I am having problem setting up the AC3 so I can access it from internet.

DLink dir-655, Verizon DSL internet. I have look over the Ken's site but I can not seem to figure it out.

I am able to access the AC3 via home network from 192.168.0.199 but when I tried to go outside the home network by using 173.67.115.68:1234, unable to conect.

Please help. Thanks.

 

[RussM]

Remove the port forwarding rule. With the DIR-655, you use one or the other for a given purpose... stick with the Virtual Server. Even though the rule you depict in the Port Forwarding section is disabled, it will still conflict with the equivalent rule in Virtual Server.

Make sure the AC3 default router/default gateway is set to the inside (LAN) address of the router (probably 192.168.0.1)

If this is the first time you've tried to use the Virtual Server, reboot the router.

 

[bvoss]

I just had a long struggle with this. I don't know about this router configuration, but what tripped me up was the http setting.

I had to set the http on the AC3 to 1234. I then had to access it internally from my network using http://192.168.1.50:1234/menu.htm.

Then I was able to access from outside of my network using your equivalent of 173.67.115.68:1234.

I hope that works for you. It took me a while to get it right.

 

[EmDy]

guys..still no go. I have been trying this for 2 days now.

 

[Deleted member 143833]

Look at the status screen in the D-Link and verify that DynDns is picking up the correct (public) address and as mentioned.

Since you mention you can connect internally that you changed the AC3 address to 192.168.0.199 and you left the http port set to 80l correct?

Something doesn't appear correct with the DynDns; when I ping aqua.kicks-***.net: I am getting an internal address (not internet address)

 

[RussM]

Ken, I worked with EmDy by phone this evening, and your keen observation of the DynDNS weirdness is just one of multiple anomalous things going on with his router.

 

[EmDy]

Russ, thanks for helping me last nite. My next step is purchasing a new DLink router today after work to see if I still have the problem.

 

[EmDy]

<a href=showthread.php?s=&postid=15582271#post15582271 target=_blank>Originally posted</a> by kenargo
Look at the status screen in the D-Link and verify that DynDns is picking up the correct (public) address and as mentioned.

Since you mention you can connect internally that you changed the AC3 address to 192.168.0.199 and you left the http port set to 80l correct?

Something doesn't appear correct with the DynDns; when I ping aqua.kicks-***.net: I am getting an internal address (not internet address)

that aqua.kicks...is the 3rd one I created since my dlink was never able to stay connected.