I would suggest checking that your application correctly binds to a hostname and interface correctly, that the port is actively opened by using another tool like netstat, etc before you go digging around in packet captures. Using Wireshark to diagnose a connection problem with your application is generally overkill. Generally, there shouldn't be anything else on your system using Pcap, but we have no way of knowing what is on your system. If you have other tools that require packet capturing they may use pcap. Pcap is a dependency for providing that functionality, as you found out. Wireshark is a tool used to analyze network traffic. I'd like to know what impact replacing WinPcap will have on my system. OK, that's nice and all, but frankly satisfying Wireshark's needs alone isn't what I'm here to do. And according to Wireshark's website, whatever version of WinPcap currently on my system is, “… annoying bugs …” and version 4.1.2 of WinPcap fixes them. I've done another search on that and have found on Wikipedia and see that it is the Windows version of pcap, which stands for packet capture. Early on in the installation it informed me that it wants to update something called WinPcap. I've downloaded Wireshark and have started to install it. Is Wireshark sort of like Fiddler, only including other protocols besides HTTP?Īnd another thing.
I've asked on the MSDN forums, and was told to run something called Wireshark. I've no idea why the target machine (our Windows 2003 Server) should now be actively refusing my connecting to it, when just last week it was all hunky-dory. It's causing me problems saying, “…the target machine actively refused” my attempting to connect to it. I'm working with a WCF service I wrote a few years back, which uses TCP.
0 kommentar(er)
