hi, I am facing a serious issue on connecting PCs to my Domain Controller running on win server 2008 St Ed. Here below is the message i got everythime from my pc ----------------------------------------- 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 following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "epistat-bdi.bi": 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.epistat-bdi.bi Common causes of this error include the following: - The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses: 196.2.8.205 192.168.1.3 - One or more of the following zones do not include delegation to its child zone: epistat-bdi.bi bi . (the root zone) -------------------------------------------------------- I ve checked many time my ip configs and seen this: Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet Physical Address. . . . . . . . . : 00-23-5A-81-C0-3A DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::dcdb:7ef8:d8:14cd%11(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.1.10(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.2 DHCPv6 IAID . . . . . . . . . . . : 234890074 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-64-5D-A6-00-23-5A-81-C0-3A DNS Servers . . . . . . . . . . . : 192.168.1.3 196.2.8.205 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter isatap.{A1F651B0-6645-4A91-9546-DDAC6A80E4C0}: ........................................................................... The ip adress has been added manually . I am looking forward to get a help Regards,

do you have any firewall or AV running on the client if yes please disable and recheck the behavior and al please disable the ipv6 from the clienthttp://www.virmansec.com/blogs/skhairuddin

Hello, you have a DNS resolution problem. Please make sure that: Each DC / DNS server is pointing to its private IP address as primary DNS server and other internal DNS servers as secondary ones Each DC without DNS is pointing to internal servers as DNS servers Each public DNS server is set as a forwarder and not mentioned in IP addressing Once done, run ipconfig /registerdns and restart netlogon on each DC you have. Also, make sure that needed ports for authentication are opened: http://msmvps.com/blogs/rexiology/archive/2006/04/05/89389.aspx For client computers, make sure that they point to a DC / DNS server as primary DNS server. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified IT Professional: Enterprise Administrator Microsoft Certified IT Professional: Server Administrator

Hello, your problem with connecting to the domain belongs to the public ip address 196.2.8.205. This MUST be configured as FORWARDER on the DNS server properties in the DNS management console and should NEVER be used on domain machines NICs, doesn't matter which one. So remove the public ip address and run ipconfig /flushdns and ipconfig /registerdns and restart the clients. On a DC run the same commands BUT just restart the netlogon service. Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.