From: Tim Fletcher (tim@fletchmail.net)
Date: Tue Oct 29 2002 - 15:57:38 GMT-3
Try removing your static default route. When you point a route to an
interface, it assumes the destination is directly connected.
The default route learned by DHCP will be installed in your route table,
so you shouldn't need a default.
-tim
On Sun, 27 Oct 2002, Kip Palmer wrote:
> Here's the deal:
>
>
> PC host------e0---R1---e1----------------> ISP's DHCP
> Server-------DNS server's 4.4.4.4 4.4.4.5/16
>
>
>
> interface Ethernet0
> ip address 139.2.25.3 255.255.255.0
> ip nat inside
>
> interface Ethernet1
> ip address dhcp
> ip nat outside
>
>
> ip nat inside source list 2 interface Ethernet1 overload
>
> ip route 0.0.0.0 0.0.0.0 Ethernet1
>
> access-list 2 permit 139.2.25.0 0.0.0.255
>
>
>
> Problem:
>
> On the PC host;
>
> Static IP 139.2.25.254 /24
> Default gateway - Ethernet 0's IP
> Static DNS of ISP's DNS servers(2)
>
>
> I debug ip nat translations detail:
>
> 05:53:38: NAT: i: udp (139.2.25.254, 5843) -> (4.4.4.4, 53) [56071]
> 05:53:38: NAT: s=139.2.25.254->4.46.28.254 , d=4.4.4.4 [56071]
>
> No reply and no resolution.
>
> Question:
>
> Why doesn't the DNS make it back, and what's the solution?
>
> I have other machines that are full DHCP clients, and that is how I
> derived the DNS server addresses.
> I can ping the ISP's df-gateway and DHCP server from PC host.
>
> Thanks in advance!
>
> KPALMER
This archive was generated by hypermail 2.1.4 : Tue Nov 05 2002 - 08:35:59 GMT-3