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

May 2001

New Tricks for IP Tools

As a network analyst, an extended IP tool utility should always be a part of your analysis toolbox. These tools extend the capability of the venerable Ping and other command line utilities included with virtually every operating system. They also provide an easier to use and easier to integrate interface to the end-user.

Most tools integrate the usual Ping, Trace Route, Name Lookup (DNS), etc., into a single utility. Many include more advanced options such as the ability to scan ports and ranges of IP addresses. One such advanced tool, WildPackets' iNetTools (integrated with WildPackets' analyzers or available separately) can even do a spot check on a web server's throughput.

Are IP address and UDP/TCP port scanners just for hackers?

Besides the obvious devious use of scanners, these tools can be put to good use. For example, if a user can't connect to a server that's supposed to have Web services, you might conduct a port scan on that server. Assuming that the server's HTTP service has not been remapped from the "well-known" port of 80, you should see a response.

Or perhaps you want to make sure that your firewall is blocking certain ports. Chances are, you will have full access to a server inside of your Intranet, so you need to run a port scan from the outside in. One way to do this is to dial-up to a service provider outside of your intranet, then run the port scan.

You've undoubtedly performed Ping one or two or a thousand times, but what about when you want to check on a range of addresses? By using the iNetTools Ping Scan, you can choose a range of IP addresses (for example, 10.1.2.1 through 10.1.2.100) and see who replies. Automatic DNS resolution may also reveal the name of the devices.

Hey, as long as you're on that dial-up connection, use the iNetTools Throughput tool for a quick throughput test. It'll tell you the number of files associated with that page and how long it's taking to get each file. Repeat the test a few times to get a feel for the averages. Never hurts to check the response time of your web site that half the world sees on dial-up connections!

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.