<?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 Client connectivity Issue in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/client-connectivity-issue/m-p/2214146#M96292</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is the web portal going to be from the ISE or the WLC? If you set up the ISE as both the web authentication portal and Sponsor Portal, then you need to change the Web Authentication Type on the WLC to External Server with and type the DNS resolvable address of the ISE Sponsor portal that you may have created.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you are using the ISE as the authentication server only and WLC as the the web redirect portal, then only the ISE IP address specified as the Radius server is sufficient.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Finally, you need to check if your DNS server is actually up&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 15 Jul 2013 11:03:31 GMT</pubDate>
    <dc:creator>grabonlee</dc:creator>
    <dc:date>2013-07-15T11:03:31Z</dc:date>
    <item>
      <title>Client connectivity Issue</title>
      <link>https://community.cisco.com/t5/wireless/client-connectivity-issue/m-p/2214145#M96291</link>
      <description>&lt;P&gt;Hello All...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have two wlc (5508) configured Foriegn/Anchor method. Mobility tunnel is up, eping &amp;amp; mping were successfull. We configured external DHCP and DNS at the anchor end. web authentication (we use ISE) at L3 level was configured. But when client tries to connect, it gets the IP assignment from dhcp, but it is not getting redirected. When nslookup for any URL also, 'DNS Request timed out' error comes. Any suggestions where exactly i have to check...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;KVS&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 07:25:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-connectivity-issue/m-p/2214145#M96291</guid>
      <dc:creator>Prasan Venky</dc:creator>
      <dc:date>2021-07-04T07:25:15Z</dc:date>
    </item>
    <item>
      <title>Client connectivity Issue</title>
      <link>https://community.cisco.com/t5/wireless/client-connectivity-issue/m-p/2214146#M96292</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is the web portal going to be from the ISE or the WLC? If you set up the ISE as both the web authentication portal and Sponsor Portal, then you need to change the Web Authentication Type on the WLC to External Server with and type the DNS resolvable address of the ISE Sponsor portal that you may have created.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you are using the ISE as the authentication server only and WLC as the the web redirect portal, then only the ISE IP address specified as the Radius server is sufficient.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Finally, you need to check if your DNS server is actually up&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Jul 2013 11:03:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-connectivity-issue/m-p/2214146#M96292</guid>
      <dc:creator>grabonlee</dc:creator>
      <dc:date>2013-07-15T11:03:31Z</dc:date>
    </item>
  </channel>
</rss>

