well kithylin, theres some good news and some bad news for ya on this one. the good news is that the box that you used as an example in your first post in this thread is easily fixed. if you drop to a shell, youll notice that you can ping 4.2.2.2 just fine, and that the box actually CAN reach the internet through your ASA5505. the solution to this problem is to manually point your box(es) on your network to a dns server, cause your problem isnt DHCP related, port related or anything, but ultimately a DNS issue. in linux (which it looks like your example box is in that first post), you just wanna edit your /etc/resolv.conf file and add a nameserver to it. this will basically tell your box to use that nameserver for your dns lookup requests. on any windows box of course, you just wanna exit the tcp/ip properties of your network interface and add a dns server manually. once you do this, youll have no problem at all resolving DNS and browsing the web.
the bad news is kinda 2 fold. (1) ive found that the ASA5505 is not at all capable of acting as a dns server. i find this is a surprising shortcoming of this device, as i previously couldnt imagine a hardware firewall/router device that couldnt act as a fully functional DNS and DHCP server. (2) despite my best efforts (and believe it or not, my research for this problem brought me to this thread to begin with), I am finding that if you want static IP's on a network that is behind a 5505, you may have to set your IP's on the client side instead of the DHCP server. my personal preference is to configure a DHCP server to assign a particular IP to a particular MAC ID that requests an IP, but unless I am just totally missing something, I dont think this can be done.
anyways, good luck with your intro into cisco (and wow, a 5505 is a hell of a way to get your feet wet with cisco hardware, but hey, ya gotta start somewhere, right?!)
