<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>NMCap: the easy way to Automate Capturing</title><link>http://blogs.technet.com/netmon/archive/2006/10/24/nmcap-the-easy-way-to-automate-capturing.aspx</link><description>OK, I'm not going to blow smoke up your Async port. I don't mean to say that the NMCap is necessarily easy to use, though it's not that hard. But any command line utility always has its quirks. Isn't that why GUI was invented? What NMCap does make easy,</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: NMCap: the easy way to Automate Capturing</title><link>http://blogs.technet.com/netmon/archive/2006/10/24/nmcap-the-easy-way-to-automate-capturing.aspx#479384</link><pubDate>Wed, 25 Oct 2006 21:54:05 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:479384</guid><dc:creator>HeatfanJohn</dc:creator><description>&lt;p&gt;This is great information.&lt;/p&gt;
&lt;p&gt;FYI, I had to turn off the &amp;quot;Enable local only&amp;quot; option on a capture to be able to capture packets that weren't addressed to my PC. &amp;nbsp;My guess is that turning this off turns on promiscuous mode for the packet capture. &amp;nbsp;I briefly reviewed the Netmon3 user guide and I didn't see anything on this.&lt;/p&gt;
&lt;p&gt;You might want to highlight this somewhere as this is a change from NM2 which I believe ran in promiscuous mode by default.&lt;/p&gt;
&lt;p&gt;We were spanning traffic through our Cisco network and I didn't see the traffic by default using NM3, but did with other software and NM2.&lt;/p&gt;
&lt;p&gt;The capture only local traffic also shows up in two areas. &amp;nbsp;It shows up under options and also under the capture. &amp;nbsp;I had to uncheck this under capture for it to take effect.&lt;/p&gt;
&lt;p&gt;John&lt;/p&gt;
</description></item><item><title>re: NMCap: the easy way to Automate Capturing</title><link>http://blogs.technet.com/netmon/archive/2006/10/24/nmcap-the-easy-way-to-automate-capturing.aspx#506553</link><pubDate>Tue, 07 Nov 2006 20:17:53 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:506553</guid><dc:creator>PaulELong</dc:creator><description>&lt;p&gt;Thanks John. &amp;nbsp;I've sent a note to our team to try and document this in the release notes.&lt;/p&gt;
&lt;p&gt;Paul&lt;/p&gt;
</description></item><item><title>re: NMCap: the easy way to Automate Capturing</title><link>http://blogs.technet.com/netmon/archive/2006/10/24/nmcap-the-easy-way-to-automate-capturing.aspx#541392</link><pubDate>Tue, 05 Dec 2006 15:25:59 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:541392</guid><dc:creator>alicain</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I like the ability to filter from the command line with &amp;quot;NMCap /InputCapture&amp;quot; &lt;/p&gt;
&lt;p&gt;I think there are a couple of typos there...the following seems to work :&lt;/p&gt;
&lt;p&gt;NMCap /InputCapture test.cap /capture Ipv4.Address ==10.0.0.1 /file c1.cap &lt;/p&gt;
&lt;p&gt;Ali.&lt;/p&gt;
</description></item><item><title>re: NMCap: the easy way to Automate Capturing</title><link>http://blogs.technet.com/netmon/archive/2006/10/24/nmcap-the-easy-way-to-automate-capturing.aspx#541434</link><pubDate>Tue, 05 Dec 2006 17:33:21 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:541434</guid><dc:creator>PaulELong</dc:creator><description>&lt;p&gt;Ali, thanks for the corrections. &amp;nbsp;I've fixed the typos in the blog.&lt;/p&gt;
&lt;p&gt;Paul&lt;/p&gt;
</description></item><item><title>EventMon: Stopping a Capture Based on an EventLog Event</title><link>http://blogs.technet.com/netmon/archive/2006/10/24/nmcap-the-easy-way-to-automate-capturing.aspx#658158</link><pubDate>Thu, 22 Feb 2007 23:59:22 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:658158</guid><dc:creator>Network Monitor</dc:creator><description>&lt;p&gt;Having worked in Product Support for many years, I’ve had many occasions where a specific Event Log error&lt;/p&gt;
</description></item><item><title>re: NMCap: the easy way to Automate Capturing</title><link>http://blogs.technet.com/netmon/archive/2006/10/24/nmcap-the-easy-way-to-automate-capturing.aspx#1837947</link><pubDate>Mon, 27 Aug 2007 12:42:10 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:1837947</guid><dc:creator>SuperBfred</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;Do you have plans to provide more sophisticated automation interface. COM or .Net ?&lt;/p&gt;
&lt;p&gt;It would be handy. In fact relying on shell commands is not the way to go&lt;/p&gt;
&lt;p&gt;Regards&lt;/p&gt;
</description></item><item><title>re: NMCap: the easy way to Automate Capturing</title><link>http://blogs.technet.com/netmon/archive/2006/10/24/nmcap-the-easy-way-to-automate-capturing.aspx#1839449</link><pubDate>Mon, 27 Aug 2007 16:35:51 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:1839449</guid><dc:creator>PaulELong</dc:creator><description>&lt;p&gt;One of our goals for the next version is to provide some kind of API so that you can capture, store, and analyze trace data using our engine. &amp;nbsp;As for a COM or .Net interface, we probably will try to provide a managed interface, but I can't be sure if that will be provided at the same time.&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Paul&lt;/p&gt;
</description></item><item><title>General network errors (GNEs), Timeout expired, SQL Server not found or Access Denied…</title><link>http://blogs.technet.com/netmon/archive/2006/10/24/nmcap-the-easy-way-to-automate-capturing.aspx#1909024</link><pubDate>Thu, 06 Sep 2007 16:29:13 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:1909024</guid><dc:creator>Microsoft SQL Server Support Blog</dc:creator><description>&lt;p&gt;Many times, the key to solving these errors is a network packet trace. The problem is that these errors&lt;/p&gt;
</description></item><item><title>NMCap: the easy way to Automate Capturing, .cap file</title><link>http://blogs.technet.com/netmon/archive/2006/10/24/nmcap-the-easy-way-to-automate-capturing.aspx#3036555</link><pubDate>Mon, 14 Apr 2008 13:38:19 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3036555</guid><dc:creator>ilpostino</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;is there a way to read the data from the .cap file for example if i want to get HTTP Headers from captured frames &lt;/p&gt;
&lt;p&gt;Thanks.&lt;/p&gt;
</description></item><item><title>re: NMCap: the easy way to Automate Capturing</title><link>http://blogs.technet.com/netmon/archive/2006/10/24/nmcap-the-easy-way-to-automate-capturing.aspx#3036659</link><pubDate>Mon, 14 Apr 2008 16:28:47 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3036659</guid><dc:creator>PaulELong</dc:creator><description>&lt;p&gt;Today, you'd have to use the UI and add a column for the HTTP header. &amp;nbsp;Then you could export that data from the UI by Cut &amp;amp; Pasting, for instance, into Excel. &amp;nbsp;Then you could extract that one column.&lt;/p&gt;
&lt;p&gt;In the next version, NM3.2, you'll be able to use the NMAPI to extract that data programmatically. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Paul&lt;/p&gt;
</description></item><item><title>re: NMCap: the easy way to Automate Capturing</title><link>http://blogs.technet.com/netmon/archive/2006/10/24/nmcap-the-easy-way-to-automate-capturing.aspx#3037434</link><pubDate>Tue, 15 Apr 2008 13:34:37 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3037434</guid><dc:creator>ilpostino</dc:creator><description>&lt;p&gt;Hello again,&lt;/p&gt;
&lt;p&gt;Do you have a library for all command and parameters?&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
</description></item><item><title>re: NMCap: the easy way to Automate Capturing</title><link>http://blogs.technet.com/netmon/archive/2006/10/24/nmcap-the-easy-way-to-automate-capturing.aspx#3037504</link><pubDate>Tue, 15 Apr 2008 16:21:59 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3037504</guid><dc:creator>PaulELong</dc:creator><description>&lt;p&gt;The next version will also contain a NetmonSDK.CHM with information about all the API calls and examples. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Paul&lt;/p&gt;
</description></item><item><title>re: NMCap: the easy way to Automate Capturing</title><link>http://blogs.technet.com/netmon/archive/2006/10/24/nmcap-the-easy-way-to-automate-capturing.aspx#3037965</link><pubDate>Wed, 16 Apr 2008 13:05:40 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3037965</guid><dc:creator>ilpostino</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I am very sorry for disturbing you but i realy need a way to automate capturing, so i need to capture HTTP responses and requests on the port 1000 of my PC&lt;/p&gt;
&lt;p&gt;i tried with: /capture &amp;quot;http.port == 1000&amp;quot;&lt;/p&gt;
&lt;p&gt;it doesnt work &lt;/p&gt;
&lt;p&gt;it wil be ok if i could just specify the port 1000 without the http filter&lt;/p&gt;
&lt;p&gt;finaly is there any option for /network so i can limit the capture to my own PC without need to specify my IP address?&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
</description></item><item><title>re: NMCap: the easy way to Automate Capturing</title><link>http://blogs.technet.com/netmon/archive/2006/10/24/nmcap-the-easy-way-to-automate-capturing.aspx#3038027</link><pubDate>Wed, 16 Apr 2008 16:26:35 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3038027</guid><dc:creator>PaulELong</dc:creator><description>&lt;p&gt;The port information is part of TCP not HTTP. &amp;nbsp;so waht you want is &amp;quot;/capture tcp.port == 1000&amp;quot;.&lt;/p&gt;
&lt;p&gt;By default when you capture with NMCap, you only see traffic comming to your machine. &amp;nbsp;You actually have to add an option /DisableLocalOnly, to see traffic that's not destine for you machine.&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Paul&lt;/p&gt;
</description></item><item><title>The Quick and Easy on Using NMCap to Create Circular Network Traces Based on File Size</title><link>http://blogs.technet.com/netmon/archive/2006/10/24/nmcap-the-easy-way-to-automate-capturing.aspx#3113014</link><pubDate>Thu, 28 Aug 2008 00:42:19 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3113014</guid><dc:creator>Microsoft Enterprise Networking Team</dc:creator><description>&lt;p&gt;Hello all Networking Blog readers.&amp;amp;#160; My name is Brett Crane and I am an engineer with the Networking&lt;/p&gt;
</description></item></channel></rss>