First, you didn't mention what kind of DSL router it is. (BTW, most DSL routers comercially marketed are actually ethernet-to-ethernet routers. Calling them DSL routers is a misnomer.) Every NAT implementation I've worked with requires explicit ranges set up for NAT. There's a good chance that your NAT router is configured to only NAT addresses in the 192.168.0.X range.
If you'd like a more in depth discussion of what NAT is and how it works, I'd be happy to write a quick one up. Second, your Windows box is using it's loopback address for DNS. This is only a correct configuration if your Windows box is a DNS server and is receiving zone transfers from external DNS servers. I doubt that this is the case, so I would assume that DNS queries are failing. Wait... I suppose if you're running DNS on that box and have a secondary lookup to a public DNS, it should work. Better solution is to use the DNS server your ISP provides. Thirdly, while your Windows box knows how to get to the 10.0.0.0 network, due to your "route add" commands (BTW, that is not a reliable solution. Don't ask hosts (like a server) to make routing decisions), your NAT router does not know how to get there, or even that it exists. So even if the NAT router would translate 10.0.0.0 into public addresses, the router would not be able to send any packets back. For this you need a static route in the NAT router for the 10.0.0.0 network. This solution also removes the need for the "route add" commands. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=34906&t=34894 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
