[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wireshark-users
Subject:    Re: [Wireshark-users] my traffic not captured
From:       "David Sheats, Friendly Computer Service" <david.sheats () yahoo ! com>
Date:       2014-03-19 18:50:45
Message-ID: BAF3D1B7666342F381C6B3C9B9C7E60B () lugnut
[Download RAW message or body]

Ohhh, I see what I did.  It was a network byte-ordering problem.  I wanted 
it to connect to port 2022 (07e6 hex), but it was switching the bytes around 
such that I was actually connecting to port 58887 (e607 hex).  My eye had 
been skipping right past the captured packets because I assumed they were 
for some other protocol!

Thanks for you the help, Guy and Anne.

(I am relatively new to using email lists such as this- will Anne also get 
this message, or do I have to reply specifically to her email in order for 
her to see it?)

-David



----- Original Message ----- 
From: "Guy Harris" <guy@alum.mit.edu>
To: "Community support list for Wireshark" <wireshark-users@wireshark.org>
Sent: Wednesday, March 19, 2014 1:44 PM
Subject: Re: [Wireshark-users] my traffic not captured


>
> On Mar 19, 2014, at 7:08 AM, "David Sheats, Friendly Computer Service" 
> <david.sheats@yahoo.com> wrote:
>
>>      I am writing a program that makes use of Windows Sockets, and I 
>> thought I might use Wireshark to watch the traffic go back and forth 
>> across my network.  However, the Shark doesn't seem to capture the 
>> packets generated by my program.
>>      I send data from the client computer to the server computer using a 
>> regular TCP connection onto port 2022 of the server.  I know the server 
>> is receiving the information, because it is able to print it on the 
>> screen.
>>      Wireshark seems to be capturing other data just fine, such as HTTP 
>> traffic on port 80, and VNC traffic (I use that to fiddle with my server 
>> so I don't have to walk back and forth between my computers).
>
> Is it capturing other traffic *between the client and server in question*?
>
> ___________________________________________________________________________
> Sent via:    Wireshark-users mailing list <wireshark-users@wireshark.org>
> Archives:    http://www.wireshark.org/lists/wireshark-users
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
> 
> mailto:wireshark-users-request@wireshark.org?subject=unsubscribe 

___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users@wireshark.org>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request@wireshark.org?subject=unsubscribe
[prev in list] [next in list] [prev in thread] [next in thread]