After establishing my VPN connection I run a batch script to map some network shares. While mapping I am required to provide my domain credentials to be able to establish the drive mappings. What I believe to be the root cause of the problem is that my internal domain name is the same as my external domain name for my externally hosted web site which is causing a name resolution issue. To fix the DNS issue I am running an lmhosts file that points to the servers and DC within my internal network. Even with the lmhosts file it does not seem that my DC is receiveing the credentials for logon once the tunnel is established. Before the lmhosts was implemented with I would ping my DC and my external web server would respond with name resolution.Any ideas would be appriciated.

Go to the properties of the VPN connection and manually configure the private IP of your DC in the DNS box.Bill

Hi Murphy125, In addition to Bill's suggestion, you may also select the option "log on use dial-up connection" on the login Window. When you enable this option, you can simply choose your PPTP VPN connection as the dial-up connection, then enter your VPN user/passwd for VPN connection, after that, enter the domain user/passwd to logon the computer. In this way, you user will be able to logon the domain (not cached logon) after the PPTP VPN connection has been established. You should be able to map drive without typing domain user name and password again. Sincerely, Wilson JiaThis posting is provided "AS IS" with no warranties, and confers no rights.