I am having an issue with our field users who have a windows 7 laptop and connecting with a verizon aircard for internet access and then connecting to a cisco VPN to gain network access, but they cannot access company websites. I am able to replicate this issue as well and I believe this is a DNS issue. I have a windows 7 laptop and connect to the internet with the aircard, I then perform a nslookup, it reports back a Verizon DNS server. Next I connect to the Cisco VPN, after I connect I perform another nslookup and I still have a verixon DNS server reporting back. If I perform the same steps on a Windows XP laptop, after I connect to the VPN and perform an nslookup, my company DNS server reports back. I am really at a loss since if I connect to a regular internet connection via wireless or wired connection, and then connect to VPN, and perform a nslookup, I get the company dns server reporting back. So my question is, what could be different with Windows 7 to cause this? Is there anyway to force this connection to use the company's DNS over verizon? Any help would be appreciated.

Hi, It is not related to DNS server. 1. Check DNS servers with ipconfig/all command under Command Prompt. 2. Manually add DNS server for VPN connection. 3. Check if IP address is obtained properly. This issue is not related to Windows 7. Also, I suggest to contact ISP to clarify that they have not blocked the VPN packs.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, It is not related to DNS server. 1. Check DNS servers with ipconfig/all command under Command Prompt. 2. Manually add DNS server for VPN connection. 3. Check if IP address is obtained properly. This issue is not related to Windows 7. Also, I suggest to contact ISP to clarify that they have not blocked the VPN packs. Replies to your "steps". 1. ipconfig /all shows Verizon DNS servers for the Verizon adapter, and Internal DNS servers for the Cisco adapter. 2. No. That's stupid and is not a fix. 3. I'm not sure how to answer that. How would I know if the address was being assigned improperly? The only thing that doesn't work is Win7/Verizon/Cisco VPN. We have tried a different installation order, i.e. installing the Cisco client after Verizon and vise versa with no luck. The only solution was to add an LMHOSTS file with entries for internal services. Obviously NOT a fix for the broken Microsoft TCP stack changes that occurred with the Win7 release. Now what?

I am having the same issue with a slightly different setup: OS: Windows 7 x64 Wireless Provider: Verizon VPN Client: Watchguard/OpenVPN I have tried this on Windows XP x86 and Vista x86, and the problem doesn't happen, upon using nslookup I query the internal DNS servers specified in the SSL VPN client, but on Windows 7 with this setup, nslookup always queries the Verizon DNS servers and disregards the DNS servers that are defined in the SSL VPN client. Something is broken here with Windows 7...Newbie