Sign in with
Sign up | Sign in
Your question
Solved

How to setup home domain?

Last response: in Toms Network
Share
February 5, 2014 8:29:19 AM

From home, I am running Windows Server 2008 R2 and want to connect my domain using Windows 7 Professional.

I have successfully installed Active Directory on my Window Server 2008 R2.

However i am receiving an error where domain name cannot be contacted. Is this DNS relating? Do i manually have to setup my static IP address?

Can someone send me a step by step instructions for the correct guide and installation please?

Thanks

More about : setup home domain

a b $ Windows 7
February 5, 2014 8:36:50 AM

Make sure you have also the DNS role installed on your WS 2008 R2, and that all pcs on your network are able to ping your DNS/AD server before trying to join them to your local domain.

Yes, it's ideal that your WS 2008 R2 server have a static IP, so your DHCP server can assign the proper DNS server to your clients.

There are several guides on the net, give a look to this one:

http://www.howtogeek.com/99323/installing-active-direct...
m
0
l
February 5, 2014 9:06:52 AM

RaDiKaL_ said:
Make sure you have also the DNS role installed on your WS 2008 R2, and that all pcs on your network are able to ping your DNS/AD server before trying to join them to your local domain.

Yes, it's ideal that your WS 2008 R2 server have a static IP, so your DHCP server can assign the proper DNS server to your clients.

There are several guides on the net, give a look to this one:

http://www.howtogeek.com/99323/installing-active-direct...


Excellent!

Can you explain when you mean by "all pcs on your network are able to ping your DNS/AD server before trying to join them to your local domain"?

Becuase i have DNS role installed on my Windows Server 2008 also shown in the installation guide link you have sent.

When signing, does the DNS has to match with my Windows 7 and Windows Server 2008?

Thanks
m
0
l
Related resources
a b $ Windows 7
February 5, 2014 12:55:25 PM

"Can you explain when you mean by "all pcs on your network are able to ping your DNS/AD server before trying to join them to your local domain"?"

Every pc/laptop you are planning to join to the domain needs to have connection with the DNS server, else they won't be able to resolve the domain controller name when you tell them to join it.

Check that in case you're getting an error when trying to join them to the domain.


"When signing, does the DNS has to match with my Windows 7 and Windows Server 2008?"

If you mean the domain has to match both in the client account in windows 7 and in the windows server 2008 yes it has to be the same:

Windows Server 2008 Domain: UmarDomain.local
Windows 7 client log data: UmarDomain.local\clientaccount
m
0
l
February 5, 2014 2:05:02 PM

RaDiKaL_ said:
"Can you explain when you mean by "all pcs on your network are able to ping your DNS/AD server before trying to join them to your local domain"?"

Every pc/laptop you are planning to join to the domain needs to have connection with the DNS server, else they won't be able to resolve the domain controller name when you tell them to join it.

Check that in case you're getting an error when trying to join them to the domain.


"When signing, does the DNS has to match with my Windows 7 and Windows Server 2008?"

If you mean the domain has to match both in the client account in windows 7 and in the windows server 2008 yes it has to be the same:

Windows Server 2008 Domain: UmarDomain.local
Windows 7 client log data: UmarDomain.local\clientaccount


Hi

Excellent, thanks for the reply. Really appreciate.

I am re-installing my Windows Server 2008 R2 and will be starting again with umar.local domain.

I believe i have to set my ip address to static ip address right?

Another question, when manually setting an ip address, it also ask for DNS. In my case its probably 127.0.0.1.

Does this mean my Windows 7 will also have the same DNS 127.0.0.1 to match with my Windows Server 2008 DNS?

Thanks
m
0
l

Best solution

a b $ Windows 7
February 5, 2014 3:30:43 PM

Yes, it's a better practice to always use static IPs on servers.

On your Windows Server 2008 the DNS server could be itself: 127.0.0.1, on your windows 7 client however it has to point to the IP address of your Windows Server (if you assigned your WS2008 with a static IP of 192.168.1.100 then your windows 7 DNS server would be 192.168.1.100).
Share
February 5, 2014 5:14:47 PM

RaDiKaL_ said:
Yes, it's a better practice to always use static IPs on servers.

On your Windows Server 2008 the DNS server could be itself: 127.0.0.1, on your windows 7 client however it has to point to the IP address of your Windows Server (if you assigned your WS2008 with a static IP of 192.168.1.100 then your windows 7 DNS server would be 192.168.1.100).


Excellent thanks.

Do you also think i should enable my network discovery as well?

On Windows Server and Windows 7.
m
0
l
a b $ Windows 7
February 5, 2014 5:40:52 PM

Yeah, it will allow many shared stuff (from folders to programs) to work with no hiccups.
m
0
l
February 6, 2014 4:24:52 AM

RaDiKaL_ said:
Yeah, it will allow many shared stuff (from folders to programs) to work with no hiccups.


Hi

Thanks everything worked all and managed to get the domain working on my Windows 7.

Problem all solved thanks alot!!! :D 
m
0
l
a b $ Windows 7
February 6, 2014 6:37:50 AM

You're welcome
m
0
l
!