<?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 Authentication at connection issues in M and MSM Series</title>
    <link>https://community.hpe.com/t5/m-and-msm-series/authentication-at-connection-issues/m-p/4695512#M3336</link>
    <description>&lt;P&gt;We had initially setup the MSM760 controller on the LAN port, login script ran and users were able to connect. It was then recommended that we move to the Internet Port as we are now looking to setup Guest access. Sometimes users get a 169.154 address, and sometimes they get a valid IP address but the login script doesn't run.&lt;BR /&gt;&lt;BR /&gt;We have also Selected "Internet Port" under Service Controller -&amp;gt; Management -&amp;gt; Device Discovery -&amp;gt; Controlled AP discovery&lt;BR /&gt;&lt;BR /&gt;One fix is to repair their wireless connection and then run the login script&lt;BR /&gt;Could it be an EAPOL setting or some other setting I need to do to move over to the internet port?&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;P.S. This thread has been moved from Communications, Wireless (Legacy ITRC forum) to MSM Series. -HP Forum Moderator&lt;/P&gt;</description>
    <pubDate>Mon, 02 Dec 2013 08:33:39 GMT</pubDate>
    <dc:creator>cedric Naera</dc:creator>
    <dc:date>2013-12-02T08:33:39Z</dc:date>
    <item>
      <title>Authentication at connection issues</title>
      <link>https://community.hpe.com/t5/m-and-msm-series/authentication-at-connection-issues/m-p/4695512#M3336</link>
      <description>&lt;P&gt;We had initially setup the MSM760 controller on the LAN port, login script ran and users were able to connect. It was then recommended that we move to the Internet Port as we are now looking to setup Guest access. Sometimes users get a 169.154 address, and sometimes they get a valid IP address but the login script doesn't run.&lt;BR /&gt;&lt;BR /&gt;We have also Selected "Internet Port" under Service Controller -&amp;gt; Management -&amp;gt; Device Discovery -&amp;gt; Controlled AP discovery&lt;BR /&gt;&lt;BR /&gt;One fix is to repair their wireless connection and then run the login script&lt;BR /&gt;Could it be an EAPOL setting or some other setting I need to do to move over to the internet port?&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;P.S. This thread has been moved from Communications, Wireless (Legacy ITRC forum) to MSM Series. -HP Forum Moderator&lt;/P&gt;</description>
      <pubDate>Mon, 02 Dec 2013 08:33:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/m-and-msm-series/authentication-at-connection-issues/m-p/4695512#M3336</guid>
      <dc:creator>cedric Naera</dc:creator>
      <dc:date>2013-12-02T08:33:39Z</dc:date>
    </item>
    <item>
      <title>Re: Authentication at connection issues</title>
      <link>https://community.hpe.com/t5/m-and-msm-series/authentication-at-connection-issues/m-p/4695513#M3337</link>
      <description>It is hard to comment without knowing the configuration and network environment, but most likely on the guest VSC you should make sure to check the "always tunnel client traffic" (or equivalent) checkbox. This will force the guest traffic to reach the controller without mixing with local network traffic, and that might get you more predictability in this scenario.</description>
      <pubDate>Wed, 06 Oct 2010 12:35:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/m-and-msm-series/authentication-at-connection-issues/m-p/4695513#M3337</guid>
      <dc:creator>Fred!</dc:creator>
      <dc:date>2010-10-06T12:35:36Z</dc:date>
    </item>
  </channel>
</rss>

