What's this 135/UDP traffic?

[Joel Hammer]

No expert here but:
My samba system doesn't listen on port 135, as far as I can tell using
netstat -an
What do you see with netstat -an | grep 135 ?
Second, could you configure your system to listen on port 135 for UDP
packets, say with ipchains, and REJECT them, not DENY them.
The REJECT command notifies the sender that the packet has been rejected.
That might make the sender switch over to TCP without the 2 minute wait.
Your log seems to suggest that you are sending notification, but maybe
REJECT might be more definitive.
You might even try REJECTing all packets to port 135 and see if your client
will function ok.
BTW, my /etc/services doesn't list any assignment for port 135, so this
might be a Microsoft enhancement.
Joel

On Fri, Dec 21, 2001 at 10:56:05AM -0500, Pierre Belanger wrote:
> Hello,
> 
> This is a hard one, I've been trying to figure out something since
> 2 days...
> 
> When opening a document which has a link to another document, I see
> traffic
> from the Windows NT client station going to the Samba server on port
> 135/UDP. According to Microsoft's web site, port 135 TCP or UDP is
> "Location Server"... but the Samba server doesn't listen for traffic
> on port 135/UDP. So, the client keeps trying to connect to port 135/UDP
> on the Samba server for about 2 minutes and then switches to 135/TCP,
> which works better...
> 
> Can someone help me figure out how to fix this "timeout" issue?
> 
> Here's a snoop of the connection if this can help you understand
> the situation.
> 
> 10.64.33.238 -> alkonost     UDP D=135 S=1066 LEN=88
>     alkonost -> 10.64.33.238 ICMP Destination unreachable (UDP port 135
> unreachable)
> 10.64.33.238 -> alkonost     UDP D=135 S=1066 LEN=88
>     alkonost -> 10.64.33.238 ICMP Destination unreachable (UDP port 135
> unreachable)
> 
> About 2 minutes later, the client switches to 135/TCP.
> 
> 10.64.33.238 -> alkonost     TCP D=135 S=1074 Syn Seq=3472092006 Len=0
> Win=8192 Options=<mss 1460>
>     alkonost -> 10.64.33.238 TCP D=1074 S=135 Rst Ack=3472092007 Win=0
> 10.64.33.238 -> alkonost     TCP D=135 S=1074 Syn Seq=3472092006 Len=0
> Win=8192 Options=<mss 1460>
>     alkonost -> 10.64.33.238 TCP D=1074 S=135 Rst Ack=3472092007 Win=0
> 10.64.33.238 -> alkonost     TCP D=135 S=1074 Syn Seq=3472092006 Len=0
> Win=8192 Options=<mss 1460>
>     alkonost -> 10.64.33.238 TCP D=1074 S=135 Rst Ack=3472092007 Win=0
> 10.64.33.238 -> alkonost     TCP D=135 S=1074 Syn Seq=3472092006 Len=0
> Win=8192 Options=<mss 1460>
>     alkonost -> 10.64.33.238 TCP D=1074 S=135 Rst Ack=3472092007 Win=0
> 10.64.33.238 -> alkonost     SMB C Code=0x2e Name=SMBreadX Error=0 
>     alkonost -> 10.64.33.238 SMB R Code=0x2e Name=SMBreadX Error=0 
>     alkonost -> 10.64.33.238 NBT Type=Unknown Length=1456
>     alkonost -> 10.64.33.238 NBT Type=SESSION MESSAGE Length=1235
> 10.64.33.238 -> alkonost     NBT C port=1035 
> 10.64.33.238 -> alkonost     SMB C Code=0x2e Name=SMBreadX Error=0 
> 
> 
> Thank you very much,
> Pierre B.
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba