<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Turning off 4G to get Cisco Network Assitant to work on Android in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/turning-off-4g-to-get-cisco-network-assitant-to-work-on-android/m-p/3861444#M472743</link>
    <description>&lt;P&gt;I finally have BYOD working on ISE 2.4.x with 8.5.x running on my WLC's. Working fine for a week, then I asked a few users in my building to test sitting near the outer ring close to our building windows (my 4G signal is very intermittent in the center of my floor where I sit). Of the 3 users I tested the following error appears after clicking Cisco Network Assistant for Android:&lt;/P&gt;&lt;P&gt;“"&lt;STRONG&gt;Unable to detect Server. Please ensure your network access device is configured to redirect enroll.cisco.com to ISE”&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Came across a few forums referring to DNS named WLC ACL entries nothing seemed a definite solution to me. So I asked the 3 users to turn off 4G on there devices (all Android) suddenly Cisco Network Assistant starts working, users complete onboarding successfully, job complete.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Having a look at packet captures from my Anchor WLC I can clearly see the issue, each user was sending out a request to our BYOD DNS Servers (google Servers 8.8.8.8) over DNS-TLS port 853, the difference was all of these users were sending out SYN packets unlike working Android devices who are completing 3 way handshakes!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;With DNS-TLS obviously I can't see packet information to decode&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Asking users to turn 4G off on their devices for onboarding is not an easy task. Has anyone else had this issue with Android or iOS?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have opened a TAC..............no reply as yet.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 23 May 2019 09:02:03 GMT</pubDate>
    <dc:creator>stephendrkw</dc:creator>
    <dc:date>2019-05-23T09:02:03Z</dc:date>
    <item>
      <title>Turning off 4G to get Cisco Network Assitant to work on Android</title>
      <link>https://community.cisco.com/t5/network-access-control/turning-off-4g-to-get-cisco-network-assitant-to-work-on-android/m-p/3861444#M472743</link>
      <description>&lt;P&gt;I finally have BYOD working on ISE 2.4.x with 8.5.x running on my WLC's. Working fine for a week, then I asked a few users in my building to test sitting near the outer ring close to our building windows (my 4G signal is very intermittent in the center of my floor where I sit). Of the 3 users I tested the following error appears after clicking Cisco Network Assistant for Android:&lt;/P&gt;&lt;P&gt;“"&lt;STRONG&gt;Unable to detect Server. Please ensure your network access device is configured to redirect enroll.cisco.com to ISE”&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Came across a few forums referring to DNS named WLC ACL entries nothing seemed a definite solution to me. So I asked the 3 users to turn off 4G on there devices (all Android) suddenly Cisco Network Assistant starts working, users complete onboarding successfully, job complete.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Having a look at packet captures from my Anchor WLC I can clearly see the issue, each user was sending out a request to our BYOD DNS Servers (google Servers 8.8.8.8) over DNS-TLS port 853, the difference was all of these users were sending out SYN packets unlike working Android devices who are completing 3 way handshakes!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;With DNS-TLS obviously I can't see packet information to decode&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Asking users to turn 4G off on their devices for onboarding is not an easy task. Has anyone else had this issue with Android or iOS?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have opened a TAC..............no reply as yet.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 23 May 2019 09:02:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/turning-off-4g-to-get-cisco-network-assitant-to-work-on-android/m-p/3861444#M472743</guid>
      <dc:creator>stephendrkw</dc:creator>
      <dc:date>2019-05-23T09:02:03Z</dc:date>
    </item>
    <item>
      <title>Re: Turning off 4G to get Cisco Network Assitant to work on Android</title>
      <link>https://community.cisco.com/t5/network-access-control/turning-off-4g-to-get-cisco-network-assitant-to-work-on-android/m-p/3861739#M472747</link>
      <description>&lt;P&gt;Apple iOS and Android use Multipath TCP.&amp;nbsp; I've seen this behavior in my lab environment when an iOS device like iPhone doesn't have a very good wifi signal.&amp;nbsp; Unfortunately, the only way I was able to combat the issue was to increase wifi coverage so that the request remains with the wifi network and not go out through the cellular network.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;-Tim&lt;/P&gt;</description>
      <pubDate>Thu, 23 May 2019 15:40:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/turning-off-4g-to-get-cisco-network-assitant-to-work-on-android/m-p/3861739#M472747</guid>
      <dc:creator>Timothy Abbott</dc:creator>
      <dc:date>2019-05-23T15:40:27Z</dc:date>
    </item>
  </channel>
</rss>

