asked on

Cisco VPN clients unable to resolve names through VPN connection

Hello - we just recently changed Operations Masters from our old 2003 AD/DNS server to a new 2008 AD/DNS server that we've been using on the network for some months now, and are now trying to switch the network onto for the primary AD server, so the 2003 server can soon be decommisioned. AD and DNS works fine on the network with local desktops and servers, but remote laptop users are having naming resolution problems through their VPN connection. In the ASDM, the DNS Client setting has the old DNS server, as well as the new one added to it, but it does not help. The strange thing I am seeing is that no matter what I set for the DNS servers in the ASDM, I continue to see old entries on an IPCONFIG /ALL command on clients when connected via VPN. I cannot figure out where the old entries are coming from. Here is a screenshot link to show you the DNS settings that seem to be stuck. For reference - 192.168.1.134 is our old 2003 server, 192.168.1.7 is an old secondary AD server which no longer exists and should be removed, and the new server is 192.168.1.9 (not showing).
http://screencast.com/t/Tko8ehX2N (link to screenshot)

Pete Long

Brave the command line you will have it fixed on no time

what VPN? IPEC or AnyConnect/SSL?

find the gorup policy thats assigned to your VPN

show group-policy

Open in new window

will tell you, lets say its called MY-VPN-POLICY

simply issue a

group-policy MY-VPN-POLICY attributes
dns-server value 192.168.1.1 192.168.1.2
default-domain value yourdomain.local

Open in new window

obviously inset your DNS/Domain Values

Pete

Damian Gardner

ASKER

tried this and it worked! Thank you Pete.

ASKER CERTIFIED SOLUTION

Pete Long

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Damian Gardner

ASKER

I thought I closed this. sorry.