Topic: problems connecting to domain

[n00b]

I am currently running SME server 6.0.1. I want to be able to log in to the domain on my win xp client. I have configured the server. I have also set the DNS server address on the client to 10.0.0.1 which is the IP of the server. When I go to the system properties on the client and try to change from the workgroup to the domain and press ok I just get an error message. This tells me that the domain controller for that domain cannot be contacted. In the details it also says the following:

"Note: This information is intended for a network administrator.  If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\WINDOWS\debug\dcdiag.txt.

The domain name petdam might be a NetBIOS domain name.  If this is the case, verify that the domain name is properly registered with WINS.

If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration.

The following error occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain petdam:

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.petdam

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:

petdam
. (the root zone)

For information about correcting this problem, click Help."

I have spent a long time trying to get this to work and I hope someone can help.

[crazybob]

Have you applied the xp logon registry patch to the xp client?

[n00b]

Yes I have applied the registry patch. I am also running the server as a gateway to the internet across my network. This is working fine. I just can't seem to connect to the domain.

[p-jones]

Dont ask me to explain why because I have not had time to investigate but I had this same issue just 3 or 4 days ago  it went like this... (maybe someone knows why off the top of their head)

I was entering the FQDN into the windoze client. In the end, I just used the netbios name and it was fine. To explain, the server was "server.mydomain.dydns.com".  I was entering "mydomain.dydns.com" and experiencing your problem. I resolved it by just entering "mydomain"

Just be sure you have no active connections to any shares/printers when joining the wkstn to the domain.

HTH
Peter

[mrwa]

it looks like a DNS problem
so check if you use de right DNS adres on the client.
point to Sme as dns server
mrwa

[mrwa]

sorry,
i didnt read the message well
you did pont to the right DNS
mrwa