Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-users: Re: [Wireshark-users] Only seeing HTTP responses

From: <ohaya@xxxxxxx>
Date: Thu, 30 Apr 2009 20:28:36 -0400
---- ohaya@xxxxxxx wrote: 
> 
> ---- Guy Harris <guy@xxxxxxxxxxxx> wrote: 
> > 
> > On Apr 29, 2009, at 8:07 PM, ohaya@xxxxxxx wrote:
> > 
> > > I just installed Wireshark, and I'm trying to use it to monitor HTTP  
> > > requests from computers on my network.
> > >
> > > However, when I do an HTTP request (from a different computer,  
> > > 192.168.0.13 on my network), I am only seeing the responses in  
> > > Wireshark (from a website, to 192.168.0.13).
> > 
> > What version of what operating system is on the machine running  
> > Wireshark?
> > 
> > What type of network are you on?  Ethernet?  If so, is it switched?   
> > (Note that some so-called "hubs" are actually switches:
> > 
> > 	http://wiki.wireshark.org/HubReference
> > 
> > ).  Wi-Fi?  If so, what type of network adapter do you have?
> > 
> 
> 
> Hi Guy,
> 
> Actually, I have Wireshark running on a guest under Virtual PC (VPC).  I hadn't mentioned this in my original message, because I didn't think that made a difference.
> 
> On the configuration that I had tried earlier, I had Wireshark running on the VPC guest, and I had been testing by using IE on the VPC host (the physical machine where VPC is running), and as I described earlier, I only was seeing the HTTP responses.
> 
> I just did another test, but this time, instead of running IE on the VPC host, I started a 2nd VPC guest, and ran IE on the 2nd VPC guest.  
> 
> When I did that, I could then see both the HTTP requests (from the IE on the 2nd VPC guest to the website) and the HTTP responses (from the website back to the IE on the 2nd VPC guest).
> 
> So, it seems like there must be something going on with the "virtual" networking and with the VPC guests.  I've posted about this on the MS VPC newsgroup.
> 
> Thanks, and sorry for not mentioning that earlier.
> 
> Jim
> 


Hi,

For the record, I got a response on the MS VPC newsgroup, pointing to this, which I think explains the "why":

http://blogs.msdn.com/virtual_pc_guy/archive/2006/09/27/774228.aspx

Jim