not sure why i'm having a brain fart trying to remember how to explain this, but i beleive it has to do with the route from 192.168.x.x to 192.168.x.x or there is no route from your external 192.168.x.x to your 10 network. that is where i would start looking. sorry i couldnt break it down further.
are your dns servers configured in your ACL? are your dns servers in your split tunneling policy? on your desktop, what does your wireshark trace show on both adapters while the tunnel is up? what does your tcp dump show when you connect over the tunnel?
The ACL's look fine. I've put a rule in to enable DNS.
I've noticed when doing an IPCONFIG that the DNS settings a blank, like it's not known. That possibly why DNS resolution is not working. The question is now why does the client device not know what it's DNS settings are. I've tried the option of using the IVE DNS Settings, and manually entering the DNS configuration into the NC Connection Profile section.
that would be a problem, yes. when you do nslookup or dig on the PC, what do you see? is this on all flavors of windows or just a specific version?