General discussion

Locked

unable to join domain from the client

By mjp5108-50318218 ·
I have a home network with a Win 2000 server as the only server/domain controller. The problem I'm having is that when I try and connect either a Win 2000 pro or XP pro client, I am unable to connect to and join the domain.
It seems that the error message is saying that the SRV records(_ldap._tcp.dc._msdcs) on the server are not available. There are no SRV records that have been created under the forward lookup zone on the server.
In the server's event viewer, it is saying that a single label name exists, but according to various searches on the net and Microsoft's site, when I go to the netword id tab on the server what is listed is correct.
The full computer name is "server name.domain name.com" and the domain is listed correctly as well. So, even though, it is saying a single label name exists, it doesn't. I have even demoted and promoted the domain controller and even did a complete format and started over on the server.
It also mentions that a global catalog server couldn't be contacted, yet this server under AD sites and services; under ntds settings, it is listed as a global catalog server.
The server has two nics and I have pointed both nic's ip addresses to the internal dns server address. I have configured forwarders to the isp dns servers.
Under the forward lookup zone, I have configured under the domain name, the soa, ns and a records to all point to the internal dns server.
When I ipconfig /all from the command line there is a primary suffix pointing to the correct domain name (this also was mentioned as a possible problem).
From the client side I can ping the server name and it even lists the domain name. But when I do an nslookup server name it gives the correct ip address but it says this is a non existent domain.
I can see the shares on the all machines but I'm just not able to join the domain.
The source of the problem seems to be that the SRV records are not being created.
I'd appreciate any help.
Th

This conversation is currently closed to new comments.

7 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by mjp5108-50318218 In reply to unable to join domain fro ...

I've have also ipconfig /flushdns and registerdns on both server and clients, as well, but still no go.
I am also using dynamic updates on the zone file under the forward lookup zone as well.

Collapse -

In your question you said that the server has 2 nics pointed to the ip addresses of the internal dns server. The domain controller should be the internal DNS server and the nics should point to itsself. You should not config pointers to the ISP's dns servers then internal users could be using them and not resolve to local DC.

Run DNS on the DC only. Point all computers to it. Make sure DHCP is on or you have static IP's on the same network. If your dhcp is not working and a scope configured you need all computers to have static IP's in the same network 192.168.0.xx. Point the DC to itself as its DNS server and configure your router as the default gateway.

Collapse -

by mjp5108-50318218 In reply to

Poster rated this answer.

Collapse -

by mjp5108-50318218 In reply to unable to join domain fro ...

California,
What you have suggested I have already done. Both server's nic ip addresses are configured so that they are pointing to the Internal dns server address.
Both have static ips on them. In the dns console I have configured the forwarders tab to point to my isp's dns servers ip addresses.
On the client side I have configured the nic to point to the Internal dns server. I have tried to configure the client side with a static address as well as let dhcp determine the client's address (not the dns address).
I'm still stumped as to why the srv records are not being automatically created on the server's dns console. That seems to be the problem in preventing the client from seeing the Internal dns server.
Thanks for your response

Collapse -

by d'solve IT In reply to unable to join domain fro ...

Hi,

You mention >>The full computer name is "server name.domain name.com"

I would recommend that you change the domain name to domain_name.Local. Demote the DC and then recreate the domain as mentioned again.

Prior to demoting your server, I would also recommend you uninstall the DNS, DHCP and any other service that is bound with the current domain name. After you redo the AD and install DNS, you should be able to connect the Win2K or XP Pro to this domain without issues.

Good Luck.

Collapse -

by mjp5108-50318218 In reply to

Poster rated this answer.

Collapse -

by mjp5108-50318218 In reply to unable to join domain fro ...

This question was closed by the author

Back to Windows Forum
7 total posts (Page 1 of 1)  

Related Discussions

Related Forums