This is a static archive of our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

Capture SOAP traffic from a virtual Windows to Mac OS X host?

0

My host is a Mac OS X 10.8 machine with a virtual Windows 8 residing in Parallels 8. The Mac's ethernet address is 172.168.10.100, the Win machine shows 172.168.10.115 and is "pc-rrupp-win8.testdomain.com". Parallel's is setup to use "bridged network over Ethernet". On the Windows machine, I'm running a web service which is called from a Mono C# application that is running on the Mac host. I would like to capture all the reply XML that is sent back by the Windows' service. However all I get is: nothing :-( I tried to use the ethernet adapter, as well as the loopback device but filtering for 172.168.10.115 does not show any responses. However, I can see the response in my Mac's C# application.

Is there maybe a sample around that would show the usage of Wireshark in combination with Parallels?

asked 20 May '13, 09:44

Krumelur's gravatar image

Krumelur
11112
accept rate: 0%


One Answer:

0

You could run Wireshark in your Windows 8 virtual machine and capture the traffic there.

device but filtering for 172.168.10.115 does not show any responses.

What was your display filter for this?

BTW: Can you post the output of the following command?

ifconfig -a

Regards
Kurt

answered 20 May '13, 11:50

Kurt%20Knochner's gravatar image

Kurt Knochner ♦
24.8k1039237
accept rate: 15%

edited 20 May '13, 11:55

I'll try that. The reason why I wanted to do it on the Mac: I'm hunting a bug here that has to do with corrupt network traffic (deserialization fails). I tried with Fiddler on Windows but as soon as I do that to analyze the traffic, it starts working. But maybe Wireshark is less "intrusive".

(20 May '13, 11:58) Krumelur

Fiddler is a HTTP/HTTPS proxy. Usually it will simply forward the request, but in certain situations it will change the communication behavior. Wireshark is 'non-intrusive' (even on Windows) and it will show the whole communication, as it is sent to the NIC. So, you should be able to troubleshoot your problem with Wireshark on Windows.

(20 May '13, 12:07) Kurt Knochner ♦