<?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: Microsft Netbios in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/microsft-netbios/m-p/970011#M19047</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Winson,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I always put my policies under the All Device Group to maintain a global standard across all my WAEs (but it should definitely go under where you manage your global policies), so I start by the following.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Devices/Device Groups/All Device Group/Acceleration/Definitions/&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There I would follow your step 2).  If the R3000 starts working again, then you can incrementally add TFO, then DRE/LZ to see if it works. I might also add a Application to then track the optimizations in the CM GUI if you so desire.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 02 Jun 2008 15:47:49 GMT</pubDate>
    <dc:creator>dstolt</dc:creator>
    <dc:date>2008-06-02T15:47:49Z</dc:date>
    <item>
      <title>Microsft Netbios</title>
      <link>https://community.cisco.com/t5/application-networking/microsft-netbios/m-p/970008#M19044</link>
      <description>&lt;P&gt;In Location A, our users have a mapping drive over the WAN, the mapping will be disconnected in short period when the WAE set up in between LAN switch and WAN router. Another service - content filtering (using 8e6 R3000), it cannot be work in location A after WAE512 installed. It is using Netbios to map the R3000 on client PC, then to define the user profile. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The connectivity is &lt;/P&gt;&lt;P&gt;(Client PC) &amp;lt;-&amp;gt; (LAN Switch) &amp;lt;-&amp;gt; (WAE 512) &amp;lt;-&amp;gt; (WAN Router in Location A) &amp;lt;-&amp;gt; (WAN Router in Location B) &amp;lt;-&amp;gt; (WAE 612) &amp;lt;-&amp;gt; (LAN Switch) &amp;lt;-&amp;gt; (8e6 R3000) &amp;lt;-&amp;gt; (FW) &amp;lt;-&amp;gt; (Internet Router)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WAE OS version is 4.0.13 &lt;/P&gt;</description>
      <pubDate>Mon, 02 Jun 2008 12:34:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/microsft-netbios/m-p/970008#M19044</guid>
      <dc:creator>winsonfu</dc:creator>
      <dc:date>2008-06-02T12:34:21Z</dc:date>
    </item>
    <item>
      <title>Re: Microsft Netbios</title>
      <link>https://community.cisco.com/t5/application-networking/microsft-netbios/m-p/970009#M19045</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Winson,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would add a Application Policy to bypass traffic to the IP address R3000 and then slowly add optimizations back into that policy.  See if that fixes it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Dan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Jun 2008 13:54:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/microsft-netbios/m-p/970009#M19045</guid>
      <dc:creator>dstolt</dc:creator>
      <dc:date>2008-06-02T13:54:49Z</dc:date>
    </item>
    <item>
      <title>Re: Microsft Netbios</title>
      <link>https://community.cisco.com/t5/application-networking/microsft-netbios/m-p/970010#M19046</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Dan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your prompt message.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just clarified that the application policy settings you suggested,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) Create Application policy, &lt;/P&gt;&lt;P&gt;Select Acceleration -&amp;gt; Policies -&amp;gt; Definitions&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) New Application Policy&lt;/P&gt;&lt;P&gt;Type: Basic&lt;/P&gt;&lt;P&gt;Application : Other&lt;/P&gt;&lt;P&gt;Application Classifier : R3000 (defined Destination address)&lt;/P&gt;&lt;P&gt;Action : Passthrough&lt;/P&gt;&lt;P&gt;Accelerate: Do Not Set&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please confirm me the above settings that is your expectation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Winson&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Jun 2008 14:37:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/microsft-netbios/m-p/970010#M19046</guid>
      <dc:creator>winsonfu</dc:creator>
      <dc:date>2008-06-02T14:37:35Z</dc:date>
    </item>
    <item>
      <title>Re: Microsft Netbios</title>
      <link>https://community.cisco.com/t5/application-networking/microsft-netbios/m-p/970011#M19047</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Winson,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I always put my policies under the All Device Group to maintain a global standard across all my WAEs (but it should definitely go under where you manage your global policies), so I start by the following.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Devices/Device Groups/All Device Group/Acceleration/Definitions/&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There I would follow your step 2).  If the R3000 starts working again, then you can incrementally add TFO, then DRE/LZ to see if it works. I might also add a Application to then track the optimizations in the CM GUI if you so desire.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Jun 2008 15:47:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/microsft-netbios/m-p/970011#M19047</guid>
      <dc:creator>dstolt</dc:creator>
      <dc:date>2008-06-02T15:47:49Z</dc:date>
    </item>
  </channel>
</rss>

