<< | Thread Index | >> ]    [ << | Date Index | >> ]

To: CIPE <cipe-l,AT,inka,DOT,de>
Subject: Re: tcpdump - laptop
From: James Knott <james.knott,AT,rogers,DOT,com>
Date: Thu, 11 Sep 2003 22:43:33 -0400
In-reply-to: <008401c378a2$d02c38e0$d620a8c0@pcw_hans.hnsasd.priv>
References: <008401c378a2$d02c38e0$d620a8c0@pcw_hans.hnsasd.priv>

Hans Steegers wrote:
James,
I'll give it another (last!) try:

What all those packet dumps tell me is this:

1. there was no file transfer at all: all dumps contained only small
(protocol) packets. conclusion: the SAMBA server didn't even try to transfer
a file.

2. For a 'failing PMTU discovery' problem, we should have seen at least 1
large packet. Since there are none we have to look further.

3. The cipe interface 192.168.2.20 on the notebook informed the server
92.168.1.10 that port 138/udp is (blocked or not listening:) unreachable,
after receiving an NBT UDP PACKET(138) from the server. We can follow the
NBT packet from server to notebook and the ICMP answer from notebook to
server. So the server stopped. What tell the Samba logs?

** Find the reason why cipe cannot pass on port 138/udp packets to the lo
interface on the notebook:

-> Check with 'netstat -lun' on the notebook if listening on ports 137 and
138.
you should see something like:
..
udp        0      0 192.168.2.20:137        0.0.0.0:*
udp        0      0 0.0.0.0:137             0.0.0.0:*
udp        0      0 192.168.2.20:138        0.0.0.0:*
udp        0      0 0.0.0.0:138             0.0.0.0:*

Here it is again, while connected via Wi-fi.


Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
udp        0      0 0.0.0.0:32768           0.0.0.0:*
udp        0      0 0.0.0.0:2049            0.0.0.0:*
udp        0      0 0.0.0.0:32769           0.0.0.0:*
udp        0      0 0.0.0.0:32770           0.0.0.0:*
udp        0      0 0.0.0.0:10000           0.0.0.0:*
udp        0      0 0.0.0.0:666             0.0.0.0:*
udp        0      0 192.168.3.166:6969      0.0.0.0:*
ESTABLISHED
udp        0      0 0.0.0.0:7741            0.0.0.0:*
udp        0      0 0.0.0.0:68              0.0.0.0:*
udp        0      0 0.0.0.0:111             0.0.0.0:*
udp        0      0 0.0.0.0:631             0.0.0.0:*

This time, I can successfully access shares on the server and there are
no new entries in log.nmbd or log.smbd.  I still don't see any reference
to ports 137 or 138.

..


<< | Thread Index | >> ]    [ << | Date Index | >> ]