<?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 Re: Wireless/Wired Connections in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/wireless-wired-connections/m-p/939357#M29368</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It should be possible for you to load a client that disallows/favors one type of media or the other. i.e. Disable WLAN is wire is plugged in, etc.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 02 Apr 2008 05:01:58 GMT</pubDate>
    <dc:creator>jafrazie</dc:creator>
    <dc:date>2008-04-02T05:01:58Z</dc:date>
    <item>
      <title>Wireless/Wired Connections</title>
      <link>https://community.cisco.com/t5/wireless/wireless-wired-connections/m-p/939350#M29361</link>
      <description>&lt;P&gt;What, if any would be the best solution to deal with users connecting to a wired infrastructure but also connected to another organization wireless?  We want to only permit wired when connected.  The end users are not domain controlled but 802.1x authenticated.  Options?  much appreciated.&lt;/P&gt;</description>
      <pubDate>Sat, 03 Jul 2021 22:36:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-wired-connections/m-p/939350#M29361</guid>
      <dc:creator>bradbrookc</dc:creator>
      <dc:date>2021-07-03T22:36:14Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless/Wired Connections</title>
      <link>https://community.cisco.com/t5/wireless/wireless-wired-connections/m-p/939351#M29362</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;one way to do this would be with a supplicant (CSSC). another would be to use CSA (Cisco security Agent)...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Mar 2008 04:32:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-wired-connections/m-p/939351#M29362</guid>
      <dc:creator>sabhasin</dc:creator>
      <dc:date>2008-03-28T04:32:36Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless/Wired Connections</title>
      <link>https://community.cisco.com/t5/wireless/wireless-wired-connections/m-p/939352#M29363</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Do you mean you need to kill WLAN when connected to wired and/or vice-versa?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 29 Mar 2008 03:56:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-wired-connections/m-p/939352#M29363</guid>
      <dc:creator>jafrazie</dc:creator>
      <dc:date>2008-03-29T03:56:21Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless/Wired Connections</title>
      <link>https://community.cisco.com/t5/wireless/wireless-wired-connections/m-p/939353#M29364</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Correct, since potentially the WLAN is another org's &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Mar 2008 13:47:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-wired-connections/m-p/939353#M29364</guid>
      <dc:creator>bradbrookc</dc:creator>
      <dc:date>2008-03-31T13:47:31Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless/Wired Connections</title>
      <link>https://community.cisco.com/t5/wireless/wireless-wired-connections/m-p/939354#M29365</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;one solution is Network Access Quarantine provided by Microsoft IAS/Radius server. As part of the authentication process a script is run on the client to verify it meets the requirements for connection to the network&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is a link to a white paper describing the features.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://download.microsoft.com/download/0/7/e/07ed1953-0ab5-41ea-b5da-41cf8bb9cdae/Quarantine.doc" target="_blank"&gt;http://download.microsoft.com/download/0/7/e/07ed1953-0ab5-41ea-b5da-41cf8bb9cdae/Quarantine.doc&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The client does not have to be a member of the domain.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Bill&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Apr 2008 06:05:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-wired-connections/m-p/939354#M29365</guid>
      <dc:creator>bcolvin</dc:creator>
      <dc:date>2008-04-01T06:05:23Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless/Wired Connections</title>
      <link>https://community.cisco.com/t5/wireless/wireless-wired-connections/m-p/939355#M29366</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Bill, that's great.  Do you know of any way to accomplish the same with freeradius?  IAS is nice but doesn't support as many EAP types as we require.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Apr 2008 14:18:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-wired-connections/m-p/939355#M29366</guid>
      <dc:creator>bradbrookc</dc:creator>
      <dc:date>2008-04-01T14:18:40Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless/Wired Connections</title>
      <link>https://community.cisco.com/t5/wireless/wireless-wired-connections/m-p/939356#M29367</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I don't know of any solutions of this type that don't cost money.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it possible for you clients to standardize on one tyoe of EAP to connect to your system.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;good luck&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Bill&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Apr 2008 04:44:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-wired-connections/m-p/939356#M29367</guid>
      <dc:creator>bcolvin</dc:creator>
      <dc:date>2008-04-02T04:44:36Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless/Wired Connections</title>
      <link>https://community.cisco.com/t5/wireless/wireless-wired-connections/m-p/939357#M29368</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It should be possible for you to load a client that disallows/favors one type of media or the other. i.e. Disable WLAN is wire is plugged in, etc.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Apr 2008 05:01:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-wired-connections/m-p/939357#M29368</guid>
      <dc:creator>jafrazie</dc:creator>
      <dc:date>2008-04-02T05:01:58Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless/Wired Connections</title>
      <link>https://community.cisco.com/t5/wireless/wireless-wired-connections/m-p/939358#M29369</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;which client would recommend?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Apr 2008 16:36:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-wired-connections/m-p/939358#M29369</guid>
      <dc:creator>bradbrookc</dc:creator>
      <dc:date>2008-04-02T16:36:18Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless/Wired Connections</title>
      <link>https://community.cisco.com/t5/wireless/wireless-wired-connections/m-p/939359#M29370</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Juniper Odyssey Access Client.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This can be modified by an Admin and a user MSI file can be produced.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once of the options is to overide WLAN when the device is connected to the Wired network.  You can also restrict wireless access to certain SSIDs or just to WLANs with certain security critera&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Chargeable client though at about $50 a seat.  There is a 15 day full functional demo available to download from the Juniper site.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Paul&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Apr 2008 23:46:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-wired-connections/m-p/939359#M29370</guid>
      <dc:creator>pablo1711</dc:creator>
      <dc:date>2008-04-17T23:46:12Z</dc:date>
    </item>
  </channel>
</rss>

