Static NAT issues

[collinks2]

Hello,

I am having issues with static NAT. I have public subnet that gives me 5 usuable addresses. I used one for my public interface on the Cisco router. I set up dynamic NAT with port overload and it's working very well.

However, I have an internal server which I want Internet users to access. I have configured static NAT use for this command :

Ip NAT inside source static 10.1.1.1 3.3.3.3 extendable  but I can't ping 10.1.1.1 from Internet. Can someone help?

[Francesco Molino]

Why NAT? 

Your NAT seems working right? you've got some helps from other members during my night :-) and it seems to be ok.

Now you want to have a DNS resolution. To do it very quickly, just add a Type A entry on your provider admin page for matching exp-e.fuoict.fuotuoke.edu.ng to IP 165.90.243.14.

You don't need more NAT.

If you want to split fuoict.fuotuoke.edu.ng and exp-e.fuoict.fuotuoke.edu.ng to 2 different IPs then you need to create 1 more NAT but anyway you'll still need to create the DNS entry zone.

Thanks

PS: Please don't forget to rate and mark as correct answer if this answered your question.

[collinks2]

Hello Francis,

for the splitting ,fuotuoke.edu.ng will have 165.90.243.14 and the dns entry zone for exp-e.fuoict.fuotuoke.edu.ng might have 10.108.13.14 which will be statically mapped to 165.90.243.13. In the dns entry, i  can enter 165.90.243.13. Then in the internal host,i use nat to map 10.108.13.14 to 165.90.243.13

The exp-e stands for expressway E WHICH IS TRAVERSAL FIREWALL. it has an option of enabling static nat mode if its to be deployed behind a static router.

Thank you in anticipation.sorry for bothering you a lot. Am CCNA and CCNP certified.

https://www.youtube.com/watch?v=OLWVribzUCQ

[collinks2]

let me explain to you what i intend to achieve with this. I have a dns server running on the virtual machine. i set up a domain which is fuoict.fuotuoke,edu.ng. i  want this domain to be publicly accessible  by internet users.This domain is publicly resolved to 165.90.243.14.

On the virtual machine, i gave it an ip address 10.108.13.11 .i want this private ip to be statically mapped to 165.90.243.14 so that internet users can resolve. This deployment is for Mobile and remote access, so that external jabber users can communicate with internal jabber users

Similarly, i have an e-learning server which has an ip address 10.108.14.5.I want the internet users to access this url. for instance ,i can access 10.108.14.5/certsrv locally.

[collinks2]

Right now ,am using another internet source. i can ping 165.90.243.14.let me try that one

[Georg Pauwen]

Hello,

the virtual machine might be the problem. Which VM are you using ? VMware and VirtualBox by default create virtual machines with the NAT network type. You need to enable port forwarding for the ports you want to access from the outside.

[collinks2]

Hi Georg,

Am using vmware 8 which runs on ESXI 5.0.How do i enable the port forwarding on vmware ?

[Georg Pauwen]

Hello,

I am not sure what exactly applies to your specific setup, so here are a few links:

http://www.virten.net/2013/03/how-to-setup-port-forwarding-in-vmware-workstation-9/

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2006955

http://blog.romant.net/technology/configuring-nat-on-esx-and-esxi/

[collinks2]

Hello,

Thank you for the links. I think the last one is related to my set up cos I am running it on Esxi host. However I have read the article.

The author mentioned pfsene which downloaded and installed. Am stuck in choosing nics  ie the Wan and lan interfaces using this software pfsene. According to his article the wan interface should be for my internal lan while the lan interface should be for the pfsene lan.

Am I right to say that the wan interface corresponds to my public interface (165.90.243.13)and the lan interface corresponds to my host 10.108.13.11? During the installation of pfsene, I should select two nics, right. Currently, my existing lan on the Esxi host is vlan 13, subnet 10.108.13.0.i created a  new network adapter on vswitch1 but there is no physical adapter attached to it. Am confused.

[Georg Pauwen]

Hello,

I'll check how exactly to set this up. In the meantime, can you, for testing purposes, set up the same static NAT for another of your internal hosts, that is, a host that is not running on VM ? I am pretty sure that the problem is related to VM, if another host static NAT works, at least you know for sure what to work on.

Also, can you ping 10.108.13.11 from the public interface ?

ping 10.108.13.11 source outside_interface

?

[collinks2]

i tried it yesterday to set it up on another physical machine but got the same error. i can ping 10.108.13.11 source outside_interface. i have disabled firewall but the same.u can ping my static nat public ip 165.90.243.14 but u cant reach the internal host.

[Francesco Molino]

OK then if your server is using the right IP and all other hosts are using other IPs which problem do you have? 

Maybe I missed something

[collinks2]

I have an intranet server which has the ip-10.108.13.11.i want Internet users to access this private server. So, I decided to set up static NAT to create one to one mapping between 10.108.13.11 and 165.90.243.10