Microsoft Network Monitor 3.0 Beta 2

A new era of network sniffing has begun at Microsoft with the soon to be released Network Monitor 3.0. So, it seems appropriate that we create a Network Monitor Blog site to accompany it. [So this is what a Blog feels like, nice!]

The Essentials

Microsoft Network Monitor 3.0 Beta 2, where is it?

We currently have a Beta version of Network Monitor 3.0 available on our Microsoft Connects site (http://connect.microsoft.com), you'll need a passport account. Select "Available Connections" and look for Network Monitor 3.0. Once you sign up, it will appear in your "My Participation" section. Feel free to download, provide feedback, and use the newsgroups.

Microsoft Network Monitor 3.0 Beta 2, what is it?

Network Monitor 3.0 is a total overhaul of our previous Netmon2.x program. We actually threw out everything and started from scratch. This has produced a much easier and safer way to analyze network traffic.. DLLs for parsers have the inherent problem of overruns, which pose security risks. All of our parsers are based on editable scripts, (Netmon Parsing Language or NPL), which define how protocols are parsed. Nearly 200 of these scripts are included in the beta release and the list keeps growing. Users can easily review and modify these protocol definitions to add their own protocols or update our definitions as they see fit.

Key features of Microsoft Network Monitor 3.0 include:

A completely new user interface

Real time capture and display of frames

Simultaneous capture on multiple network adapters

Multiple simultaneous capture sessions

Network conversations and a tree view displaying frames by conversation

A new script-based protocol parser language, and script-based parsers

Support for Vista/Windows XP/Windows Server 2003

Support for 32bit and 64bit platforms

Who Am I?

My name is Paul Long, and I’ve worked for Microsoft for the last 15 years. Most of my career has been spent in our support organization, and primarily supporting the OS platforms with the Critical Problem Resolution group (CPR). Networking has been my specialty for the last 4 years, though I’ve been involved with networking at many different times in my career. My first job was installing Novell back in the day, and then again with Microsoft’s introduction of Windows for Workgroups 3.1. It was at this time I discovered what a sniffer was, and at that time it was a hunk of a portable (30 lbs Compaq I think), created by Data General. And now my life evolves around Network Monitor 3.0 and its upcoming incarnations.

What is this Blog all about?

The main focus of this Blog is to discuss the features of Network Monitor 3.0 and future versions. This includes how the GUI works, using filters, as well as how NPL works. But I also want to talk about trouble shooting network problems in general and discuss how to apply the features we have in Netmon3.0 towards finding and fixing networking issues.

 

Comments

Post a Comment

Popular posts from this blog

Exchange Server Error -1018: How Microsoft IT Recovers Damaged Exchange Databases

Image
I found this paper on the showcase site from microsoft I hope it is of help to you. It sure helped me!     Technical White Paper Published: August 1, 2005 Executive Summary Error –1018 (JET_errReadVerifyFailure) is a familiar—and dreaded—error in Microsoft® Exchange Server. It indicates that an Exchange database file has been damaged by a failure or problem in the underlying file system or hardware. This paper explains the conditions that result in error –1018. It also covers the detection mechanisms that Exchange uses to discover and recover from damage to its database files. The Microsoft Information Technology group (Microsoft IT) runs one of the most extensive Exchange Server organizations in the world. Exchange administrators at Microsoft have investigated and recovered from dozens of –1018 error problems. This paper shows you how Microsoft IT monitors fo
Read more

Server and Domain Isolation Using IPsec and Group Policy

Image
Microsoft Solutions for Security and Compliance Server and Domain Isolation Using IPsec and Group Policy © 2006 Microsoft Corporation. This work is licensed under the Creative Commons Attribution-NonCommercial License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc/2.5/ or send a letter to Creative Commons, 543 Howard Street, 5th Floor, San Francisco, California, 94105, USA. Table of Contents Chapter 1: Introduction to Server and Domain Isolation. 1 Executive Summary. 1 Who Should Read This Guide. 2 The Business Challenge. 3 The Business Benefits. 3 The Technology Challenge. 4 Creating a Project Team.. 6 Guide Overview.. 7 Chapter 1: Introduction to Server and Domain Isolation. 7 Chapter 2: Understanding Server and Domain Isolation. 7 Chapter 3: Determining the Current State of Your IT Infrastructure. 7 Chapter 4: Designing and Planning Isolation Groups. 8 Chapter 5: Creating IPsec Policies for Isolation Groups.
Read more

[Solved] The Group Policy client-side extension Internet Explorer Zonemapping failed to execute

Image
I had the error below in my application eventlog.     Event Type:    Error Event Source:    Userenv Event Category:    None Event ID:    1085 Date:        30-09-2008 Time:        15:20:30 User:        NT AUTHORITY\SYSTEM Computer:    TBG-TS01 Description: The Group Policy client-side extension Internet Explorer Zonemapping failed to execute. Please look for any errors reported earlier by that extension. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp .   My problem was with my site to zone assignment list I used a wildcard like this: “ *microsoft.com ” but what you need to do is this “ *.microsoft.com ” So it is safe to say that the documentation from microsoft needs some sort of an update stating that you can only use a wildcard infront of dot. Below is the microsoft explaination:   This policy setting allows you to manage a list of sites that you want to associate with a particular s
Read more