06-06-2017 11:46 AM
Hi Team,
I'm working with a customer for a roll out of anyconnect into win10 machines.
During the tests phases, an issue was found related to DNS Search Suffix.
Customer using Windows 7 machine is able to add their internal domain into DNS suffix search list. and all internal sites are resolved with any problem.
When using windows 10 machine, the internal domain is not added, and having issue trying to access internal sites.
Customer used split DNS and that's the only way to solve internal sites.
Customer must remove split DNS and make windows 10 to add the correct domain into prefix search list.
Any one has an idea on how to fix it?
SR is opened and looking for opening a BUG.
Solved! Go to Solution.
06-06-2017 01:25 PM
Hello,
Are the Windows 10 users accessing the same Connection profile/Group Policy as the Windows 7 users ?
What is the case number? If you haven't gathered a DART for the Windows users please do so we can take a look.
Best regards,
Paul
06-06-2017 01:25 PM
Hello,
Are the Windows 10 users accessing the same Connection profile/Group Policy as the Windows 7 users ?
What is the case number? If you haven't gathered a DART for the Windows users please do so we can take a look.
Best regards,
Paul
06-06-2017 01:52 PM
Hi Paul,
Thanks for the prompt reply,
Aa far as I know users are connecting to same group as win7 users. The SR is: 682384260
DART for window 10 are attached into SR.
Thank very much!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide