Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

we have a virtual machine which hosts a web based bug tracker in our network which is reached internally via e.g. 192.168.1.5:9800. From the outside we made a port forwarding in our firewall so that the web site can be reached via e.g. 72.10.10.10:9800.

Now that works fine but the problem is that we got different IP addresses to reach the same service depending if we are in the office or at home and when the service sends out an email the link doesn't always work :)

So we are looking for a solution to fix it.

One could be to make a rule in out firewall that all communication to 72.10.10.10:9800 is forwarded to 192.168.1.5:9800... If that's possible that is considering it's an IP address + a port. The reason we used a port is because we only got one static public IP address but multiple virtual web appliances.

Thanks for any suggestions or solutions :)

Patrick

PS: The network is a Win 2008 R2 domain by the way and our firewall is SonicWall 2040 PRO http://www.sonicwall.com/us/products/PRO_2040.html

share|improve this question
    
You surely already have a rule that all traffic from 72.10.10.10:9800 is forwarded to 192.168.1.5:9800, thats how port forwarding works. –  Sam Mar 22 '10 at 10:20
2  
What brand/model is the firewall device? Some devices require extra configuration to support this kind of internal loopback NATing. –  einstiien Mar 22 '10 at 10:58
    
+1 for einstiien, loopback NATing is what you want to use. –  ITGuy24 Mar 22 '10 at 14:20
    
Thanks Einstiien that was what I needed –  Patrick Mar 23 '10 at 2:59

4 Answers 4

On most of your higher end Routers you can specify

Forward Wan traffic on this port to this IP address or Forward all traffic on this port to this IP address

What make and model Router are you using?, check to see if it has the ability to set the All traffic option, if it does, tell everyone to stop using the internal IP and only use the External.

HTH

share|improve this answer

Have you though about using a vpn for this , rather than port forwarding?

share|improve this answer
    
Yes we have a VPN but needing to turn the VPN on just to go to our bugtracker website isn't the most comfortable solution. Thanks –  Patrick Mar 23 '10 at 2:37
    
your right only ip level but he has the same port listed 9800 –  trent Mar 24 '10 at 6:47

Based on Einstiien I found DNS NAT loopback from Sonicwall which is what we needed: http://www.sonicwall.com/us/support/2134_3454.html

Only question left is, could we have also done the DNS NAT loopback on Win 2008 R2 considering that all traffic goes through it before going to the router?

Thanks, Patrick

share|improve this answer

I would use DNS to solve this problem ...give the server a name then resolve this server internally as the 192 address and have your external DNS server resove it with the other address.

share|improve this answer
    
Does it also work with ports? I though DNS works only on the IP level. Thanks –  Patrick Mar 23 '10 at 12:43

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.