AD Infrastructure Failed

[Gazzieh]

We have just finished creating a Server 2003 network system in a small location (21 workstations) and, aside from minor, normal issues everything seemed to go fine.

The WS OS was sent out via RIS and though the network card failed to install through RIS we have since installed it manually. RIS had registered the units with AD but since the units failed to install the network cards they were not actually on the network. Therefore, we have since deleted the AD accounts and re-attached the workstations manually.

The account for the WS appears in AD as expected. The log on is slow but there. And yet no GPOs are having effect and the fault is down to AD Infrastructure failure (fault log on workstation).

Any ideas?

 

[Gazzieh]

Okay, maybe a pointer!

When I do an ipconfig /all the DNS server section only lists the external DNS servers and NOT the Domain Controller's IP address at the start. I am presuming that the primary (first DNS) address should be our Domain Controller and therefore the reason for the fail is simply it cannot resolve the IP address requests.

If I am correct; where is the solution? )

 

[Gazzieh]

Solved!

Stupid really. When I was checking all the settings it was clear that DHCP was handing out false info. Checking the Server Options showed nothing but the Scope Options did. Adjusted these correctly and the system is fully up and running!