04-27-2019 02:10 PM
We have just upgraded from a rv042g to the rv340w. the router is setup with a static public ip. We are trying to point one of our static ip to an internal ip (exchange server) but i noticed there is no one to one nat option. i tried to use the static nat but when i enable it the internet connection on the exchange server stops working? Any help would be greatly appreciated.
Solved! Go to Solution.
05-08-2019 04:30 PM - edited 05-08-2019 04:31 PM
I was having the same issue but have this part working successfully now. It is the Static Nat section you want to be in and create an entry and private IP is the internal IP of your exchange server and Public IP Range Begin would be the external IP for your exchange server range length would be 1 services would be whichever exchange service you are trying to setup (i.e. https, smtp) as i had to create 1 entry per service and then Interfaces would be whichever WAN port interface you are using.
This then creates some access rules for what you just set up in static nat however the destination interface was being set to "VLAN" this would not allow traffic through. I then manually created the access rule where the destination interface was "VLAN1" and traffic flowed as expected. Hope this helps if you are still having a problem.
07-11-2019 06:18 PM
Turns out the settings i had were correct, the issue was from the isp gateway. I had to power down the rv340 and the isp gateway then power them back on. The isp gateway wasnt registering the rv340's mac address
04-27-2019 03:07 PM
we need to more information how your outgoing NAT configured.
follow below guide for NAT example for incoming, :
04-27-2019 03:20 PM
So we have a comcast gateway connected to the rv340w. We have a total of 13 static ip addresses. The rv340w is assigned public ip 50.x.x.x. i would like to point another one 9f our public ip to our internal exchange server. Hope this helps im not to familiar with this. Our previous router was the rv042g and it was as simple as going to the site selecting one-to-one nat and entering the ip info but this one is a little complicated.
04-27-2019 03:12 PM - edited 04-28-2019 01:33 AM
Hello
@MoradA wrote:
i tried to use the static nat but when i enable it the internet connection on the exchange server stops working? Any help would be greatly appreciated.
Personally I have no exposure to this modal of router others on this forum may have However nat is nat and if this device supports it then its viable to work with 121 nat.
Can you post your configuration for this -Also can do you have spare public addressing to use for 121 nat translation!
04-28-2019 12:15 AM
Hello,
on a side note, how did you configure the static NAT (page 76 of the attached guide) ? The idea is to NOT include the WAN IP address in the public IP range...
https://www.cisco.com/c/dam/en/us/td/docs/routers/csbr/RV340/Administration/EN/b_RV340x_AG.pdf
04-28-2019 10:38 AM
My wan Static ip is 50.x.x.1 . In static nat i want to point 50.x.x.2 to internal 10.15.x.21. But when i enter that the server im pointing 50.x.x.2 to loses internet connection
04-28-2019 11:13 AM
Hello
curious do you have 50.x.x.2 available what’s is your public subnet range?
04-28-2019 11:35 AM
04-28-2019 12:47 PM
Hello
Please post your present configuration if applicable.
05-08-2019 04:30 PM - edited 05-08-2019 04:31 PM
I was having the same issue but have this part working successfully now. It is the Static Nat section you want to be in and create an entry and private IP is the internal IP of your exchange server and Public IP Range Begin would be the external IP for your exchange server range length would be 1 services would be whichever exchange service you are trying to setup (i.e. https, smtp) as i had to create 1 entry per service and then Interfaces would be whichever WAN port interface you are using.
This then creates some access rules for what you just set up in static nat however the destination interface was being set to "VLAN" this would not allow traffic through. I then manually created the access rule where the destination interface was "VLAN1" and traffic flowed as expected. Hope this helps if you are still having a problem.
07-11-2019 06:18 PM
Turns out the settings i had were correct, the issue was from the isp gateway. I had to power down the rv340 and the isp gateway then power them back on. The isp gateway wasnt registering the rv340's mac address
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide