RV042 NAT Issue

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by HAL6000, Apr 8, 2005.

  1. HAL6000

    HAL6000 Network Guru Member

    I am having a bit of a problem getting NAT to work like I need on my RV042. I am running a windows webserver with my own DNS behind the router on my cable connection. When I set everthing up the router gives out my LAN IP of instead of the WAN IP. My dns entries normaly have hal6000.com going to With my old Kingston router this was not an issue and everthing got translated to the WAN address. I tried playing with the one-to-one NAT setting but I can not use that. Right now I am forced to enter my WAN IP in my DNS server to function correctly.

    Does anyone know what I might need to configure in the router to make the NAT work, IMO, correctly?


    RV042 1.3.1 FW
    2003 Server running IIS, DNS, no AD
    4Mb/512kb Cable connection
  2. fizzerfits

    fizzerfits Network Guru Member

    If the DNS server you are talking about is meant to be serving the general public, then you should have your WAN IP dialed in there.

    While I can't speak with absolute authority, I can say that Kingston routers have been known to mess with protocol to make things easier and as such make some things work that shouldn't (this may be why it worked before).

    I'm assuming you are fowarding port 53 (UDP and TCP) to Also, if you are using dual WAN, make sure that all traffic on port 53 is going out the same interface that it is supposed to be coming in on.

  3. HAL6000

    HAL6000 Network Guru Member

    Right now I am just using WAN1 & WAN2 is just not used. I may connect my 2nd cable modem to it however. At the moment I am only forwarding 53 with UDP at that is the default forwarding option.
    I have done some reading on NAT and it seems there are 4 ways to do it. Static, Dynamic, Overloading, & Overlapping. Which I think the Kingston was operating in Overloading or Overlapping NAT, which seems to be what I want. If I can configure the Linksys the way that would be nice. If not then I wasted $150 on a new router that I didn't really need. It just makes more work for me in my current configuration when my IP does get changed by my cable company.

  4. DocLarge

    DocLarge Super Moderator Staff Member Member

    Just as an add on, try looking at getting a dynamic dns account with someone. That way, when your ip changes to a new one, you're still get requests pointed towards your established "dns name" (in this case www.hal6000.com)
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice