Redirect a hard coded IP address

I posted this over at the sonicwall forums but I'm not getting any response.

I have a device on my network running an application that must talk to another server. When the app was written the IP address it talks to was hard coded in. That address has since changed and the app doesn't work anymore.

We have a new development team working on it but the new app won't be ready for months. In the mean time I would like to redirect this traffic some how.

The server is behind a sonicwall tz210 and the IP I want to redirect it to is also behind a sonicwall, an NSA240.

Is there some way to have the tz210 grab this IP and redirect it to the nsa240?
Who is Participating?
Cas KristCommented:
Maybe with NAT policies, never tried this before.

Source original : firewalled subnets
Source translated: X1 IP

Destination original:  (the hard coded ip)
destination translated: (the new ip)

Service original: (try to add the service or choose any)
Service translated: original

interface inbound: any (not sure about this one)
interface outbound: any (not sure about his onne either)

Not sure, but you can try it.

The short answer is yes, you can do that with NAT.  What happened to the old address?  It might be easier to assign a secondary IP address to the server so it will listen on the old address as well as the new one.
AJNSAuthor Commented:
the IP address it is trying to reach is actually a live IP on the internet that used to belong to the wan interface on a firewall. That is no longer our IP, it stayed with a hosting company.

Do you think NAT will get me out one firewall and back in the other?
Firewall Management 201 with Professor Wool

In this whiteboard video, Professor Wool highlights the challenges, benefits and trade-offs of utilizing zero-touch automation for security policy change management. Watch and Learn!

NAT is not going to do you any good if you don't have access to the IP address anymore.  NAT will convert address from an outside port to an inside port (or any variation like that) but you have to have an interface that is "listening" for that address.  The issue you've got is that even if you configured that address on your public interface the carrier isn't routing that address to your premise so the traffic would never get there.

So did you have the public address configured directly on the server?  If so, then you could create that address as a secondary address on the LAN interface of your router.  You could then NAT a different public address that appears on the public side of your router now to the old address.  That should work for you.
Cas KristCommented:
When the NAT policy is used on the 'sending' firewall, the traffic is redirected to the new ip address. The receiving firewall accepts that traffic.
Cas KristCommented:
Sure this method works
Cas KristCommented:
I've used this outbound NAT policy to redirect traffic to SMTP-servers, not exactly this setup, but close.
Cas KristCommented:

3) Accept one or more Expert posts as the answer

Following an 'Objection' by caskrist (at to the intended closure of this question, it has been reviewed by at least one Moderator and is being closed as recommended by the Expert.
At this point I am going to re-start the auto-close procedure.
Thank you,
Community Support Moderator
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.