Windows Server 2008 - Home Domain Server

March 7, 2011 at 10:13:28
Specs: Windows Server 2008
Hello everyone,
I am very new to Windows Server 2008 as I am starting to learn it now. My question might be very silly and i do apologize in advance if so. Here is my situation:
I have 3 x PCs and 1 x Laptop at home. What I am trying to accomplish IF POSSIBLE is use one of my PCs (i5 750, 8Gb RAM, 4TB Hard Drive + 2Tb External Drive) as the server (with Windows Server 2008) using a Domain, so that the other machines can connect to it. The user can have their on account on the domain, login in to different machines with the same account and accessing their files. (All of the machines connect to my router at the moment).

Now what I want to know is, is it possible to set this up locally or does it have to be on an external domain over the internet. I am confused at the part when setting up AC DC and it asks for a domain name, the example given is e.g. Would I need an actual domain such as the example or can the domain be setup and hosted locally/home in my "server" PC (specified above).

If I need an actual domain such as then I have been hanging my head against the wall for no reason, If it is possible to have the domain at home then could someone please show me the steps to set up this scenario.

I do apologize in advance if my novice ignorance has talked for stupid/impossible scenario.
Thank you for your help

See More: Windows Server 2008 - Home Domain Server

Report •

March 7, 2011 at 10:26:33
The domain name can refer to a local name such as "name.local." Don't use a real top level name such as "com" as this will cause confusion and complicate configuration. There is no need for the domain name to be registered, although that is often desirable in a business setting.

Setting up and configuring an active directory domain is not a simple thing. You can find this information with an internet search.

Report •

March 7, 2011 at 10:54:28
Thank you for your reply. I did indeed try to setup AD DC with "name.local" but still no luck. :-(

This is what I get under Server Manager:
The local domain controller could not connect with the following domain controller hosting the following directory partition to resolve distinguished names.

Domain controller:

Directory partition:

Additional Data
Error value:
1355 The specified domain either does not exist or could not be contacted.
Internal ID:

Event ID: 1844

And this is what I get when i try to connect of of the client machines to the domain:

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 "veljan.local":

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.veljan.local

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:

- One or more of the following zones do not include delegation to its child zone:

. (the root zone)

Thank you.

Report •

March 8, 2011 at 06:35:15
Help Please

Report •

Related Solutions

April 15, 2011 at 04:17:56
try and demote your AD DS and remove all the role frm your server.redo all the promotion again and b4 you start try and connect all your devices to a switch and assign a static IP to your be cont..........

Report •

April 15, 2011 at 09:42:37
Noahvelo buy one of the mcse training books on 2008 and follow it.

You can't learn this stuff the way you are going about it. You have to start with basics before moving on to advanced.

You should not have a root zone.
You should have the workstation pointing to the servers ip for dns.

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

Report •

Ask Question