[vox-tech] tight-vnc, can't ping box from windows

tech_dev(Alex Mandel) tech_dev at wildintellect.com
Wed Jan 26 23:30:03 PST 2005


So I tried tcpdump(or I should say windump) and couldn't figure out how 
to get it to work. But no matter I ran ethereal which seems to give the 
same kinds of info.

Now the question is what am I looking for, I did notice a checksum error 
(not that I understand what that means) down at the bottom.
104 is the win box and 106 is the linux box...
--------------------------------------
No.     Time        Source                Destination           Protocol 
Info
       1 0.000000    192.168.1.104         192.168.1.255         ICMP 
   Echo (ping) reply
       2 0.079423    192.168.1.106         Broadcast             ARP 
   Who has 192.168.1.104?  Tell 192.168.1.106
       3 0.079448    Belkin_1d:31:44       192.168.1.106         ARP 
   192.168.1.104 is at 00:11:50:1d:31:44
       4 0.082732    192.168.1.106         192.168.1.104         ICMP 
   Echo (ping) reply
       5 0.086566    192.168.1.104         192.168.1.106         ICMP 
   Echo (ping) request
       6 5.103971    192.168.1.104         192.168.1.106         ICMP 
   Echo (ping) request
       7 6.530434    192.168.1.100         Broadcast             ARP 
   Who has 192.168.1.151?  Tell 192.168.1.100
       8 10.111055   192.168.1.104         192.168.1.106         ICMP 
   Echo (ping) request
       9 15.118274   192.168.1.104         192.168.1.106         ICMP 
   Echo (ping) request
----------------------------------------------
No.     Time        Source                Destination           Protocol 
Info
       4 0.082732    192.168.1.106         192.168.1.104         ICMP 
   Echo (ping) reply

Frame 4 (104 bytes on wire, 104 bytes captured)
     Arrival Time: Jan 26, 2005 23:08:23.438774000
     Time delta from previous packet: 0.003284000 seconds
     Time since reference or first frame: 0.082732000 seconds
     Frame Number: 4
     Packet Length: 104 bytes
     Capture Length: 104 bytes
Ethernet II, Src: 00:04:5a:5c:0b:3e, Dst: 00:11:50:1d:31:44
     Destination: 00:11:50:1d:31:44 (Belkin_1d:31:44)
     Source: 00:04:5a:5c:0b:3e (192.168.1.106)
     Type: IP (0x0800)
Internet Protocol, Src Addr: 192.168.1.106 (192.168.1.106), Dst Addr: 
192.168.1.104 (192.168.1.104)
     Version: 4
     Header length: 20 bytes
     Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
         0000 00.. = Differentiated Services Codepoint: Default (0x00)
         .... ..0. = ECN-Capable Transport (ECT): 0
         .... ...0 = ECN-CE: 0
     Total Length: 90
     Identification: 0x004e (78)
     Flags: 0x04 (Don't Fragment)
         0... = Reserved bit: Not set
         .1.. = Don't fragment: Set
         ..0. = More fragments: Not set
     Fragment offset: 0
     Time to live: 64
     Protocol: UDP (0x11)
     Header checksum: 0xb622 (correct)
     Source: 192.168.1.106 (192.168.1.106)
     Destination: 192.168.1.104 (192.168.1.104)
Internet Control Message Protocol
     Type: 0 (Echo (ping) reply)
     Code: 137
     Checksum: 0x0089 (incorrect, should be 0x8503)    <----
     Identifier: 0x0046
     Sequence number: 0x55ae
     Data (62 bytes)

0000  80 ff 85 80 00 00 00 01 00 00 00 00 20 45 44 45   ............ EDE
0010  50 46 4a 45 50 46 45 45 46 43 41 43 41 43 41 43   PFJEPFEEFCACACAC
0020  41 43 41 43 41 43 41 43 41 43 41 41 41 00 00 20   ACACACACACAAA..
0030  00 01 00 03 f4 80 00 06 00 00 c0 a8 01 6a         .............j

Thanks again for the help,
Alex

PS: I looked at iptables but couldn't quite decipher what I was looking 
for and nothing stood out as incorrect.

Peter Jay Salzman wrote:
> On Wed 26 Jan 05,  6:31 PM, tech_dev <tech_dev at wildintellect.com> said:
> 
>>Peter Jay Salzman wrote:
...
> 
> Use XP to ping Linux again, but this time, use tcpdump to verify that Linux
> even sees the icmp packets to begin with.
> 
> Pete
> 


More information about the vox-tech mailing list