NAT issue unable to ping target server

[ershadali11]

Hi Team,

could anyone suggest to me what can be an issue that i am not able to ping target server 100.0.0.2 or 100.0.0.3

i just want to pass traffic for 10.0.0.0/24 network only to the target servers.

please just let me know the troubleshooting steps so can perform them.

Snap are attached for the reference..

Ershad,

[MHM Cisco World]

can I see the config of router and cloud ?

[ershadali11]

Sir, i am able to reach the cloud to Server.

[MHM Cisco World]

I need to check some point here, may be it not issue with NAT but routing 

[ershadali11]

Sir,

below is the cloud router routing

Gateway of last resort is not set

10.0.0.0/24 is subnetted, 1 subnets

S 10.0.0.0/24 [1/0] via 90.0.0.3

90.0.0.0/8 is variably subnetted, 2 subnets, 2 masks

C 90.0.0.0/24 is directly connected, Serial0/0/0

L 90.0.0.1/32 is directly connected, Serial0/0/0

100.0.0.0/8 is variably subnetted, 2 subnets, 2 masks

C 100.0.0.0/24 is directly connected, GigabitEthernet0/1

L 100.0.0.1/32 is directly connected, GigabitEthernet0/1

[MHM Cisco World · Accepted solution]

your config is prefect for cloud,
your router R1 can you see 100.0.0.0 subnet ??

[Flavio Miranda]

Hi

 Basics steps:

PC must have default gateway

R1 must have route to 100.x.x.x.

Web/FTP server must have a gateway or must have route back to 10.x.x.x

If you are doing NAT to get to the server, server must know how to reply to the NATed address

[Jitendra Kumar · Accepted solution]

I have a workout for you. hope it will help you..

1-check Nat router interface config
2-check access list
3- check routing

your router LAN interface
confg t
int f0/0
ip nat inside

check start ping PC1 or PC2 to server 100.0.0.2

check natting happen or not..

below is the show command

sh ip nat translation

clear ip Nat translation*

go to the config mode make access-list for specific network allow.

conf t
access-list 1 permit 10.0.0.0 0.0.0.255

if routing is ok this will work perfectly.

Thanks,
Jitendra

[ershadali11]

was missed ip nat inside and routing was missed on R1 for the target server..

[MHM Cisco World]

so there is routing issue also.
great job man