Defrag Tools #175 - Debugging the Network Stack

Sign in to queue

The Discussion

  • User profile image

    Hello Guys, great show, this new way of viewing dumps and is really great.

    - I wish that you could do more episodes with windbg cmds for real troubleshooting scenarios, for example NIC dropped packets, communication errors, how to search and related the threads where communications were happening and how to check the destination IPs where communicating at the time of the crash, I also have seen some weird problems with arp cache that I usually solve by clean it with arp -d cmd, but not sure why it happens, can we catch router related errors like spanning tree, etc... (Is it possible to do this post-morten/LiveDebug or we still need a network analyzer to get that information).

    - I tested this on some crashes that I have for Windows 2008 and appears the report will not show all information, for example IP Address is missing and I get some symbol resolution errors for  tcpip!_IP_PROTOCOL, tcpip!_IP_INTERFACE, perhaps it only works for latter OS??!!

    - I have a final question regarding to new protocols introduced since windows vista, appears that when we`re using a given IP in a given subnet and we try to ping an online address in the same subnet, pathping will show that we`re using the correct interface (with the same IP for the same subnet), but when the IP does not exist or the destination server is offline, Windows will try to use the interface with default Gateway!!! Do you know if this behavior is related with any of the newer protocols introduced in windows Vista (in previous OS this didn`t happen)?

    Thank you for all the great shows, learning a lot...

  • User profile image
    Steve Madden

    I found a website from which i get rid out of this type of error problem, now you can also check this for getting rid of it completely:

  • User profile image

    I like that stuff, more of this, please! :)

Add Your 2 Cents