I have been using a Cisco client to establish VPN connection to my work PC for over a year now and recently something went weird. I just replaced my old router with a new Airport extreme and (maybe coincidentally?) then the RDC connection stopped working. It works in XP (running under VMware) just fine. Issue seems to be with the system being unable to resolve any DNS requests. Since the issue started, if the VPN client is connected, ALL REQUESTS for DNS resolution time out, including the name address of my work PC. I can connect only by manually entering the IP address of the PC. I found this: The following problem has occurred with non-Windows VPN Clients. While connected to the VPN Client, DNS resolution to the internal network works at first but fails later in the connection. If the workstation is set to use DHCP and receives a DNS address from the DHCP server, the new DNS overwrites the VPN Concentrator's pushed DNS that had been resolving internal network devices. Once the new DNS has overwritten the Concentrator-pushed DNS, internal devices are no longer resolved properly. Workaround: After connecting to the ISP, record the DNS addresses assigned by the DHCP server and hard code them into the workstation. This prevents the workstation from accepting the DHCP-pushed DNS addresses in the future but still allows resolution when not connected over VPN. The drawback of this is that if the ISP changes their DNS server addresses, the user must find out the hard way and hard code these new addresses once more on Cisco's help site but I can't make sense of it - Any help out there??