[Samba] Domain controller could not be contacted
I recently upgrade a Samba server, that was happily acting as a PDC for a school, from 3.2 to 3.4.7. This was done via an upgrade to Ubuntu (from 9.04 to 10.04LTS). Of course, the Ubuntu upgrade caused a bunch of issues, most of which were managed without undue stress. The remaining issues are with Samba's configuration. This is a fairly simple Samba configuration using the TDB password backend, no LDAP. After the upgrade, domain logons do not work, nor can new machines be joined to the domain. From a Windows XP machine, attempting to log on gives "The system can not log you on now because the domain CK is not available." Attempting to join the domain yields: "A domain controller for the domain CK could not be contacted. Ensure that the domain name is typed correctly. [...]" In the details for this message, it states that "The following error occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain CK: The error was: 'DNS name does not exist.'" It also states that "The query was for the SRV record for _ldap._tcp.dc._msdcs.CK" This seems strange because we aren't using LDAP. Workgroup machines work. But they can't browse the domain. Going directly to a share on the server via the FQDN works. This looks like a winbindd issue to me. On the Linux side, connecting to a share on the server with smbclient works fine. In all honesty, I don't have much knowledge of tools for debugging NetBIOS issues with Samba. It's always just worked for me. Any ideas what could be going on here? Suggestions for further inquiry? Mark -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Re: WinXP vs Samba: domain controller could not be contacted
Finally I found out that I had to add the samba server's IP address to the wins entry in the network configuration and reboot afterwards. I also switched on "enable netbios over TCP/IP". The Norton Internet Security firewall can also cause this "domain could not be contacted" error, how I found out independently from the above problem. Later I stumbled in another problem: When I tried to join the domain I got the error message "user does not exist". I found out that the "add user script" doesn't add machines anymore and is now called "add machine script". Again this error left no trace in the logs. Why are there logs if they don't log anything? Setting up XP with Samba was a real nightmare. Why isn't there some useful documentation that shows which settings really need to be made in Windows XP? Why aren't there useful error messages? So long, Martin -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Re: WinXP vs Samba: domain controller could not be contacted
Martin Wartens schreef: I guess this a problem with netbios/wins, but I am out of ideas. What could it be? I have found the same question lots of times on google, but never any solutions. Help please! Martin How about your name resolution. Can you resolve the netbios name of the samba server? Try ping netbiosname. Can you resolve the FQDN. Try ping hostname.domain (like www.google.com). If you can't resolve, try adding the host to lmhost file (system32\drivers\etc\lmhost) and then nbtstat -R . If you can resolve, did you actually join the domain? Are you on the same subnet. Is your firewall blocking (maybe xp sp2 firewall active). Look in your nmbd.log file for entries that state that your machine is a doamin master browser and a local master browser (if you have 1 pdc, no bdc). -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] WinXP vs Samba: domain controller could not be contacted
Hi, when I try to connect with a Windows XP Professional workstation to my domain (My Computer->Computer Name ...), I keep getting the error message "A domain controller for the domain ... could not be contacted". This attempt leaves no traces in the samba logs. I have applied the recommended WinXP registry tweaks. I am pretty shure that I have typed the domain name right. nmdb is running on the samba server. Strange enough, I can connect to the samba server if I enter its IP directly in Start->Run. Reversely, I can also connect from the samba server to the XP machine with smbclient. I guess this a problem with netbios/wins, but I am out of ideas. What could it be? I have found the same question lots of times on google, but never any solutions. Help please! Martin -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
