Resolved: W2k -> Solaris: Cannot connect to port 139

Michael Kolmodin MIchael.Kolmodin at
Wed Aug 29 11:46:54 GMT 2001

Thanks for the hints. The problem seems to be that NT in some
situations routes packets to hosts on the same network via
the default router. In my case, this is the ISP's router which
blocks port 139 (and only that one, BTW). The routing is not stable,
sometimes the packets goes direct. This explains the random
behaviour and that no other service is affected.

I know it sounds silly, but below you will find the logs describing
how my stupid NT client (address routes packets
to the host mumin/ via the default router. Note that
according to the output from the "route" command this should not
happen. But it does, at least according to "traceroute".

Any idea where this kind of topics are best discussed out there?
I think I understand the problem, but have no solution on hand
right now. But I see some light in the tunnel... And I'm happy
to inform all of you that my suspicions regarding samba where
totally wrong :-)


C:\>route print
Interface List
0x1 ........................... MS TCP Loopback interface
0x1000003 ...00 b0 d0 88 df 19 ...... EL90BC0 3Com EtherLink PCI
0x1000004 ...00 02 2d 01 35 7a ...... wlluc487 ORINOCO PC Card
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
      1       1      1       1      1      1         1000003       1
Default Gateway:
Persistent Routes:

C:\>tracert mumin

Tracing route to []
over a maximum of 30 hops:

  1   <10 ms    10 ms   <10 ms [213
  2   <10 ms    10 ms   <10 ms  
se []

Trace complete.

More information about the samba-technical mailing list