That is correct. The partners in this business primarily work out of their homes in different cities. Their laptops are not members of the domain since they are rarely here. They authenticate to the domain for files sharing and email by tunneling in thru VPN. On the rare occasion that they are actually in town and working from the office, they need to have the ability to establish a tunnel from within the network to authenticate them to the domain. So, what happens is the tunnel request needs to go outside of the network and then come back in to reach the outside interface and establish a VPN tunnel on the ASA. As it is now, if they attempt a connection from within the network, they get an error that the server is not responding. I'm assuming it's due to a missing ACL on the router. Hopefully this makes sense.

OK, understood, with your current setup, having the vpn configured to the outside, this won't work, you will need to apply the same crypto map that you have applied to the outside into the inside interface, as well as enable isakmp on the inside interface too, but that does not end there, you need to enable the command "same-security" to permit intra-interface.