a 6ya expert can help you resolve that issue over the phone in a minute or two.
best thing about this new service is that you are never placed on hold and get to talk to real repairmen in the US.
the service is completely free and covers almost anything you can think of (from cars to computers, handyman, and even drones).
click here to download the app (for users in the US for now) and get all the help you need. goodluck!
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
first you need to setup the roles in the server, go to the manage server console, ( can be found as a shortcut in the taskbar or under start menu ) then open the console and go to add roles.
1 - add active directory
2 - in the process it will ask you to install the DNS server role ( do it )
3 - after installing the role in the CMD command prompt type DCPROMO
4 - the DC controller installation and setup will beging ( do not do anything during this proccess )
5 - when asked by DC setup to choose what type of domain functionality level do the following
1 - windows 2003 ( this is for compatibility for windows server running 2003 and XP machines )
2 - Windows Server 2008 ( at this point nothing lower than XP can be added to the DC of course domain functionalities will increase - Only other 2008 server domain controller can be added and cluster migration from server 2003 to 2008 is not supported. )
3 - Windows Server 2008 R2 ( at this point only machines running Vista and 7 can be added to domain - windows xp is no longer supported. All the functionalities of the domain controller are available)
keep in mind once you promote the domain controller to a higher level it can't be brouht to a lower level.
once active directory is installed restart you server and the you should be able to add the clients pc or laptos to the DC example
- right click over my computer icon - click on properties - computer name - change the computer from workgroup to domain - type your FQDN ( fully qualified domain name) example: mynetwork.local or mysite.com - apply changes and restart - your computer will be part of the domain next time system boots up.
<p><span>Some days before I have done a job on Windows Server 2003 Enterprise edition & Client XP. It is departmental food court. In the office room of the restaurant have a system which will be Server system and main domain. There was another 8 system in every department of food <span> </span>with printer for billing.I</SPAN><br>
<p><span>Windows Server 2003 includes a mission critical Windows Server operating system, such as security, reliability, availability, and scalability.</SPAN><br>
<p><span>You have to install DNS server for DC without DNS the client computers wouldn't know which one is DC.You can host DNS on a different server than DC.</SPAN><br>
<p><span>Before Starting the DC installation process you need to make sure the <span> </SPAN>following points</SPAN><br>
<p><span>1)You have installed Basic windows server 2003 installation</SPAN><br>
<p><span>2)Make sure you have assigned a static ip address to your server</SPAN><br>
<p><span><span> </SPAN>Now start DC and DNS Setup process</SPAN><span></SPAN><br>
<span>Active Directory is a huge topic in itself. While DCPROMO is easy to run, planning of both the physical and the logical structure is the key to a trouble free active directory. </SPAN>
<p><span>Domain controllers do not have to be your most powerful machines, however they must be reliable and always available to answer logon requests. </SPAN><br>
<a><span>DNS (Domain Name System)</SPAN></A><span><span> </SPAN></SPAN><span>Role</SPAN>
<p><span>Once DNS is setup, it runs itself thanks to the new dynamic component hence DDNS. TCP/IP knowledge plus understanding of how DNS works is essential when troubleshooting connectivity problems.</SPAN><br>
<p><span>DNS enables client machines to resolve servers IP addresses. Once the client finds the server, Active Directory uses LDAP to locate services like Kerberos, Global Catalog that clients request.</SPAN><br>
<a><span>Print Server Role</SPAN></A><span></SPAN>
<p><span>In my experience there is a contrast between the software settings which are easy to configure and the hardware which constantly need for attention e.g. paper jam, 'out of toner'. Check list for print server:</SPAN><br>
<p><b><span>Client Configuration :- </SPAN></B><span>After</SPAN><span><span> Installation of Windows Xp give the IP Add on TCP/IP of IPV4.If you want to manually configure DNS server addresses, click</SPAN></SPAN><span><span> </SPAN></SPAN><b><span>Use the following DNS server addresses</SPAN></b><span><b><span>,</SPAN></B></SPAN><span><span> and then type the preferred DNS server and alternate DNS server IP addresses in the</SPAN></SPAN><span><span> </SPAN></SPAN><b><span>Preferred DNS server</SPAN></b><span><span> </SPAN></SPAN><span><span>and</SPAN></SPAN><span><span> </SPAN></SPAN><b><span>Alternate DNS server</SPAN></b><span><span> </SPAN></SPAN><span><span>boxes. After all job try to ping each other. I'm trying this and it also pinging. Files and data also can be shared through it.</SPAN></SPAN>
This is an excerpt from a MS Technet page for error 53:
Resolutions:1) if it is domain environment, check your WINS; 2) if it is peer-to-peer workgroup, enable NetBIOS over TCP/IP; 3) make sure the machine is running; 4) make sure file and Printer Share enabled on remote computer; 5) make sure client for ms networks is enabled on local computer; 6) make sure you type the correct name. 7) Make sure no firewall running or any security setting.
Pay close attention to #s 4 and 5 - I suspect XP pro might not be open enough.
OU stands for Organizational Unit and is a part of Windows Server Active Directory. When you add an Organizational Unit to Active Directory, this allows you to create a category for computers, or for users, or both. For example, in a high school, I may create an OU for Students and have all my student accounts within this OU, and an OU for Staff, and have all my staff accounts in this OU. Now I can apply GPO's, or Group Policy Objects, to this Organizational Unit, such as Interface controls if I want to lock down student interfaces for example. You can also configure OU's with computers in them. So for example, I may join a set of teacher computers to the Staff Computers OU within Active Directory after these machines have been joined to the domain, and then apply a Policy on that OU that says that ONLY staff accounts may log into these computers to prevent students from logging onto a staff machine.
OU's are extremely handy because you cannot apply policy objects to just a single user or computer. OU's also help keep your Active Directory structure nice and clean.
When you install a server operating system at that time it will ask you that how many maximum clients you want to attach this server so by default its 10 ,that means you can attach maximum of 10 clients , you can increase or decrease the no of computer you want.
Firstly you have to decide whether to add clients in workgroup mode or Domin mode..in domain mode you have the centralised management on the computer .so select domain level mode . now to make clients either you can make 5 user in active directory user and computer. 1:Go to Administrative tools > Select Active Directory Users and computers > Select user on the left side > right click on that and select new user > now follow on screen instruction to make a user > now make other 4 user also in the same mannner.Now when you are logged on with local user on the clients select my computer > right click and Select properties > select my computer tab >now click change button to make client work with domain type only domain name for eg if your domain is contoso.com ,> type their only contoso > now a box will appear asking you for administrator and password enter domain controller pc password ,it will ask you to restart > after restart user can login at the client computer... Or: just login with local user at client computer Right click my computer > and do the same procedure ,after restarting you can login with your server name administrator and password . --------------------------------------------------------------------------------------------- If this answers your question please rate this as fixed. If you need more help just add a comment and I'll be glad to help you further ---------------------------------------THANKS ----------------------------------------