Product Support
Product Activation FAQs
Downloads
Maintenance Programs
White Papers
WildPackets Forums
Technical Compendium
Additional Resources
Tip of the Month
Wireless Tips
Plugin Tips
Product Versions
Networking Books
Networking Glossary
Networking Links
Tech Support Requests
Home > Support > Additional Resources > Tip of the Month

Tip of the Month

Network Analysis Tip of the Month – May 2005

Omni DNX Engine Service Scripts and more!

Author – Saurabh Bhasin

I’ve always found the process of exploring through the Start menu -> Programs -> Administrative Tools -> Services to be an over assumption of a user’s familiarity with Windows navigation menus and clicking abilities to arrive at another menu just to start or stop a Windows Service.

Unfortunately, you have had to go through the above mentioned procedure to get to the Omni DNX Engine Service. Read on and change your life forever. There’s a faster way that will save you a few seconds and increase the click life of your mouse!

Fire up notepad and call the file “Peek DNX Start.bat” (the .bat extension is very important as it creates a Windows Batch file). Type the following line “net start peekdnx” and save the file to your desktop. Repeat the same procedure and create another file called “Peek DNX Stop.bat”. You guessed it; the command that goes in the second file is “net stop peekdnx”.

For Advanced Users:

You can take this a step further and add these in your OmniPeek’s Tools menu for direct access from within OmniPeek. Under Tools -> Customize, Click on “Insert”. Type the following to create an entry for starting the DNX Engine:

  • Menu Context - Peek DNX Start
  • Command - C:\WINDOWS\system32\net.exe
  • Arguments – start peekdnx
  • Initial directory – leave this blank

Leave all other options untouched and click on “Ok” and go back to the Tools menu to see your recently created link! Repeat the above steps for a link to stop the service but replace the start with “stop” in the arguments. Look at the following screenshot for an example:

 

Download a demo of OmniPeek
Custom Integration & Engineering
WildPackets understands that one size does not fit all. Moreover, we all face new challenges every day. WildPackets Custom Engineering performs software development and systems integration, complementing WildPackets products and enhancing the capabilities of Network Operations Centers.
Learn more...

Network Analysis & Consulting
WildPackets offers a full spectrum of professional services, available remote and on-site. Our network engineers provide expertise for your network troubleshooting, capacity planning, or baseline performance analysis needs.
Learn more...

Tip of the Month
Don’t Lose The Tags
WildPackets’ Technical Support Team regularly receives questions about capturing VLAN (Virtual LAN) tags in packets. Some customers report that they cannot see VLAN tags when capturing packets from their switches. The tags are usually missing because the capture configuration or the location of OmniPeek (or Omni Engine) is incorrect. So, this tip is aimed at understanding VLAN tags and how they can be captured using OmniPeek Product Family.