[Samba] Cannot sync browser lists

[daniel.jarboe at custserv.com]

Well, thanks for all your help.

> interface ctc0 ?

Channel to channel, a point-to-point connection without broadcast, one
of the interface types that are available with the s/390 architecture.
That could be why the tcpdump looked screwy.  The server is dual-homed,
I'll go ahead and add the eth interface to samba, route to the pdc
through that, and see if I have better luck.  It'll at least help in
diagnosing with tcpdump, probably.

> what does    smbclient -L winshostname  -U validuseronserver  
I saw the shares on that WINS/PDC and below that, the computers that
show up in network neighborhood (and mine wasn't in there :().

Things just got more interesting... I changed the route table so traffic
to the pdc goes through the eth0 interface, and added eth0 to my
interfaces line in smb.conf.  Right after firing up nmbd I got:
[2003/03/10 07:10:46, 0]
nmbd/nmbd_responserecordsdb.c:find_response_record(235)
  find_response_record: response packet id 693 received with no matching
record.
[2003/03/10 07:10:46, 0]
nmbd/nmbd_responserecordsdb.c:find_response_record(235)
  find_response_record: response packet id 694 received with no matching
record.
but since first start, it hasn't shown up in log.nmdb, and now the wins
server sees me, the samba server shows up in network neighborhood.

I've read that the find_response_record sometimes occurs with subnets
with some versions of win95 on them?  I don't know what's on that
subnet.

> Ahh wait a minute...if some things work and not others...I 
> believe wins
> calls are udp protocol based NOT tcp...even though the port 
> nos are the
> same. which brings us back to the firewall again!!!!

Well, using either interface, nmap -sU -p 137 [wins/pdc] says:
Note: Host seems down. If it is really up, but blocking our ping probes,
try -P0

And using -P0 works over both interfaces, shows 137 udp open.

Same deal with tcp 139.  Have to -P0 and then it shows it open.

Unfortunately users are on now... tomorrow morning I'll try switching
back to ctc0 and see if things stop working.  Things stopped working the
first time over a weekend, and the windows guys said that the pdc/wins
server had crashed and burned and needed to be rebooted, and since then
I wouldn't show up anymore.  Wishful thinking, I know, but maybe
connecting over the other interface will get me back "in" over the
interface which used to work and which I should be connecting over, ctc.
I guess I'll find out tomorrow.

I took a tcpdump over eth0, a lot more chatty (probably because things
are working, and it may just be a chattier interface).  Any things I
should be looking for in it?

> regards
> Richard Coates.

Thanks for your patience,
~ Daniel




-----------------------------------------------------------------------

This message is the property of Time Inc. or its affiliates. It may be
legally privileged and/or confidential and is intended only for the use
of the addressee(s). No addressee should forward, print, copy, or
otherwise reproduce this message in any manner that would allow it to be
viewed by any individual not originally listed as a recipient. If the
reader of this message is not the intended recipient, you are hereby
notified that any unauthorized disclosure, dissemination, distribution,
copying or the taking of any action in reliance on the information
herein is strictly prohibited. If you have received this communication
in error, please immediately notify the sender and delete this message.
Thank you.