We setup VPN on a windows 2008 standard sp2. One of VPN client running Windows 7 Home Edition has name resolution issue. He can establish the VPN and ping the remote server by IP, but name. If he ping the server name, it replies back with a public IP address. The VPN server does assign correct DNS and WINS to the VPN client as shown below. My temporary solution is creating a host and mlhosts files to point to the remote server. The hosts file works meaning we can ping the remote server by FQDN, but when ping server host name, it still replies with a public IP address. Here are more information. IPCONFIG Wireless LAN adapter Wireless Network Connection: Connection-specific DNS Suffix . : yourofficedenver.com Description . . . . . . . . . . . : Dell Wireless 1397 WLAN Mini-Card Physical Address. . . . . . . . . : 0C-EE-E6-D2-81-43 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IPv4 Address. . . . . . . . . . . : 192.168.1.141(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Thursday, October 07, 2010 8:58:24 AM Lease Expires . . . . . . . . . . : Friday, October 08, 2010 8:58:23 AM Default Gateway . . . . . . . . . : 192.168.1.1 DHCP Server . . . . . . . . . . . : 192.168.1.1 DNS Servers . . . . . . . . . . . : 38.112.11.202 208.67.222.222 208.67.220.220 NetBIOS over Tcpip. . . . . . . . : Enabled PPP adapter Paradigm: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Paradigm Physical Address. . . . . . . . . : DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv4 Address. . . . . . . . . . . : 192.168.10.209(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.255 Default Gateway . . . . . . . . . : Primary WINS Server . . . . . . . : 192.168.10.1 NetBIOS over Tcpip. . . . . . . . : Enabled Routing table route print =========================================================================== Interface List 33...........................Paradigm 12...0c ee e6 d2 81 43 ......Dell Wireless 1397 WLAN Mini-Card 11...00 25 64 6d f2 a0 ......Marvell Yukon 88E8040 PCI-E Fast Ethernet Controll er 16...00 50 56 c0 00 01 ......VMware Virtual Ethernet Adapter for VMnet1 18...00 50 56 c0 00 08 ......VMware Virtual Ethernet Adapter for VMnet8 1...........................Software Loopback Interface 1 15...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter 23...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface 14...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2 13...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter 17...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3 19...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #4 20...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #5 =========================================================================== IPv4 Route Table =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.141 30 127.0.0.0 255.0.0.0 On-link 127.0.0.1 306 127.0.0.1 255.255.255.255 On-link 127.0.0.1 306 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306 192.168.1.0 255.255.255.0 On-link 192.168.1.141 286 192.168.1.141 255.255.255.255 On-link 192.168.1.141 286 192.168.1.255 255.255.255.255 On-link 192.168.1.141 286 192.168.10.0 255.255.255.0 192.168.10.200 192.168.10.201 26 192.168.10.201 255.255.255.255 On-link 192.168.10.201 281 192.168.159.0 255.255.255.0 On-link 192.168.159.1 276 192.168.159.1 255.255.255.255 On-link 192.168.159.1 276 192.168.159.255 255.255.255.255 On-link 192.168.159.1 276 192.168.204.0 255.255.255.0 On-link 192.168.204.1 276 192.168.204.1 255.255.255.255 On-link 192.168.204.1 276 192.168.204.255 255.255.255.255 On-link 192.168.204.1 276 216.243.16.121 255.255.255.255 192.168.1.1 192.168.1.141 31 224.0.0.0 240.0.0.0 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 192.168.204.1 276 224.0.0.0 240.0.0.0 On-link 192.168.159.1 276 224.0.0.0 240.0.0.0 On-link 192.168.1.141 286 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306 255.255.255.255 255.255.255.255 On-link 192.168.204.1 276 255.255.255.255 255.255.255.255 On-link 192.168.159.1 276 255.255.255.255 255.255.255.255 On-link 192.168.1.141 286 255.255.255.255 255.255.255.255 On-link 192.168.10.201 281 =========================================================================== Persistent Routes: None IPv6 Route Table =========================================================================== Active Routes: If Metric Network Destination Gateway 1 306 ::1/128 On-link 16 276 fe80::/64 On-link 18 276 fe80::/64 On-link 16 276 fe80::9477:d6d3:78be:ec30/128 On-link 18 276 fe80::94b1:bc7:4650:9b58/128 On-link 1 306 ff00::/8 On-link 16 276 ff00::/8 On-link 18 276 ff00::/8 On-link =========================================================================== Persistent Routes: None 3. nslookup Default Server: hyperserver1.paradigm.org Address: 192.168.10.1 > pa08vsrv03 Server: hyperserver1.paradigm.org Address: 192.168.10.1 *** hyperserver1.paradigm.org can't find pa08vsrv03: Non-existent domain 4. Ping result. ping pa08vsrv03 Pinging pa08vsrv03.yourofficedenver.com [67.215.65.132] with 32 bytes of data: Reply from 67.215.65.132: bytes=32 time=32ms TTL=55 Reply from 67.215.65.132: bytes=32 time=37ms TTL=55 Reply from 67.215.65.132: bytes=32 time=25ms TTL=55 Reply from 67.215.65.132: bytes=32 time=27ms TTL=55 Ping statistics for 67.215.65.132: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 25ms, Maximum = 37ms, Average = 30msBob Lin, MS-MVP Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net How to Setup Windows, Network, VPN & Remote Access on http://www.howtonetworking.com

It is DNS suffix issue. The more details can be found this post: VPN Name resolution on windows 7 HomeBob Lin, MS-MVP Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net How to Setup Windows, Network, VPN & Remote Access on http://www.howtonetworking.com