<?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: MPPE keys, Microsoft PPTP client in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/mppe-keys-microsoft-pptp-client/m-p/213062#M434642</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You shouldn't need to add anything in for these attributes, so just don't enable them.  MPPE will work without them (it *should* just work with only the "MS-CHAP-MPPE-Keys" attribute returned to the NAS).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would suggest going under Interface Config - Radius (Microsoft) and disable the check boxes for these two attributes, then you won't even see them under the User/Group configuration.  They won't be returned to the NAS and the connection should work fine.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If this still doesn't work, then we'd need to see debug output from the router during a connection attempt, so it may be easier to open a TAC case.  What we'd need to see is the following:&lt;/P&gt;&lt;P&gt;&lt;B&gt;&lt;/B&gt;&lt;/P&gt;&lt;P&gt;debug aaa authen&lt;/P&gt;&lt;P&gt;debug aaa author&lt;/P&gt;&lt;P&gt;debug ppp neg&lt;/P&gt;&lt;P&gt;debug ppp auth&lt;/P&gt;&lt;P&gt;debug radius&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 30 Mar 2004 00:28:53 GMT</pubDate>
    <dc:creator>gfullage</dc:creator>
    <dc:date>2004-03-30T00:28:53Z</dc:date>
    <item>
      <title>MPPE keys, Microsoft PPTP client</title>
      <link>https://community.cisco.com/t5/network-access-control/mppe-keys-microsoft-pptp-client/m-p/213061#M434641</link>
      <description>&lt;P&gt;I'm trying to use ACS 2.6 and ACS 3.2 as a radius server to for my Msft win-xp client to do authentication before it brings up its pptp client.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To that end, on ACS, I enable the attributes:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MS-CHAP-MPPE-Keys  (N/A)&lt;/P&gt;&lt;P&gt;MS-CHAP-MPPE-Types (128 bit)&lt;/P&gt;&lt;P&gt;MS-MPPE-Recv-Key (N/A)&lt;/P&gt;&lt;P&gt;MS-MPPE-Send-Key (N/A)&lt;/P&gt;&lt;P&gt;Service-Type (outbound)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, ACS 2.6 and 3.2 require me to enter in a value for MS-MPPE-Recv-Key and MS-MPPE-Send-Key !&lt;/P&gt;&lt;P&gt;I was using an even later implementation of ACS (I think it was 3.32) and that does not require me entering in a value for these two keys .... and ACS 3.32 works just fine.  However, I just can't get 2.6 working... as it wants me to enter in values but I have no idea what to enter.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can somebody who's gotten ACS working in this fashion help?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 14:43:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/mppe-keys-microsoft-pptp-client/m-p/213061#M434641</guid>
      <dc:creator>admin_2</dc:creator>
      <dc:date>2019-03-10T14:43:46Z</dc:date>
    </item>
    <item>
      <title>Re: MPPE keys, Microsoft PPTP client</title>
      <link>https://community.cisco.com/t5/network-access-control/mppe-keys-microsoft-pptp-client/m-p/213062#M434642</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You shouldn't need to add anything in for these attributes, so just don't enable them.  MPPE will work without them (it *should* just work with only the "MS-CHAP-MPPE-Keys" attribute returned to the NAS).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would suggest going under Interface Config - Radius (Microsoft) and disable the check boxes for these two attributes, then you won't even see them under the User/Group configuration.  They won't be returned to the NAS and the connection should work fine.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If this still doesn't work, then we'd need to see debug output from the router during a connection attempt, so it may be easier to open a TAC case.  What we'd need to see is the following:&lt;/P&gt;&lt;P&gt;&lt;B&gt;&lt;/B&gt;&lt;/P&gt;&lt;P&gt;debug aaa authen&lt;/P&gt;&lt;P&gt;debug aaa author&lt;/P&gt;&lt;P&gt;debug ppp neg&lt;/P&gt;&lt;P&gt;debug ppp auth&lt;/P&gt;&lt;P&gt;debug radius&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Mar 2004 00:28:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/mppe-keys-microsoft-pptp-client/m-p/213062#M434642</guid>
      <dc:creator>gfullage</dc:creator>
      <dc:date>2004-03-30T00:28:53Z</dc:date>
    </item>
  </channel>
</rss>

