Also no PDC found

[Michel]

> 
> You do need it. I think Luke took out the line saying you didn't
> need to do it.
> 
> HOSTNAME$:uid:LMHASH:NTHASH:80
> with the password set to "hostname" in lower case.

[snip]

Well I did that, and modified it too :0080: as well... Still no luck
(unable to locate the domain controller for this domain).
Then, rather than using the system's tcpdump, I used tcpdump-smb.
Then something frightning happened:

The NT Wks queries for the PDC of the domain (or at least I think so),
and then samba replies with:

15:04:27.265907 elzas.nijenrode.nl.netbios-ns > quebec.nijenrode.nl.netbios-ns:
>>> NBT UDP PACKET(137): QUERY; NEGATIVE; RESPONSE; UNICAST
TrnID=0x83A8
OpCode=0
NmFlags=0x58
Rcode=3
QueryCount=0
AnswerCount=1
AuthorityCount=0
AddressRecCount=0

ResourceRecords:
Name=BLUBBER         NameType=0x00 (Workstation)
ResType=0x0
ResClass=0x1100
TTL=12592
ResourceLength=13872

               ^^^^^ Eeeeeks!

I shall not include the resource data but it involves all kind of stuff
that has nothing to do with either elzas (the samba server) or quebec (the NT 
wks), including what looks like an ENTIRE arp table. And I can't believe
13k is a usual size for a query response ?

Then tcpdump-sbm cores (and I even got the binary dist).

Does this help anyone in guessing what could be the problem ?

Michel.