Hi all, I am using a samba WINS server for my Microsoft network that is split across 5 physical networks. For a long time, everything has worked fine, however recently we have had wierd problems with domain controllers "disappearing". Even with a primary or backup DC on the physical wire, workstations and other NT servers suddenly start complaining "a domain controller for DOMAIN cannot be found". I am assuming the workstation or server is asking WINS to give it the address of a domain controller, and WINS is not responding, or is responding wrong. Anyone else had a problem like this? I am using samba v1.9.18p10. Regards, Graham -- ----------------------------------------- graham@vwv.com "There's a moon VWV Interactive over Bourbon Street tonight... -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 2071 bytes Desc: S/MIME Cryptographic Signature Url : http://lists.samba.org/archive/samba/attachments/19981102/77cdf1ca/smime.bin
"GL" == Graham Leggett <graham@vwv.com> writes: GL> For a long time, everything has worked fine, however recently we have GL> had wierd problems with domain controllers "disappearing". I can offer nothing but moral support, but I've seen a similar problem. We're using NT WINS servers in a multi-subnet environment, and I've had the primary WINS server refuse to talk to Samba (to tell it who the domain master browser is). Switching to the 2ndry WINS server "solved" the problem. I still don't understand why, and using a symbolic debugger on nmbd didn't help. You might want to glance at the code to see what it's expecting (in terms of server or client responses) and then go straight to packet sniffing. John.
Graham Leggett wrote: GL> For a long time, everything has worked fine, however recently we have GL> had weird problems with domain controllers "disappearing". One thing to look for is machines supporting netblooie or Novell networking protocols participating in elections. One of the team posted (Mr. Terpstra, if memory servers) a caution about this some time ago: as I understood it, the winner might be a machine that assumes ``everybody should be using the protocols **I'M** using'', and fail to provide service on TCP/IP. This, and other Bad Things occur if you use NetBlooie or the default workgroup name, WORKGROUP. In the latter case, you usually find ill-configured machine on your net, arguing with the correctly-configured ones (;-)) --dave -- David Collier-Brown, | Always do right. This will gratify some people 185 Ellerslie Ave., | and astonish the rest. -- Mark Twain Willowdale, Ontario | davecb@hobbes.ss.org, canada.sun.com N2M 1Y3. 416-223-8968 | http://java.science.yorku.ca/~davecb