The problem is only with Windows, and has to do with how Windows resolves IP addresses to hostnames. When the IP cannot be resolved locally or in DNS/WINS, Windows will send directed NetBIOS queries to the device to try and get a response. If the device (the ACS server in this case) does not reply, each resolution request can take up to 4 seconds. This really starts to add up.
The workaround is to add an entry for the ACS server to avoid this long resolution process. As I said, this is a bug in LMS, and will be fixed in 3.2.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...