NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

McDoogie's avatar
Aug 13, 2015
Solved

Nighthawk Remote Access With AT&T Arris NVG589 Modem

Hello, I am trying to use the Remote Access feature on my Nighthawk Router. Currently with Remote Access enabled I get these two IP addresses from the nighthawk: 
192.168.1.X: port number
and 2602:xxx:xxxx:xxx::xx]: port number


The 192.168.1.200 is the static IP given to my Router from my Modem. The second IP address is the one that should be the remote access, but when I try it, it simply does not work, and it just does not look correct. 
Any help on this would be appreciated. IF anyone needs any more information about anything just ask!
Thank you!

  • Hi McDoogie,

     

    Did you set port forwarding on the modem using the port number used for Remote management? The reason it works might be becuase of the modem forwarded the request to the router.

     

    Regards,

     

    JamesGL

    Community Team

23 Replies

  • JamesGL's avatar
    JamesGL
    NETGEAR Employee Retired

    Hi McDoogie,

     

    The router is getting a private IP from your modem. In order for remote access to work with private IP you may need to do port forwarding from your modem so that the request will be sent to the router.

     

    Regards,

     

    JamesGL

    Community Team

    • McDoogie's avatar
      McDoogie
      Tutor

      Thank you for the reply! What exactly would i need to port forward in the modem?

      • JamesGL's avatar
        JamesGL
        NETGEAR Employee Retired

        The port number that remote access is using. Check if the modem has port forwarding feature. Once port forwarding has been done, you can access it via the WAN IP:Port number.

         

        Regards,

         

        JamesGL

        Community Team


  • McDoogie wrote:

    Hello, I am trying to use the Remote Access feature on my Nighthawk Router. Currently with Remote Access enabled I get these two IP addresses from the nighthawk: 
    192.168.1.200: port number
    and 2602:xxx:xxxx:xxx::xx]: port number


    The 192.168.1.200 is the static IP given to my Router from my Modem. The second IP address is the one that should be the remote access, but when I try it, it simply does not work, and it just does not look correct. 
    Any help on this would be appreciated. IF anyone needs any more information about anything just ask!
    Thank you!


    That second IP address is actually an IPv6 address.

     

    I would think twice about enabling remote access on your Nighthawk.  It will make it easier for hackers to break into your network.

     

    If you are still determined to do this, then instead of setting up a port forward on the modem, you might be better off enabling IP Passthrough on the NVG589.  This is a pseudo-bridge mode for the modem.  The important point is that your Nighthawk's WAN interface will receive the same public IP address as your modem.  Then you should be able to remotely access your Nighthawk using the public IP address.

     

    dslreports.com has a good article on setting up IP Passthrough.  https://www.dslreports.com/faq/17734

  • I appreciate your reply! I do currently have Ip pass through enabled. Some time ago I setup this modem as bridge mode, even though it does not technically have a bridge mode option. I have all the firewall settings disabled on the modem except ip pass through. I have tried netgear and uverse tech support multiple times, but they have not been able to help. I also have an ip camera that I am unable to remote access.
  • If you have IP Passthrough enabled, then your Nighthawk should be using the PUBLIC IP address assigned to your modem, not 192.168.1.200, which is a PRIVATE IP address.

    If you log into the NVG589, go to Devices > Device List and you will see IP addresses assigned by the modem. It will clearly call out the device using IP Passthrough (which should be your Nighthawk) and its IP address. This IP address must match the Broadband Ipv4 Address shown on the Broadband Status page on the NVG589. Finally, this address must also show up as the Internet IP address on the Nighthawk's Basic > Internet page. If any of this is not true, then IP Passthrough is not set up correctly.
    • McDoogie's avatar
      McDoogie
      Tutor

      I will check when i get home today! also on the router i have it set for a static IP, should i have it set to obtain from isp?

      • TheEther's avatar
        TheEther
        Guru

        It depends on the Passthrough mode setting.  If it is set to either DHCP-Fixed or DHCP-Dynamic, then you should set the Nighthawk to obtain its IP address from the ISP.  If it is set to Manual, then you should enter the modem's public IP address as the static IP address on the Nighthawk. 

         

        I use DHCP-Fixed.  Should the modem's IP address change (a rare but not unheard of event), the Nighthawk will automatically pick it up after a few minutes.

  • Because the remote access didn't work.I was able to get this to work at a client's house with the same router but they had a time Warner cable modem. the modem was in bridge mode, and I enabled remote management on the nighthawk router, and it work, I was done in like 5 minutes. But it seems uverse is much different since they dont have a bridge mode. I don't know If my modem settings are correct or what. I'll check in the packet filters when I get home
  • Update: I just tried the 75.X.X.X ip at my girlfriend's house, even though before I left I reset my router to 192.168.1.200. And it's working. Not sure I understand why. I have the 192.168.1.200 ported in my modem currently. But it's working. Can anyone exlpain?

    • TheEther's avatar
      TheEther
      Guru

      Perhaps you didn't apply the change back to 192.168.1.200?  Anyway, it's a little unfortunate that you published your real IP address.  Anybody can now try to brute force their way into your router.  You better have a really strong password.

    • JamesGL's avatar
      JamesGL
      NETGEAR Employee Retired

      Hi McDoogie,

       

      Did you set port forwarding on the modem using the port number used for Remote management? The reason it works might be becuase of the modem forwarded the request to the router.

       

      Regards,

       

      JamesGL

      Community Team

      • TheEther's avatar
        TheEther
        Guru

        If McDoogie is still using IP Passthrough, then port forwarding isn't required.

  • Under remote access on the router, it gives the ip address and port 192.168.x.xx:xxxx.it's the lan address of my router.
    On the modem under port forwarding, I have the lan address of my router and that port required for remote access. Also under remote access on the modem it gives a 75.xx.xx.xxx ip. When I try to remote access my router, the 192 address doesn't work, but the 75ip address does work. So I can remote access my router and my modem with the 75ip given by the modem, by using different ports.
    • TheEther's avatar
      TheEther
      Guru

      While you may have gotten remote access to your router working, this is most likely a suboptimal setup overall because both your router and your modem are performing NAT.  Read this article on why double NAT is bad idea.  IP Passthrough avoids double NAT.

       

      Anyway, if everything is working...

      • McDoogie's avatar
        McDoogie
        Tutor

        now that i got it figured out, anyway to delete this thread?

  • On the modem under ip pass through I had to do default server and slect my router from the drop down list. Then any porting I need to do I have to do it on the modem and router. The dhcps fixed option didn't work on the modem. Default server was the only way I could remote in and view my cameras hardlined on my router.
    • JamesGL's avatar
      JamesGL
      NETGEAR Employee Retired

      McDoogie,

       

      Thank you for sharing the resolution of your problem. This will help other users who has the same scenario.

       

      Regards,

       

      JamesGL

      Community Team