I decided to get to the bottom of this, so I setup a clone of your network in GNS3. I used a laptop connected via ethernet to the computer running GNS3. I installed the cisco VPN client on the laptop. To eliminate any issues with access-lists, I changed access-list "access-list outside_access_in " so that it only had these 2 lines:
access-list outside_access_in extended permit ip any any
access-list outside_access_in extended permit icmp any any
I change list "dmz_access_in" so that it only had these 2 lines:
access-list dmz_access_in extended permit ip any any
access-list dmz_access_in extended permit icmp any any
(This was probably unnecessary, but I wanted to eliminate any issues with access lists)
Next, I configured list "access-list inside" so that it looked like this:
access-list inside standard permit inside-network 255.255.255.0
access-list inside standard permit dmz-network 255.255.255.0
and I configured list "inside_nat0_outbound" like this:
access-list inside_nat0_outbound extended permit ip inside-network 255.255.255.0 vpn 255.255.255.0
access-list inside_nat0_outbound extended permit ip dmz-network 255.255.255.0 vpn 255.255.255.0
I added a new NAT statement:
nat (dmz) 0 access-list inside_nat0_outbound
I added a username and password for myself like this:
username netman password ********** encrypted
username netman attributes
vpn-group-policy vpn3000
vpn-tunnel-protocol IPSec
I changed the pre-shared key for tunnel-group vpn3000 to something I knew. Then I went to the laptop and started the Cisco VPN client. I congiured a connection to use tunnel-group vpn3000 and the password I configured and when prompted for username and password I entered my credentials. The tunnel estasblished and I was able to ping successfully from the laptop to 192.168.1.2 (which was the only device I had connected to the ASA's LAN interface) and I was able to ping 192.168.2.2 (which was the only device I had connected to the ASA's DMZ interface).
If you want, I can post the entire working config.