Active Directory not working

Microsoft Windows home server oem
January 24, 2011 at 16:55:18
Specs: Windows Server 2003, 2.80 GHz 1GB
I tried setting up active directory on windows home server 2k3 enterprise, but I couldnt get it to work. I downloaded the dcdiag tool microsoft suggested and it game me this message:
Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\TDLOCAL1
Starting test: Connectivity
TDLOCAL1's server GUID DNS name could not be resolved to
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(0c6082b8-729d-4a75-9744-69a88895fcd4._msdcs.tdl.local) c
resolved, the server name (tdlocal1.tdl.local) resolved t
address (192.168.1.11) and was pingable. Check that the
registered correctly with the DNS server.
......................... TDLOCAL1 failed test Connectivi

Doing primary tests

Testing server: Default-First-Site-Name\TDLOCAL1
Skipping all tests, because server TDLOCAL1 is
not responding to directory service requests

Running enterprise tests on : tdl.local
Starting test: Intersite
......................... tdl.local passed test Intersite
Starting test: FsmoCheck
......................... tdl.local passed test FsmoCheck

tdlocal1 is the servers name
tdl.local is the domain i used for active directory

does anyone know how i can get this to work (im trying to use xp pro to connect to the active dir server)


See More: Active Directory not working

Report •

#1
January 24, 2011 at 18:53:44
Post the results of an ipconfig /all from the server for review

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#2
January 24, 2011 at 18:55:25
Windows IP Configuration

Host Name . . . . . . . . . . . . : tdlocal1
Primary Dns Suffix . . . . . . . : tdl.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : tdl.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ether
NIC
Physical Address. . . . . . . . . : 00-14-D1-1C-72-A4
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.11
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
Lease Obtained. . . . . . . . . . : Monday, January 24, 2011 9:50:13 PM
Lease Expires . . . . . . . . . . : Tuesday, January 25, 2011 5:13:38 PM


Report •

#3
January 25, 2011 at 07:30:18
You need to set up your server with a fixed IP Address and use it as the DNS and DHCP server. The DNS server in your router doesn't understand Active Directory; the DNS needs a lot of entries that only the Microsoft DNS server will do automatically.

Report •

Related Solutions

#4
January 25, 2011 at 07:38:01
I would start from scratch and do a clean install of the operating system. While installing, or immediately after, statically assign an IP address to the server as ijack said.

If your router is setup something like this:

ex:

Router's LAN IP: 192.168.1.1
Subnet Mask: 255.255.255.0
DHCP = Enabled
DHCP Scope = 192.168.1.100 to 192.168.1.199

Then I would use something like the following TCP/IP settings for the server:
IP: 192.168.1.10
SM: 255.255.255.0
Default Gateway: 192.168.1.1

Then, once it's setup and communicating, I would do any/all necessary OS updates. Once you're finished that, then run dcpromo to make the server a DC and allow it (Windows) to setup DNS during the promotion.

When you're finished, ensure you have DNS forwarding setup on the DC's DNS server. You'll want to forward to either 192.168.1.1 (the router) or to your ISP's DNS server(s). Personally, I would use the ISP's DNS for the forward.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#5
January 25, 2011 at 07:56:47
In a nutshell since you didn't configure the dns server to point to itself but pointed instead to the router, your dns server couldn't resolve its own self.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#6
January 25, 2011 at 12:57:58
I can communicate with the server just fine (I'm using it as a web server too). I dont know anything about setting up DHCP or DNS servers on it, so I'll just give up.

Report •

#7
January 25, 2011 at 14:02:21
Hey, if you give up on a little thing like that then you'd never get on with Active Directory!

Installing DNS and DHCP servers on Windows server is an absolute breeze. But if you just want to use it as a simple web server and/or file server then you have no need for AD.


Report •

#8
January 25, 2011 at 15:05:29
Installing DNS and DHCP servers on Windows server is an absolute breeze.

Especially if you let Windows configure the DNS during the promotion process.

If you have a SOHO Router, don't bother setting up DHCP on the server, leave the router doing it, just ensure the DHCP service on the server is disabled.

But if you just want to use it as a simple web server and/or file server then you have no need for AD

I agree........most emphatically!!!!

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#9
January 25, 2011 at 15:05:29
Installing DNS and DHCP servers on Windows server is an absolute breeze.

Especially if you let Windows configure the DNS during the promotion process.

If you have a SOHO Router, don't bother setting up DHCP on the server, leave the router doing it, just ensure the DHCP service on the server is disabled.

But if you just want to use it as a simple web server and/or file server then you have no need for AD

I agree........most emphatically!!!!

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#10
January 26, 2011 at 02:10:52
The only reason that I suggest using the Microsoft DHCP is that I am not convinced that all router DHCP servers will send the correct dynamic DNS updates to the DNS server. It's not essential to have DNS entries for your clients, but it can be useful, especially if any of them are running web servers or something similar.

Report •

Ask Question