- Posts: 23
- Thank you received: 0
Join a pc to domain
- allanigue03
- Topic Author
- Offline
- Junior Member
Less
More
16 years 7 months ago #25665
by allanigue03
Join a pc to domain was created by allanigue03
Hello All,
I have a question about a PC needs to join to domain.
If I have a PC want to join to domain what are the initial requirements?
Can somebody give me how the process works?
Do I need a DNS or NetBios entry to the PC? If the PC and the domain controller has a firewall in between, what settings should I need to allow on the firewall?
Thanks,
Aries
I have a question about a PC needs to join to domain.
If I have a PC want to join to domain what are the initial requirements?
Can somebody give me how the process works?
Do I need a DNS or NetBios entry to the PC? If the PC and the domain controller has a firewall in between, what settings should I need to allow on the firewall?
Thanks,
Aries
16 years 7 months ago #25670
by Chojin
CCNA / CCNP / CCNA - Security / CCIP / Prince2 / Checkpoint CCSA
Replied by Chojin on topic Re: Join a pc to domain
You need a DC to host the domain.
The OS to support the domain (windows home can't join a domain e.g.)
You need intercommunication ofcourse.
a DNS server or HOST entries local for the domain. (not sure of the last works due to LDAP entries)
DHCP would be recommended or point your computer towards the right DNS server // Gateway Server
You need a valid user account on the domain.
The OS to support the domain (windows home can't join a domain e.g.)
You need intercommunication ofcourse.
a DNS server or HOST entries local for the domain. (not sure of the last works due to LDAP entries)
DHCP would be recommended or point your computer towards the right DNS server // Gateway Server
You need a valid user account on the domain.
CCNA / CCNP / CCNA - Security / CCIP / Prince2 / Checkpoint CCSA
16 years 7 months ago #25679
by KiLLaBeE
Replied by KiLLaBeE on topic Re: Join a pc to domain
Are you looking to try to create your own domain network?
First thing you need is a domain controller. Windows Server 2000 or 2003 can be domain controllers. After you promote your servers to domain controllers and DNS is configured properly on the server, simply go to System Properties on the client computer (Windows XP Pro, can't be Home), click the Computer Name tab, click the Change button, click the Domain radio button, type in the domain name and click OK. You'll then be presented with an authentication box where you have to enter the credentials of a user that has the rights to add computers to the domain. For a test environment, the administrator on the server (or the domain admin) will be able to do this. After clicking OK and waiting about 30 seconds, you'll be presented with a box that will welcome you to the domain, click OK, restart, and when you're ready to login to the domain for the first time, ensure that you choose to login to the domain and enter the credentials of a user account that you created in Active Directory.
Generally, PCs in a domain environment don't have firewalls.
In the process of promoting Windows server to a domain controller, you'll be asked if you want to configure DNS.
For a small lab environment, you don't need a DHCP server (unless you want to play and learn with it).
In the background, a computer account is created in Active Directory when a computer is added to the domain. The computer account and the physical computer share a secure, "password protected" connection to ensure that another computer on the network doesn't "hijack" the computer account (possibly for malicious purposes).
First thing you need is a domain controller. Windows Server 2000 or 2003 can be domain controllers. After you promote your servers to domain controllers and DNS is configured properly on the server, simply go to System Properties on the client computer (Windows XP Pro, can't be Home), click the Computer Name tab, click the Change button, click the Domain radio button, type in the domain name and click OK. You'll then be presented with an authentication box where you have to enter the credentials of a user that has the rights to add computers to the domain. For a test environment, the administrator on the server (or the domain admin) will be able to do this. After clicking OK and waiting about 30 seconds, you'll be presented with a box that will welcome you to the domain, click OK, restart, and when you're ready to login to the domain for the first time, ensure that you choose to login to the domain and enter the credentials of a user account that you created in Active Directory.
Generally, PCs in a domain environment don't have firewalls.
In the process of promoting Windows server to a domain controller, you'll be asked if you want to configure DNS.
For a small lab environment, you don't need a DHCP server (unless you want to play and learn with it).
In the background, a computer account is created in Active Directory when a computer is added to the domain. The computer account and the physical computer share a secure, "password protected" connection to ensure that another computer on the network doesn't "hijack" the computer account (possibly for malicious purposes).
Time to create page: 0.118 seconds