Stopping a Sniffer Trace Automatically When a Server FailsLast reviewed: April 11, 1997Article ID: Q110619 |
The information in this article applies to:
NOTE: This article applies only to failures of servers and Windows for Workgroups or Windows NT workstations. If you are trying to stop a Sniffer trace automatically when a Microsoft LAN Manager workstation fails, use article Q110553, titled:
"Stopping Sniffer Trace Automatically When an LM WS Fails" SYMPTOMSIt is difficult to capture network traces at the time of a server failure when there is nobody there to notice and stop the Sniffer.
RESOLUTIONThe following is one possible method to automatically trigger a Sniffer on server failure. This method involves running a batch file on one machine that repeatedly attempts to establish a connection to the server(s) in question. Upon detecting a failure at the server, the batch file sends a broadcast message (STOP THE SNIFF) to the domain, which the Sniffer triggers on. The batch file: rem USAGE: stopsnif [servername] [interval] :start net view \\%1 if ERRORLEVEL 1 goto bailout delay %2 goto start rem rem The connection attempt failed. Stop the Sniffer! :bailout net send /d:davemacd STOP THE SNIFF @echo @echo Well, hopefully the Sniffer stopped! Depending on the protocol, the text string "STOP THE SNIFF" may appear at different offsets in your trace. It is therefore necessary to do the following:
|
Additional query words: wfw wfwg prodnt
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |