Windows joining a Samba domain

I am having a problem whereby I cannot make Win2k and WinXP machines join or leave a Samba 2.2 domain and they give the error message

"The following error occurred attempting to join the domain "MSEAG":

The specified domain either does not exist or could not be contacted.

This is despite the fact that
1. The machines that cannot join the domain can ping the domain controller
2. Machines that joined the domain before this problem occured can still long on the domain
3. Machines that cannot join the domain can still log on to shares on the domain via Windows Explorer

This is not caused by a bad username/password combo, I have tried every possible combo and plus I have seen that message before and it is different
The only event that I can think of that could have precipitated this problem is the fact that we have recent taken the firewall services off the server and installed a seperate IPCOP machine instead to do firewalling. So the domain controller is no longer doing DHCP/DNS.

A kind of sub-question is would installing Samba 3 solve this problem and is it a lot of hassle?


Who is Participating?
sr_millarConnect With a Mentor Commented:

Sounds like the new workstations cant locate a domain controller to logon.  I am not familiar with Samba, but you need DNS running on your network that contains an SRV record pointing to a DC.  If that is not there you will have problems.  

Are you also sure you have updated the DHCP scope to point to the new DNS server aswell and that the PCs are not trying to contact the wrong DNS server?

check this

also it is a good idea to upgrade Smba as 2.2 does not work very will as Domain controller . I dont thing it is a big hassel to upgrader to 3 .
You say that the clients can ping the DC. Using its IP address or its hostname?

Can they ping MSEAG?

Protect Your Employees from Wi-Fi Threats

As Wi-Fi growth and popularity continues to climb, not everyone understands the risks that come with connecting to public Wi-Fi or even offering Wi-Fi to employees, visitors and guests. Download the resource kit to make sure your safe wherever business takes you!

adamdepledgeAuthor Commented:

You seem to be the only one onto something so far. I don't understand what the SRV record is. The server had some DHCP problems and once those problems were sorted I managed to get one machine to join the domain. However another machine is still not joining and gives a different error message than before. The important part of the error message is included below.

The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for _ldap._tcp.dc._msdcs.MSEAG

Common causes of this error include the following:

- The DNS SRV record is not registered in DNS.

- One or more of the following zones do not include delegation to its child zone:

. (the root zone)
Have a look at this section of a Microsoft TID :

DNS Server Requirements
Microsoft recommends that you use Microsoft DNS Server as supplied with Windows 2000 Server as your DNS server. However, Microsoft DNS is not required. The DNS server that you use:
Must support the SRV RR (RFC 2052).
Supports the dynamic update protocol (RFC 2136).
Version 8.1.2 and later of BIND (a popular DNS server implementation) supports both the SRV RR and dynamic update. (Version 8.1.1 does support dynamic updates but it has flaws that were fixed in 8.1.2.) If you are using a version of BIND that does not support dynamic update, you need to manually add records to the DNS server.

NOTE: Microsoft DNS, as included with Microsoft Windows NT 4.0 Server, does not support the SRV record. Use DNS Server that is provided with Windows 2000 Server.

I am not familiar with Samba, but is the DNS Bind 8.1.2 or later?  Active directory uses what is called a SRV record to locate domain controllers - without it you might be in trouble.

What is the possibility of running DNS on a W2K box?

I will look further into this for you.


go to c:\winnt\system32\drivers\etc ( C:\WINDOWS\SYSTEM32\DRIVERS\ETC for XP)

you have a file called lmhosts.sam in there

edit it and add the following entry in it


now save this file as lmhost ( make sure u dont save it as txt or sam file )

reboot the machine & try to join again .

adamdepledgeAuthor Commented:
Thanks guys

we are going to solve the problem by going to Samba 3 so the points go to Stuart who gave me the most helpful info
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.