Can't access system from outside with IP address

  • 1
  • Problem
  • Updated 3 months ago
  • Acknowledged
Viasat changed my "sticky" IP address over the weekend and now I can't access my system from an outside computer using the new IP address (100.***.***.***).  In addition, the IP address reported to my DDNS is different from the IP address that is seen by other systems (40.***.***.***), like Speedtest.net.  However, neither IP address allows access from the outside.  They just don't connect or do anything.  I've tried shutting off the modem overnight and hoping it would come back with an outside accessible IP but it keeps popping up with the same bad one.  Otherwise, from home "inside" the system everything works fine.  The folks at Viasat have been useless.  They aren't allowed to access outside systems for testing, etc. and they don't seem to understand the issue at all!!!
Photo of Stacey Mills

Stacey Mills

  • 5 Posts
  • 0 Reply Likes

Posted 3 months ago

  • 1
Photo of J&J

J&J

  • 1788 Posts
  • 1081 Reply Likes
Your DDNS app has an update interval that may be configurable.  It might be presently set to an extended period of time to "call home" for IP address updates, thus the incorrect IP address.  The DDNS service does not call your system, your system calls them to learn of any changes in your public IP address so un-plugging your modem was counter-productive.  You need to verify your DDNS service application is actually running and check the frequency of IP updates. DDNS services that run in an always-on router work reliably most of the time.

edit:  My reply assumes you have set up firewalls and port forwarding correctly to allow the access you are attempting. 
(Edited)
Photo of Stacey Mills

Stacey Mills

  • 5 Posts
  • 0 Reply Likes
DDNS is set for hourly updates and I can tell from the DDNS site that updates are occurring as they should.  Yes, port forwarding, etc. is set up and worked fine until this recent IP address change.  Likewise, when I'm home I can check the IP address directly from the router and its the same nonfunctional one (for outside access) reported by the DDNS.
 
Photo of Stacey Mills

Stacey Mills

  • 5 Posts
  • 0 Reply Likes
I don't see any way in the modem control software that I can "release" the current IP address and have Viasat assign a new one.  If there's someone at Viasat who could do this, I haven't found them.

Photo of J&J

J&J

  • 1788 Posts
  • 1081 Reply Likes
Hmmm......   A DDNS service and many VPN's can't work if there is a double-NAT on the public IP side, or 'apparent' public side, especially if your router is the device causing the double-NAT.  Make sure your router isn't forcing (or trying) to establish a static IP to ViaSat.  Some will try with disappointing results if the WAN is set manually to a static IP address.  If there is a double-NAT on the public side, "Get" browser request to the Internet will work as they traverse the path and the system remembers that return route, but outside incoming packets get lost.  Router WAN should be set to "automatic."  To get a new IP address from ViaSat can be a lesson in patience, re-booting their modem and then your router-- a few times, to realize a change.  

These things may not be your problem but they certainly will cause what you are experiencing so they should be checked to eliminate them from a list of possibilities.
Photo of ExSatUser

ExSatUser

  • 1007 Posts
  • 615 Reply Likes
You are going down a rathole here Stacey. Good luck getting it resolved!
Photo of Stacey Mills

Stacey Mills

  • 5 Posts
  • 0 Reply Likes
I agree.  Last night I figured I'd reset the modem and afterwards I couldn't get it back in "bridge" mode.  It still works, but now it outputs an internal "192.***" IP address to the DDNS.  I can access the modem but the Viasat software can't access the pages needed to change the settings.  After a LONG call with Viasat in which they really did try to help, we ended up deciding that the modem needs to be replaced so the technician is coming on Monday.  In the mean time, it works fine as long as I'm not trying to get in from outside the system. ...same as before but for a different reason, ie. DDNS now shows an internal IP address as opposed to a non-functional external one. 

(Edited)
Photo of ExSatUser

ExSatUser

  • 976 Posts
  • 605 Reply Likes
I question if it is a problem with the modem, but good luck!
Photo of Stacey Mills

Stacey Mills

  • 5 Posts
  • 0 Reply Likes
Well, there's at LEAST a new problem with the modem since I can't get it back into bridge mode.