What’s happening in this picture? Use Netmon to figure it out?

Ok, here’s an interesting picture from my network this morning.  Can you figure out what’s going on?  Is Windows 7 confused?  By the way, Netmon 3.x is a really powerful network tool.  I was using it yesterday to diagnose a completely different question.


Get Netmon 3.2 @ http://www.microsoft.com/downloads/details.aspx?FamilyID=f4db40af-1e08-4a21-a26b-ec2f4dc4190d&DisplayLang=en.  See the Netmon blog @ http://blogs.technet.com/netmon/.

Comments (5)

  1. Peder Vendelbo Mikkelsen says:

    I think the top map is showing wireless connections to a wireless access point, the middle map is showing a wired connection (i cant remember if IPv4 and IPv6 is shown with different colours), i think the connections are active at the same time.

    The bottom map is showing a device connecting only wirelessly with the wireless acces point.

    At first i thought the lines from the computers to the network devices did show the relative speed with which the network operates, but i checked your routers specifications and it doesnt do any kind of wireless networking.

  2. Keith Combs says:

    You have part of the puzzle.

  3. Peder Vendelbo Mikkelsen says:

    It looks like you are sharing the connection between the machines:

    keithcot61p is sharing the wireless connection on win7drt.

    win7drt is sharing the wired connection on keithcot61p.

    venus has its own wireless connection.

    win7drt could be a virtual machine on keithcot61p, perhaps even booting from a virtual machine image on venus.

    I guess you run W2K8R2 on the laptop and W7 on the virtual machine.

    And you can connect to venus from both connections, are you playing around with homegroups?

    If the wireless access point handle dhcp for the wireless clients you probably have some issues with resolving the names of the machines, at least the mac-address table on the router must look funny because the machines have more than one IP-address.

    I cant think of what you are trying to achieve with that kind of network-setup, besides playing around and see how Windows 7 handles what seems like a imitated network-loop (unless you test the Hyper-V management tools on Windows 7).

  4. Keith Combs says:

    Not even close on that one.  It’s really much simpler.

    There is a wired router, the D-Link which is the gateway to the internet.  It of course is the DHCP server.

    There are two wireless bridges.  One is in my home office area of the house, the other is in the den at the entertainment center.  The wireless bridges are on the GigE backbone.

    win7drt and keithcot61p are in the homeoffice area directly connected to the wired GigE network.  Because they are both laptops and have wireless, they are also connected to the network across wireless.

    venus is my wife’s laptop and is in use in the den via wireless.

  5. Peder Vendelbo Mikkelsen says:

    When i run beta-software i sometimes play around with it and make misconfigurations on purpose to see how it reacts, if i see the same failure again i can sometime remember what i did to provoke the failure and solve the problem really fast. I thought perhaps you did the same in preparation for a presentation where you were demonstrating the Problem Recorder software in Windows 7.

    That gives me an idea, how about a webcast series about what really happens (and what it looks like from a client-pcs point of view) when important infrastructure fails, with recordings showing what the early warnings look like (after 15 minutes, 30 minutes, 2 days and so on).

    Perhaps even a webcast showing how System Center would see the situation. I got the idea with System Center from this XKCD comic:


Skip to main content