cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2175
Views
10
Helpful
7
Replies

PAT- in this network, my DHCP can ping PC, but PC can't

victorhalo84
Level 1
Level 1
 

Here are the configuration of the router, my remote DHCP server can successfully ping all the PC and router, but my Pc in the network 192.168.1.0 can't ping the remote DHCP server and access the website.

router 0 configurationrouter 0 configurationrouter 2 configurationrouter 2 configuration

For my opinion, I think there are something wrong in the ACL list, but I can't find out what is the problem.

1 Accepted Solution

Accepted Solutions

Hello
You have a default routes pointing towards two directly connected rtrs, so suggest you append a null route for your lan subnets on each rtr, also the static nat statement on rtr 1 is pointing to the wan interface and as this is NOT a PAT statement then your ping will not work for the dhcp server, as such change that static nat statement for another free public ip ( inside global) amend the ip helper adresss on rtr 0 then you should be fine.
See attached working PT file.


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

View solution in original post

7 Replies 7

ip nat inside source list 10 interface FastEthernet0/1 overload 

<<- this wrong it must be 0/1 not 0/0 

Thank you for replying Sir, but do I configure that On both router or one of the router, because I tried both or one of the router I still cannot ping my dhcp server from the PC.

 

Hello,

post your zipped Packet Tracer project (.pkt) file...

Here are the pkt in the zip file Sir.

Hello,

looking at your requirements:

--> Company AA network is assigned the public address 201.1.1.1. It has an offsite network which hosts the Remote DHCP Server0 that could be access with the public address 201.1.1.2. 

--> Show that PC0, PC1 and PC2 could successfully ping the Remote DHCP Server0. Include descriptions.

It looks like all they want you to accomplish is to ping the Remote Server using its public IP address 201.1.1.2

If you change the ip nat statements on BOTH routers (as they are both pointing to the inside and not the outside interfaces), that requirement is accomplished.

Attached the revised file...

explain the issue, 
Both Router do NAT 
this is not acceptable
why 
PC send traffic to Server 
the PC know the Server IP and send the LOCAL INSIDE of Server (before NAT)
the Router0 Do nat now the PC IP will NAT to Router IP GLOBAL IP 
the Router1 receive Router0 IP as source and as destination the LOCAL INSIDE of Server<<<--- here the issue 
the Dynamic is not bi directional traffic NAT so the Router1 drop the packet 

how can I solve this?
with one of two solution below 
*add in Router1 static NAT for Server 
ping from PC the Router1 not LOCAL INSIDE of Server 

*disable NAT in Router1 

Hello
You have a default routes pointing towards two directly connected rtrs, so suggest you append a null route for your lan subnets on each rtr, also the static nat statement on rtr 1 is pointing to the wan interface and as this is NOT a PAT statement then your ping will not work for the dhcp server, as such change that static nat statement for another free public ip ( inside global) amend the ip helper adresss on rtr 0 then you should be fine.
See attached working PT file.


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul