View Full Version : Argh.. Internet access problems
tmgrash
02/23/2014, 08:54 PM
I previously had an apex for about 5 yrs. it ran great and had internet access until it randomly bricked. So I bought another. I can't get internet access. Static ip is set. Port forwarded to 9999. Dyndns is set up same as before to same addy. Router is set to port forward to 9999. Everything exact same as before. Used same ip and ports for everything as before but this one can't be accessed through Internet?
Any suggestions?
revnull
02/23/2014, 10:50 PM
Have you acknowledged your dyndns account recently? Since they changed to the for-pay model, all old free accounts that were grandfathered in need to be verified every 30 days or they expire and become disabled.
tmgrash
02/24/2014, 09:04 AM
Yes I went ahead and paid for dyndns after nearly lapsing several times. Any more thought anyone?
kurt_n
02/24/2014, 01:38 PM
And you're putting your port number after your dyndns address, correct? (mydyndnsaddress : port_number)
What kind of message are you getting when trying to access it?
tmgrash
02/24/2014, 03:59 PM
Yes Kurt port is put after the address. It says the page cannot open because the server isn't responding
kurt_n
02/24/2014, 05:34 PM
But you can access it fine locally, correct?
tmgrash
02/24/2014, 07:49 PM
Yes local access is no problem. This is why I'm confused. When trying to access over internet it acts as though the apex isn't responding. But responds fine at home network
kurt_n
02/24/2014, 10:13 PM
I have a hunch you've tried all this, but it doesn't hurt to ask!
What if you try external access using your actual external-facing IP address, and not your dyndns address - just to rule out dyndns? Can you access it that way?
I'm not a network engineer, never played one on TV... but HAVE stayed at a Holiday Inn Express... but it seems like if you can access it via your internal network, then it's not a problem with the Apex or the Apex's internal webserver. Seems like it's pointing to something with the dyndns or router/port forwarding. Are you *sure* nothing has changed in your router? You're not running a router behind a router, are you?
tmgrash
02/25/2014, 09:59 AM
Hmm. Just tried using the actual outward facing ip and that didn't work. Now that you mention it though the only thing I have changed was that the cable company sent me a new modem. And I believe this new modem can be used as a router as well, even though I don't have it setup that way. All I did was unplug old modem and insert new one. Wall to modem to router. If this was the problem wouldn't it also be a problem with local access? Isn't the when I access locally doesn't the router send me to the ip and port I put in? Apparently it's been too long since I've stayed at a holiday inn express
revnull
02/25/2014, 10:21 AM
If the new modem is also a router, the external port is not longer forwarded.
Normally the access path is:
{Internet} -> [ISP] -> [Modem] -> [Router \w firewall, Gets external IP from ISP] --Port Forward--> [Apex, Gets internal IP from router]
You may now have:
{Internet} -> [ISP] -> [Modem/Router \w firewall, Gets external IP from ISP] -> [Router \w firewall, Gets internal IP from modem/router] --Port Forward--> [Apex, Gets internal IP from 2nd router]
Internal still works because you are all still connected to the 2nd router internally. Externally, the "ball" gets dropped at the new modem/router as there is no rule to forward the request from the new modem to the "old" router.
In this case, you have 2 options. 1. Remove the 2nd router all together and configure the new combo modem/router with a port forward to your Apex. 2. Give the 2nd router a static address in relation to the 1st router, then add the IP to the DMZ config of the 1st router. The DMZ rule will pass ALL requests from the first router to the second. The 2nd router will then pass the request per the existing port forward rule.
tmgrash
02/25/2014, 11:38 AM
Thanks ray. That helps a lot. I think that must be my problem. Part of the reason I didn't use modem/router as my router is because I can't find the page to set ports and such. Guess I'll be doing some internet searching this evening
kurt_n
02/25/2014, 11:41 AM
revnull... is another option to set the modem/router combo into "bridge mode?" Then it will just act as a modem, correct?
One potential problem is that many of those ISP-supplied devices don't let you into the full administrative areas to allow something like that.
revnull
02/25/2014, 11:54 AM
It depends on what the new modem/router supports. A good rule of thumb is, if the modem has more than 1 LAN port, it's a router. In some cases you can ask your ISP to give you a standalone modem. More often than not, they feel they are upgrading you by giving you a combo device, but if it ain't broke, it doesn't need to be fixed. :)
Travis, if you can provide the make and model of the new modem, as well as the name of your ISP, we can figure out if it's suitable for your needs and we can remove the "old" router from the setup.
tmgrash
02/25/2014, 12:01 PM
Will do when I get home
vBulletin® v3.8.4, Copyright ©2000-2025, Jelsoft Enterprises Ltd.