<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Computer Support &#187; network traffice</title>
	<atom:link href="http://www.xiitec.com/blog/tag/network-traffice/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.xiitec.com/blog</link>
	<description></description>
	<lastBuildDate>Wed, 30 Dec 2009 08:40:28 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Viewing Network Traffic</title>
		<link>http://www.xiitec.com/blog/2008/02/15/viewing-network-traffic/</link>
		<comments>http://www.xiitec.com/blog/2008/02/15/viewing-network-traffic/#comments</comments>
		<pubDate>Fri, 15 Feb 2008 23:35:02 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Networking]]></category>
		<category><![CDATA[network traffice]]></category>

		<guid isPermaLink="false">http://www.xiitec.com/blog/?p=135</guid>
		<description><![CDATA[This is useful when you need to troubleshoot or debug application problems or  system communications failures. Particularly when you are having problems with a  particular protocol, such as LDAP or DNS, looking at the associated network  traffic can be helpful to see what is being transmitted and received.

&#160;


&#160;
Open the Network Monitor tool [...]]]></description>
			<content:encoded><![CDATA[<p>This is useful when you need to troubleshoot or debug application problems or  system communications failures. Particularly when you are having problems with a  particular protocol, such as LDAP or DNS, looking at the associated network  traffic can be helpful to see what is being transmitted and received.</p>
<p><span id="more-135"></span></p>
<p style="font-weight: bold">&nbsp;</p>
<ol class="docList" type="1">
<li>
<p style="font-weight: normal">&nbsp;</p>
<p class="docList">Open the Network Monitor tool  (<em>netmon.exe</em>). Network Monitor is not installed by default. To install  it:</p>
<p style="font-weight: bold">&nbsp;</p>
<ol>
<li>Go to the Control Panel and open the <span class="docEmphBold">Add or Remove Programs</span> applet.</li>
<li>Click on <span class="docEmphBold">Add/Remove Windows  Components</span>.</li>
<li>Double-click on <span class="docEmphBold">Management and  Monitoring Tools</span>.</li>
<li>Check the box beside <span class="docEmphBold">Network Monitor  Tools</span> and click <span class="docEmphBold">OK</span>.</li>
<li>Click <span class="docEmphBold">Next</span>.</li>
<li>Click <span class="docEmphBold">Finish</span>.</li>
</ol>
<ol class="docList" type="a"></ol>
</li>
<li>
<p style="font-weight: normal">&nbsp;</p>
<p class="docList">The first time you start Network Monitor, you will be asked  from which network interface you want to capture data. On Windows Server 2003,  Microsoft finally made the list of interfaces to choose easy to distinguish  because they labeled each one by its connection name (e.g., <span class="docEmphBold">Local Area Connection</span>). With Windows 2000, it doesn&#8217;t  include that information in the label, so choosing an interface is almost a  guessing game unless you know the MAC address prefix of your NIC card vendor. A  trick you can use to narrow the list of interfaces is to disregard any that have  a <span class="docEmphBold">Dial-up connection</span> setting marked as TRUE.  After you&#8217;ve selected an interface, click <span class="docEmphBold">OK</span>.</p>
</li>
<li>
<p style="font-weight: normal">&nbsp;</p>
<p class="docList">From the menu, select <span class="docEmphBold">Capture</span> &gt; <span class="docEmphBold">Start</span>.  If you don&#8217;t see the <span class="docEmphBold">Network Utilization</span> and  <span class="docEmphBold">Frames Per Second</span> indicators fluctuating (a sign  traffic is being captured), you likely picked the wrong interface in Step 2. If  so, stop the capture by selecting <span class="docEmphBold">Capture</span> &gt; <span class="docEmphBold">Stop</span> from  the menu. Then select <span class="docEmphBold">Capture</span> &gt; <span class="docEmphBold">Networks</span>.  You&#8217;ll be presented with the same screen as in Step 2 that allows you to select  the target interface.</p>
</li>
<li>
<p style="font-weight: normal">&nbsp;</p>
<p class="docList">When you want to stop the capture, select <span class="docEmphBold">Capture</span> &gt; <span class="docEmphBold">Stop</span> from the menu. Or if you want to immediately view  the traffic, select <span class="docEmphBold">Capture</span> &gt; <span class="docEmphBold">Stop and  View</span>.</p>
</li>
<li>
<p style="font-weight: normal">&nbsp;</p>
<p>If the captured data is too much to look at, you can filter it  by selecting <span class="docEmphBold">Display</span> &gt; <span class="docEmphBold">Filter</span> from  the menu. From there you can enter Boolean expressions to limit what is  displayed.</li>
</ol>
<p><strong>Using a command-line interface</strong></p>
<p>The Windows Server 2003 Support Tools contains a new tool called  <em>netcap.exe</em> that can capture packets to a file for viewing later in  Network Monitor. Here is an example command line:</p>
<pre>&gt; netcap /C:d:\netcap.cap /N:1</pre>
<p>This command captures packets on interface #1 and stores the  output in <em>d:\netcap.cap</em>. To make sure you are capturing on the correct  interface, view the <em>netcap</em> help information:</p>
<pre>&gt; netcap /?</pre>
<p>At the very end, it displays the list of interfaces on the  system and their associated numbers. To view the contents of the capture file,  double-click it. This will launch the Network Monitor.</p>
<p>Network Monitor (NetMon) is not the most user-friendly tool,  but it offers powerful features for collecting, filtering, and analyzing a  network capture. For more on how to use some of the features of NetMon, see the  MS KB articles listed in the See Also section.</p>
<p>One thing that is worth noting about NetMon is that it has a  default buffer limit of 1 MB. After the data it captures exceeds 1 MB, it begins  to overwrite the oldest packets using FIFO (first in, first out). You can  increase the size of the buffer to a max of 1 GB. To increase the buffer, select  <span class="docEmphBold">Buffer Settings</span> from the <span class="docEmphBold">Capture</span> menu. Enter the maximum number of megabytes and  click <span class="docEmphBold">OK</span>.</p>
<p>If you are interested in an alternative to NetMon, Ethereal is  one of the most popular network traffic analyzers and it is available free from  the following site: <a href="http://www.ethereal.com/" class="docLink" target="_blank">http://www.ethereal.com/</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.xiitec.com/blog/2008/02/15/viewing-network-traffic/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

