Using Static IP's behind a Cisco ASA-5505

Can you post your config? If they are on an inside interface, they shouldn't need a rule. Higher security to lower should work by default.

i'll re-connect the cisco and look at it in a little while, went ahead and took it off until i can figure it out.

I tried a port-forwarding guide to try and forward port 3724 to one of the ip's assigned through the 5505's dhcp service, 3724 tcp for u-torrent, but that didn't work either, i should probably delete that in a bit.

Result of the command: "show running-config"

: Saved
:
ASA Version 7.2(2)
!
hostname ciscoasa
domain-name default.domain.invalid
enable password Yn8Esq3NcXIHL35v encrypted
names
!
interface Vlan1
nameif inside
security-level 100
ip address 192.168.1.1 255.255.255.0
!
interface Vlan2
nameif outside
security-level 0
ip address dhcp setroute
!
interface Ethernet0/0
switchport access vlan 2
!
interface Ethernet0/1
!
interface Ethernet0/2
!
interface Ethernet0/3
!
interface Ethernet0/4
!
interface Ethernet0/5
!
interface Ethernet0/6
!
interface Ethernet0/7
!
passwd 2KFQnbNIdI.2KYOU encrypted
ftp mode passive
dns server-group DefaultDNS
domain-name default.domain.invalid
object-group service uTorrent-3724 tcp
description uTorrent(3724)
port-object range 3724 3724
access-list outside_access_in extended permit tcp any object-group uTorrent-3724 interface outside object-group uTorrent-3724
pager lines 24
logging enable
logging asdm informational
mtu inside 1500
mtu outside 1500
icmp unreachable rate-limit 1 burst-size 1
asdm image disk0:/asdm-522.bin
no asdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 1 0.0.0.0 0.0.0.0
static (inside,outside) tcp interface 3724 192.168.1.26 3724 netmask 255.255.255.255
access-group outside_access_in in interface outside
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout uauth 0:05:00 absolute
http server enable
http 192.168.1.0 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd auto_config outside
!
dhcpd address 192.168.1.2-192.168.1.129 inside
dhcpd enable inside
!

!
class-map inspection_default
match default-inspection-traffic
!
!
policy-map type inspect dns preset_dns_map
parameters
message-length maximum 512
policy-map global_policy
class inspection_default
inspect dns preset_dns_map
inspect ftp
inspect h323 h225
inspect h323 ras
inspect rsh
inspect rtsp
inspect esmtp
inspect sqlnet
inspect skinny
inspect sunrpc
inspect xdmcp
inspect sip
inspect netbios
inspect tftp
!
service-policy global_policy global
prompt hostname context
Cryptochecksum:d0664dae2b1694f06941b2ba0ab64a1d
: end

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?!)