An active directory Domain Controller for the domain could not becontacted in windows vista Business

[CheyeNnne]

Sponsored Links

Somebody please help me out as soon as possible. As my subject says, I’m facing problems connecting an Windows Server 2003 AD DC for the domain on my Vista business based laptop. Whenever I try to connect the same I receive and error message saying:

“An active directory Domain Controller for the domain could not be contacted. Ensure that the domain name is typed correctly. If the name is correct, click details for troubleshooting information”

I don’t have any idea what could be done to fix this problem. Please help.

[T.J.]

You will need to do some troubleshooting for the same. By the way are you able to ping the Windows Server by it's ip address? Also make sure that the DNS is pointing only to the domain DNS server.

[ahmedel_rayies]

I have the same problem when I try to join new computer to the domain I receive this message (An Active Directory Domain Controller for the domain could not
be contacted.

Ensure that the domain name is typed correctly.)

and all joined computer very slow when logging into the domain.

I can ping the domain controller and I can ping the domain name only like ping abc.com it replys without any problem.

I tried to add additional domain to avoid this problem but it doesn't work and the problem happened again.

I'm facing this problem 5 month ago. When I install the domain again This happenes after 1 or 2 days after the installation.

I have 20 workstations, 1 ISA 2006 Server, and 1 Domain Controller.

Please help me this is gonna make me mad.

I want to join Windows server 2008 to
domain which is configured in windows 2003 server I am getting this
message ( An active directory Domain Controller for the
domain .............. could not be contacted. Ensure that the
domain name is typed correctly. If the name is correct, click details
for troubleshooting information)
I tried to solve but I can't solve. please help me soon

[Hockson]

Hello CheyeNnne. Let us know if you are able ping the server using its ip address and computer name? Apart from this i would like to see the ipconfig /all result from the DC/DNS/GC server and the problem machine to identify the problem proeprly.

[ahmedel_rayies]

I Already did what you mentioned before. I Have Microsoft ISA 2006 Firewall.

Thanks and Best Regards,
Ahmed Adel
MCP, MCSA, MCSE, ITIL and CCNA.

[dreddog]

I am having a similar problem. DHCP is not configured on my Win 2003 server - the client's IP address is fixed.

ipconfig/all give the following output

Windows IP Configuration

Host Name . . . . . . . . . . . . : DTWS1
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8168C(P)/8111C(P) Family PCI-E
Gigabit Ethernet NIC (NDIS 6.0)
Physical Address. . . . . . . . . : 00-1F-C6-04-9D-C1
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::adde:3a5a:c12b:7aa3%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.7(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 251666060
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-0F-5D-8F-85-00-1F-C6-04-9D-C1

DNS Servers . . . . . . . . . . . : 208.67.222.222
208.67.220.220
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e74:102f:1a14:3f57:fef8(Pref
erred)
Link-local IPv6 Address . . . . . : fe80::102f:1a14:3f57:fef8%11(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.{8A4855E0-B760-4AE6-87AD-6F8DE11CFC73}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Thanks in advance.

dreddog

[eiger3970]

I have the exact same issue. I can ping from the client pc to the SBS 2008 server's static IP address, however not the domain name.

[Mike21222]

I found a fix that worked for me for this error. I noted the error was pointing towards my wireless router. My network is a simple basic home network with MSHOME as my domain. I went into the configuration for my hiome router and set the domain name from "myname home" to MSHOME and my errors went away. I was then able to change my domain on my Vista Business laptop. which is the only PC in my home on Vista for reasons not necessary to share. I hope this help someone somewhere.