MS DNS and VPN - resolution problems Bob 6/25/2007 2:44:01 PM Scenario: When connected to network via MS VPN, some machine names can not be resolved. the work around I have been using is connecting via internal IP or connecting (via rdp) to another hostname and then rdp-ing to the hostname i originally wanted to connect to. Any ideas?

Re: MS DNS and VPN - resolution problems "Trevor Christie" <bbtrev[ at ]gmail.com> 6/25/2007 5:52:48 PM We have had this problem in the past too. Our resolution was the use the Connection Manager Administration Kit (CMAK) to create a custom connection profile. This can then be rolled out to remote users. You are given the option to specify DNS servers for the VPN connection. Here is an MS article. http://technet2.microsoft.com/windowsserver/en/library/d000ae3a-3d5d-4a20-ab44-5afca021b0881033.mspx?mfr=true "Bob" <Bob[ at ]discussions.microsoft.com> wrote in message news:E2F14E1F-397E-424F-B8CD-BA9FCE91B4A1[ at ]microsoft.com... [Quoted Text] > Scenario: When connected to network via MS VPN, some machine names can > not > be resolved. the work around I have been using is connecting via internal > IP > or connecting (via rdp) to another hostname and then rdp-ing to the > hostname > i originally wanted to connect to. Any ideas?

Re: MS DNS and VPN - resolution problems Bob 6/25/2007 6:16:00 PM That could work as a temporary work around, but would not work permanently as often it is home machines connected to the vpn. It has not caused any real problems yet, just administration issues. What is causing the dns to fail for some names and not for others?

Re: MS DNS and VPN - resolution problems oz.ozugurlu 6/26/2007 2:35:02 AM I hate to tell you that, if you tried going to host files route? Host files are for sure is trouble, but I have seen them doing the magic best oz -- Oz Ozugurlu Systems Engineer MCSE 2003| M+| S+ MCDST | Security+|Project+ oz[ at ]SMTp25.org http://smtp25.blogspot.com (Blog) "Bob" wrote: [Quoted Text] > > That could work as a temporary work around, but would not work permanently > as often it is home machines connected to the vpn. It has not caused any > real problems yet, just administration issues. > > What is causing the dns to fail for some names and not for others?