<?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>Network Sniffing Tools</title><link>http://blogs.technet.com/neilcar/pages/145799.aspx</link><description>Intro Network sniffing is a major part of my life -- I've probably pored over, on average, a trace a day every day for the past seven years. This is an area where having the right tool is of the upmost importance as a good tool can cut hours (or even</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Network Sniffing Tools</title><link>http://blogs.technet.com/neilcar/pages/145799.aspx#164811</link><pubDate>Thu, 24 Jun 2004 18:40:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:164811</guid><dc:creator>Lukas</dc:creator><description>Hello,&lt;br&gt;     Is there any way to sniff traffic between two devices where device b does not respond to a ping request or any other request?  Keep in mind device b is a embedded board with no OS. I'd like to see what device b is doing during that time.  Any help would be greatly appreciated considering I have been troubleshooting this issue for 4 days now.</description></item><item><title>re: Network Sniffing Tools</title><link>http://blogs.technet.com/neilcar/pages/145799.aspx#164817</link><pubDate>Thu, 24 Jun 2004 18:45:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:164817</guid><dc:creator>Neilcar</dc:creator><description>Lukas,&lt;br&gt;&lt;br&gt;The usual approach there is either to do one of several things:&lt;br&gt;&lt;br&gt;1.  Some switches have tcpdump or something similar on them, so you can run the trace on the switch that device B is connected to.&lt;br&gt;&lt;br&gt;2.  If not, the switch will hopefully support a mirroring/port spanning mode which allows you to mirror the port that device B is on &amp;amp; run your sniffer on a machine connected to that mirrored port.&lt;br&gt;&lt;br&gt;3.  Plug device B and a your sniffer into a hub, plug the hub into the switch.&lt;br&gt;&lt;br&gt;Let me know if that doesn't make sense.</description></item><item><title>re: Network Sniffing Tools</title><link>http://blogs.technet.com/neilcar/pages/145799.aspx#164830</link><pubDate>Thu, 24 Jun 2004 18:55:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:164830</guid><dc:creator>Neilcar</dc:creator><description>One other thing...to use this approach, you'll have to use a sniffer that supports promiscuous mode.  Neither netcap.exe nor the lite version of Netmon that's included with Windows 2000 Server/Windows Server 2003 will work.  You can use the full version of Netmon from SMS or Ethereal with Winpcap.</description></item></channel></rss>