Question : Routing problem with Cisco ASA 5505

Greetings, experts!  I am in desperate need of assistance with an evil, evil, evil routing problem currently plaguing my network.

I run 2 VLANs, one for the main house network (192.168.0.x) and one for our development environment (192.168.10.x).  VPN is handled through the ASA and comes in on subnet 192.168.100.x.  DHCP for the .0.x network is handled by the Windows domain server at 192.168.0.10 (stupid but I didn't set it up and haven't had time to re-do it).  DNS for everything is handled by the same server.  Routing and DHCP for the .10.x (dev) and .100.x (VPN) subnets are handled from the ASA 5505.

From time to time, when a system is rebooted it is completely unable to route from one VLAN to another.  Specifically, right now I have a machine on the dev network that can route to and from the VPN network, but is completely unable to route to the house network and hit the DNS server or the internet.  So one of my remote developers can RDP to the box through the VPN, but can't then get internet access to get updates for the box.  I try to ping or traceroute to the house network or the internet and everything returns timeout.  But a random length of time, reboots, or cable disconnects/IP resets/whatever later and suddenly magically it works.

I've run the following on the ASA to make sure it's not a poisoned MAC hidden somewhere:
clear arp
clear asp table
clear route

When I run show arp it shows the correct MAC for the machine, so that's definitely not it.  WTF!?  Please help!!

Answer : Routing problem with Cisco ASA 5505

Two things to start with:

1. disable proxyarp on the inside and Lab_Data interfaces. Checkboxes under Routing in the ASDM GUI..
2. Add the following command:
   no nat-control

Also, check the license page in ASDM and see if full DMZ or restricted DMZ ?