I was hoping that someone out there could help with this issue. we are implementing a new domain, therefore new DNS/WINs servers. I terminate our clients with our ASA5510. I have changed the DNS and WINs attribues. When the device doles out DHCP to teh clients, the new naming servers are not doled out, so users in my new domain are having issues.
Here is where I changed it.
group-policy UserVPN attributes wins-server value 10.161.21.41 10.161.21.23 dns-server value 10.161.21.41 10.161.21.23 default-domain value wi02.com
10.161.21.23 is my new naming server, but it is not showing up on the VPN client?
1st question: Yes, DHCP is doling out DNS/WINS server info
2nd question: I am trying to add 21.23 as the secondary DNS/WINS server (this is the new domain controller)
3rd: the group policy is associated with the tunnel group, and my clients are able to join the network just fine. However, my clients are not getting the 21.23 server in their TCP/IP stack when the ASA hands out an IP address?
I hope this answers your questions. is there anything else I could be missing?
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...