instead of using eq bootpc; try eq 67 (For the DHCP problem)
Also these two entrys may be conflicting:
access-list 101 deny ip any 10.0.0.0 0.255.255.255 (Out)
access-list 102 permit ip host 10.1.10.10 192.168.32.0 0.0.0.255 (In)
It looks like it will allow 10.1.10.10 to come in but not allow it back out.
You might try:
access-list 101 permit ip 192.168.32.0 0.0.0.255 host 10.1.10.10 (If RD only use eq 3389)
access-list 101 deny ip any 10.0.0.0 0.255.255.255
Main Topics
Browse All Topics
by: Nothing_ChangedPosted on 2009-01-08 at 07:11:53ID: 23325672
The fastest way to troubleshoot what you need for just DHCP in your environment would be to put a Sniffer on a device, start a capture, then plug it into your public wireless with the ACLs disabled, and look at exactly what and to where it communicates to pull that IP you need. Odds are your implicit deny all at the end of acl 102 is dropping something you need. If you ahve a dhcp-helper address configured, be aware that this will change the look of the packets getting forwarded to your dhcp servers from their native structure if the dhcp server was on your LAN directly, so you may want to take a capture in front of your dhcp server too jsut to see how it looks there too. If you have a few short captures fro mthis and want a hand sorting it out, paste em back in and I'll have a peek.
and yes, 125 is weak but i like looking at packet captures so im in :) if you dont own a real Network General or Netscout Sniffer, use wireshark it works pretty well for low speed captures where packet timing isnt that critical.