Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

"NAT Loopback" vs "One-to-one NAT" on Cisco RV320.

I can't find any documentation that tells me whether or not I can use NAT Loopback on a Cisco RV320. I must have this for our app to work but my boss already bought the RV320 and I need to know if it will do this. If not, is there a way to use one-to-one NAT to let 100's of users access our FTP server from inside our network?

Thanks.

  • Small Business Routers
5 REPLIES
New Member

Re: "NAT Loopback" vs "One-to-one NAT" on Cisco RV320.

I have one RV042G and IT hace One-to-One NAT available but I don't know anything about NAT Loopback. It should be the same in both units but I'm not shure either.

Cheers!

Sent from Cisco Technical Support iPhone App

Cisco Employee

Re: "NAT Loopback" vs "One-to-one NAT" on Cisco RV320.

If you mean access the internal server by the public address, yes RV320 support it. Please check attached case.

New Member

Will this work on the RV325?

Will this work on the RV325?

New Member

I have a RV320 , 

I have a RV320 , 

Currently unable to access the server internally using the external IP. But from outside the network you are able to access the server with the external IP. 

- I have 1:1 NAT setup using the external IP to the Internal Address of the server. )obviously this is working since I can access from outside the network but not inside.)

- I have tried port forwarding any/all ports and still unable to access internal server with external IP.

New Member

Hi Alex

Hi Alex

I found a very easy work around for my RV325.

  1. Configure the DNS Local Database with your host names and point them to your servers on your LAN. Use the private ip addresses. e.g. example.com -> 192.168.10.6
  2. Set the DHCP Static DNS 1: to the gateway ip. DNS 2: can be your ISP DNS or whatever external DNS you prefer. 

Now when your clients receive a new lease from the DHCP server they will look up the local DNS you have configured first and your domains will be resolved to the private ip and not the public ip. 

NB. Configure both variants of the your host names if they are in use. e.g..  www.example.com and example.com

1152
Views
0
Helpful
5
Replies
This widget could not be displayed.