BTW: You can only add one Loopback Adapter to the system! Beware: Capturing from this Loopback Adapter requires the WinPcap 3.1 release, 3.1 beta versions won't work! Let's suppose you have set the IP address of the loopback adapter to 10.0.0.10 and are capturing on that interface. This adapter is a virtual network adapter you can add, but it will not work on the 127.0.0.1 IP addresses it will take its own IP address. and is quite different than the ones available for various UN*X systems. This adapter is available from Microsoft: Microsoft: How to install the Microsoft Loopback Adapter in Microsoft Windows Server 2003 Microsoft: How to install the Microsoft Loopback adapter in Windows XP Microsoft: How To Install Microsoft Loopback Adapter in Windows 2000. Windows IP 127.0.0.1 You can't capture on the local loopback address 127.0.0.1! IP other You can add a virtual network card called Microsoft Loopback Adapter, but in most cases that might not give results as expected either. Summary: you can capture on the loopback interface on Linux, on various BSDs including Mac OS X, and on Digital/Tru64 UNIX, and you might be able to do it on Irix and AIX, but you definitely cannot do so on Solaris, HP-UX, or Windows. "Supported Platforms See CaptureSetup/NetworkMedia for Wireshark capturing support on various platforms. I can't definitively say that means that loopback traffic doesn't hit the NIC, but it's a pretty good indication. I always had to put one of the network pieces on another machine to see the traffic in wireshark. It makes it a pain in the ass to troubleshoot things like SIP servers locally. ![]() I've never seen loopback traffic in any wireshark traces. Then you could use wireshark as long as that virtual NIC is visible to wireshark. Unless there is some funky virtual NIC that gets created. In this particular situation, I don't think communication between the third party app and IIS ever egress a NIC. Yeah, but with wireshark, you select which interface you're capturing traffic on. I thought this was the whole point of Ethereal and Wireshark. "it keeps having issues when communicating with IIS."ĭo you have a support contract for the third party app? Call them up and get them to help you debug this if it's not working. You will likely break a ton of other applications and the OS itself is you do. "you can add a new route to the routing table to redirect loopback traffic through a second NIC" ![]() Sorry i dont have any experience with servers ![]() I want to do it b/c we have an app server and IIS running on the same machine (this is all part of a third party app, so we have very little access to the inner workings) and it keeps having issues when communicating with IIS. I keep finding obscure references on message boards suggesting you can add a new route to the routing table to redirect loopback traffic through a second NIC.but I can't find anything definitive about it. Sniffing loopback traffic (Windows Server)Īnyone ever done this, or heard rumors of people doing this? Some MS consultant at work told us it could only be done in windows 7, but I need to do it in Server 2003.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |