This encrypts all internet traffic from your computer but may inadvertently block you from using resources on your local network, such as a networked printer at home. All non-Stanford traffic proceeds to its destination directly. This routes and encrypts all traffic going to Stanford sites and systems through the Stanford network as if you were on campus.
When using Stanford's VPN from home, we generally recommend using the Default Stanford split-tunnel VPN. To connect to the VPN from your Windows computer you need to install the Cisco An圜onnect VPN client.
If you are big then you already have at least two internal DNS servers (your domain controllers for example), but if you are small single server shop then just enter some fake IP address for secondary DNS in client configuration as quick workaround until you upgrade all the clients.Stanford's VPN allows you to connect to Stanford's network as if you were on campus, making access to restricted services possible. They claim that this issue shows its ugly face when only one DNS server is configured to be pushed on the client. Another workaround according to Cisco is to use more than one DNS server in the tunnel group (or client configuration group). or newer don't have this problem, so I advised my customers to upgrade their Cisco VPN Clients. This required an emergency testing in my mighty lab :) - my laptop with VM Ware and Windows 7 32-bit virtual machine:)įinally I resolved the case: it's a bug in the VPN client (I found it on Cisco Bug Toolkit under CSCsq34291 name). As I wrote above it wasn't about just one case but several. So, actually you can connect to your intranet servers using IP addresses, but not with DNS names. 64-bit version of Win 7/Vista and WinXP are fine.Ī little deeper investigation isolated the problem: I noticed that vpn client upon successful connection with the Cisco router or ASA firewall doesn't receive DNS servers specified in tunnel group (ASA) or client configuration group (IOS). These days I'm receiving support calls from our customers which say that they are unable to connect to the intranet resources with Cisco VPN Client.Ī little investigation brought me to discovery that it's only about Cisco IPSec VPN Clients installed on Windows 7 32-bit.
0 kommentar(er)
