FTP 21
FTP-DATA 20
SSH 22
TELNET 23
SMTP 25
WINS 42
DNS 53
BOOTD/DHCP 68
BOOTPS 67
TFTP 69
HTTP 80
KERBEROS 88
POP2 109
SFTP 115
NNTP 119
POP3 110
NTP 123
NETBIOS 139
IMAP 143
IMAP3 220
LDAP 389
SMB 445
SSL 443
LPR 515
RIP 520
IPP 631
POP3s 995
IMAPs 993
L2TP 1701
PPTP 1725
RADIUS SERVER 1812
RADIUS ACCOUNTING 1813
LOTUS NOTES 1352
NFS 2049
RDP 3389
HTTP 8080
PANKAJ SHARMA....
Active Directory in Windows Server 2003
Active Directory is Microsoft's trademarked directory service, an integral part of the Windows 2000 architecture. Like other directory services, such as Novell Directory Services (NDS), Active Directory is a centralized and standardized system that automates network management of user data, security, and distributed resources, and enables interoperation with other directories. It is primarily used for online information and was originally created in 1996. It was first used with Windows 2000. An active directory can be defined as a hierarchical structure and this structure is usually broken up into three main categories, the resources which might include hardware such as printers, services for end users such as web email servers and objects which are the main functions of the domain and network.
This page is designed to help those who are new to Microsoft's Active Directory. My goal is to get you started with the key terms and concepts
Seven aspects of Active Directory
1) Active Directory as the Successor to NT 4.0's SAM database
Every successful operating system needs an authentication mechanism. Novell developed the marvellous NDS tree, while UNIX has the powerful directory services to manage their users. By the year 2000, NT 4.0's SAM had become an embarrassment and Microsoft developed their directory service we know as Active Directory. As a matter of interest the physical file corresponding to NT 4.0's SAM is called NTDS.DIT (Directory Information Tree).
2) Active Directory as an object based system
The NT 4.0 SAM database was very thin, both in respect to the number of users it could hold and their range of properties. The only information SAM stored was usernames and their passwords. Active Directory on the other hand, can store many many more attributes of the user object. To examine and configure these attributes, launch the Active Directory Users and Computers and browse through a user's Properties tabs. There you will discover a whole range of attributes, for example, telephone number, manager, email address, certificates, dial-in properties.
3) Active Directory's search mechanism
Microsoft do not change menu names without good reason; if you go to the Start Menu in Windows Server 2003 you will see that Find (NT 4.0) has been replaced by Search. Once you launch Search, you will see the file system in the upper window, however, it is the lower section that I am interested in, because this where you can search for Computers, Printers or People. Using this part of Search, you are actually querying Active Directory to retrieve the objects you are interested in.
Technically you are using a protocol, or query language called LDAP (Lightweight Directory Access Protocol). What LDAP does is to provide directions and so find objects in the Active Directory database. LDAP is an important language particularly useful for advanced troubleshooting and making changes suggested by TechNet articles.
4) The physical side of Active Directory
The physical side of Active Directory means your sites and subnets. If you are familiar with Exchange then the site concept is the same in Server 2003. SUB NET = split the network, so you split your network into subnets. The network routers join these subnets to form sites. Your practical task is to tell Active Directory about the physical sites; Microsoft provide a snap-in to help you define the sites. Once the sites are created, you configure the Active Directory replication through Site Links. Lastly, double check that the domain controller objects are in the correct subnet of the correct site.
Their are two main reasons for creating a site, slow network connections and the need to control Active Directory replication traffic. What confuses beginners is that there is no relationship between sites and domains. Amateurs think there is a one to one relationship between a site and a domain - wrong. You can have one domain with many sites. Multi-nationals may need one site to have domain controller from three different domains.
Plan your sites with a TCP/IP and router expert; thereafter you will only need an occasional change to the configuration. Users and computer on the other hand, always seem to need their Active Directory settings changing.
5) The logical structure of Active Directory
How you view the logical side of Active Directory depends on your company background. Small companies will start with just one Domain and focus their efforts on how many Organization Units they need. A network architect of a large companies will be primarily concerned with how to link DNS names with Domain names, should they have a blank root domain, would that subsidiary be best in its own tree.
Logical Components
Forest - Two or more trees. Each tree has a distinct name e.g. OurCompany.com and SubsiaryCo.org
Tree - Two or more domains with the same namespace e.g. OurCompany.com and son.OurCompany.com
Domain - Remains the basic unit of security and replication
Organization Unit - Sub division of a Domain. Used with delegation, management and Group Policy
Parent / Child - The two way, transitive trust relationship between two domains
Root Domain - The first domain that you create, has additional powerful groups e.g. Enterprise Admins
Contiguous namespace - Catchphrase to describe a tree where all the domains have a common word
Schema - The definition of objects and attributes for the whole forest. Every every domain, in every tree has the same schema partition in Active Directory.
6) The Active Directory Schema
At its heart, Active Directory is an object based system. The main objects are Users, Computers, Sites and Printers. Microsoft have built these objects using attributes, for example Common name (CN), Location, Department and many more. The role of we the administrators, is to set the values, for example Common name = guyt, Location = Worcester. At this stage in our education, all we need to know is: we just configure the values through the Active Directory Users and Computers, we do not mess with the Schema itself - that is a job for a developer.
The only other practical point we need to be aware of is that when you install Exchange 2000 or 2003, you have to be a member of the Schema Admins and Enterprise Admins. Also, once Exchange is installed the User objects will have more tabs with attributes like Mailbox, email address and instant messaging.
7) Group Policy and Active Directory
My first point is that without Active Directory, there would be no Group Policies. Group policies encourage central control of the desktop. Your mantra should be 'prevention is better than cure'. My vision of a group policy is to pamper users with all the software they need, yet deny them access to any part of the computer where they have no business to roam.
The best kept secret of group policy is the chance to assign software to users. Many administrators get so carried away locking down the desktop that they overlook the change to deploy software. The advantage of this method of rolling out software is the ease with which you can service pack or update the .MSI installer files.
Do you remember the Organization Units? Well part of the reason for creating them was so that you could apply group polices. I mention this as a justification for studying all the facets to Active Directory before you start configuring. The one group policy that you need to apply at the domain level is the security policy. Reluctantly, I will leave further discussion to the Group Policy 2003 section.
Domain Trusts
The trust structure that was developed in Windows 2000 and is subsequently used in Windows .NET Server 2003 has been streamlined in comparison to the Windows NT trust structure. Windows NT trusts utilized individual explicitly defined trusts for each organizational domain. This created an exponential trust relationship, which was difficult, to say the least, to manage. Windows 2000 took the trust relationship to a new level of functionality, with transitive trusts supplying automatic paths "up and down the tree." These trusts are implicitly easier to understand and troubleshoot, and have greatly improved the manageability of Windows networks. In addition, Windows .NET Server 2003 provides for additional functionality, such as cross-forest transitive trusts, which expands the capabilities of the NOS even further.
Transitive Trusts
Two-way transitive trusts are automatically established upon the creation of a subdomain or with the addition of a domain tree into an Active Directory forest. Transitive trusts are normally two way, with each domain trusting the other domain. In other words, users in each domain can access resources such as printers or servers in the other domain if they are explicitly given rights in those domains. Bear in mind that just because two domains have a trust relationship does not mean that users from one domain can automatically access all the resources in the other domain; it is simply the first step in accessing those resources. The proper permissions still need to be applied.
Explicit Trusts
Explicit trusts are those that are set up manually, similar to the way that Windows NT trusts were constructed. A trust may be set up to join two unrelated domain trees into the same forest, for example. Explicit trusts are one way, but two explicit trusts can be established to create a two-way trust
When an explicit trust is set up to expedite the flow of trusts from one subdomain to another, it is known as a shortcut trust. Shortcut trusts simply allow authentication verifications to be processed faster, as opposed to having to move up and down a domain tree.
Another possible use for explicit trusts is to allow connectivity between an Active Directory forest and an external domain. These types of explicitly defined trusts are known as external trusts, and they allow different forests to share information without actually merging schema information or global catalogs.
NOTE
The capability to establish cross-forest trusts in Windows 2000 was limited to explicit trusts that were defined between each domain that needed access to a forest. Windows .NET Server 2003 adds the capability to establish cross-forest transitive trusts, where the trust relationships flow through separate forests.
Trust types
Communication between domains occurs through trusts. Trusts are authentication pipelines that must be present in order for users in one domain to access resources in another domain. Two default trusts are created when using the Active Directory Installation Wizard. There are four other types of trusts that can be created using the New Trust Wizard or the Netdom command-line tool.
Default trusts
By default, two-way, transitive trusts are automatically created when a new domain is added to a domain tree or forest root domain using the Active Directory Installation Wizard. The two default trust types are defined in the following table.
Trust type | Transitivity | Direction | Description |
Parent and child | Transitive | Two-way | By default, when a new child domain is added to an existing domain tree, a new parent and child trust is established. Authentication requests made from subordinate domains flow upward through their parent to the trusting domain.. |
Tree-root | Transitive | Two-way | By default, when a new domain tree is created in an existing forest, a new tree-root trust is established |
Other trusts
Four other types of trusts can be created using the New Trust Wizard or the Netdom command-line tool: external, realm, forest, and shortcut trusts. These trusts are defined in the following table.
Trust type | Transitivity | Direction | Description |
External | Nontransitive | One-way or two-way | Use external trusts to provide access to resources located on a Windows NT 4.0 domain or a domain located in a separate forest that is not joined by a forest trust. |
Realm | Transitive or nontransitive | One-way or two-way | Use realm trusts to form a trust relationship between a non-Windows Kerberos realm and a Windows Server 2003 domain.. |
Forest | Transitive | One-way or two-way | Use forest trusts to share resources between forests. If a forest trust is a two-way trust, authentication requests made in either forest can reach the other forest.. |
Shortcut | Transitive | One-way or two-way | Use shortcut trusts to improve user logon times between two domains within a Windows Server 2003 forest. This is useful when two domains are separated by two domain trees. |
When creating external, shortcut, realm, or forest trusts, you have the option to create each side of the trust separately or both sides of a trust simultaneously.
If you choose to create each side of the trust separately, then you will need to run the New Trust Wizard twice—once for each domain. When creating trusts using the method, you will need to supply the same trust password for each domain. As a security best practice, all trust passwords should be strong passwords.
If you choose to create both sides of the trust simultaneously, you will need to run the New Trust Wizard once. When you choose this option, a strong trust password is automatically generated for you.
You will need the appropriate administrative credentials for each domain between which you will be creating a trust.
Netdom.exe can also be used to create trusts.
There are many companies / brands / products whose names were derived from strange circumstances.
Mercedes
This was actually the financier’s daughter’s name.
Adobe
This came from name of the river Adobe Creek that ran behind the house of founder John Warnock.
Apple Computers
It was the favorite fruit of founder Steve Jobs. He was three months late in filing a name for the business, and he threatened to call his company Apple Computers if the other colleagues didn’t suggest a better name by 5 O’clock.
CISCO
It is not an acronym as popularly believed. It is short for San Francisco.
Compaq
This name was formed by using COMp, for computer, and PAQ to denote a small integral object.
Corel
The name was derived from the founder’s name Dr.Michael Cowpland. It stands for COwpland REsearch Laboratory.
Google
The name started as a joke boasting about the amount of information the search-engine would be able to search. It was originally named ‘Googol’, a word for the number represented by 1 followed by 100 zeros.
After founders- Stanford graduate students Sergey Brin and Larry Page presented their project to an angel investor, they received a cheque made out to ‘Google’
Hotmail
Founder Jack Smith got the idea of accessing e-mail via the web from a computer anywhere in the world. When Sabeer Bhatia came up with the business plan for the mail service, he tried all kinds of names ending in
‘mail’ and finally settled for hotmail as it included the letters “html” – the programming language used to write web pages. It was initially referred to as HoTMaiL with selective uppercasing.
Hewlett Packard
Bill Hewlett and Dave Packard tossed a coin to decide whether the company they founded would be called Hewlett-Packard or Packard-Hewlett.
Intel
Bob Noyce and Gordon Moore wanted to name their new company ‘Moore Noyce’but that was already trademarked by a hotel chain so they had to settle for an acronym of INTegrated ELectronics.
Lotus (Notes)
Mitch Kapor got the name for his company from ‘The Lotus Position’ or ‘Padmasana’. Kapoor used to be a teacher of Transcendental editation of Maharishi Mahesh Yogi.
Microsoft
Coined by Bill Gates to represent the company that was devoted to MICROcomputer SOFTware. Originally christened Micro-Soft, the ‘-’ was removed later on.
Motorola
Founder Paul Galvin came up with this name when his company started manufacturing radios for cars. The popular radio company at the time was called Victrola.
ORACLE
Larry Ellison and Bob Oats were working on a consulting project for the CIA (Central Intelligence Agency). The code name for the project was called Oracle (the CIA saw this as the system to give answers to all questions or something such). The project was designed to help use the newly written SQL code by IBM. The project eventually was terminated but Larry and Bob decided to finish what they started and bring it to the world. They kept the name Oracle and created the RDBMS engine. Later they kept the same name for the company.
Sony
It originated from the Latin word ’sonus’ meaning sound, and ’sonny’ a slang used by Americans to refer to a bright youngster.
SUN
Founded by 4 Stanford Universitybuddies, SUN is the acronym for Stanford University Network. Andreas Bechtolsheim built a icrocomputer; Vinod Khosla recruited him and Scott McNealy to manufacture computers based on it, and Bill Joy to develop a UNIX-based OS for the computer.
Yahoo!
The word was invented by Jonathan Swift and used in his book ‘Gulliver’s Travels’. It represents a person who is repulsive in appearance and action and is barely human. Yahoo! Founders Jerry Yang and David Filo selected the name because they considered themselves yahoos
PANKAJ SHARMA..........
Manual steps to back up the registry
1. Click Start, click Run, type %SystemRoot%\system32\restore\rstrui.exe, and then click OK.
2. On the Welcome to System Restore page, click Create a restore point, and then click Next.
3. On the Create a Restore Point page, type a name for the restore point and then click Create.
4. After the restore point has been created, click Close.
Note If System Restore is turned off, you receive a message that asks whether you want to turn on System Restore now. Click Yes. Then, in the System Properties dialog box, click to clear the Turn off System Restore check box, click OK, and then repeat this step.
Manual steps to restore the registry
1. Click Start, click Run, type %SystemRoot%\system32\restore\rstrui.exe, and then click OK.
2. On the Welcome to System Restore page, click Restore my computer to an earlier time (if it is not already selected), and then click Next.
3. On the Select a Restore Point page, click the system checkpoint. In the On this list select the restore point area, click an entry that is named "Guided Help (Registry Backup)," and then click Next. If a System Restore message appears that lists configuration changes that System Restore will make, click OK.
4. On the Confirm Restore Point Selection page, click Next. System Restore restores the previous Windows XP configuration and then restarts the computer.
5. Log on to the computer. When the System Restore confirmation page appears, click OK.
To change the name of the Recycle Bin desktop icon, open Regedit and go to:
HKEY_CLASSES_ROOT/CLSID/{645FF040-5081-101B-9F08-00AA002F954E}
and change the name "Recycle Bin" to whatever you want (don't type any quotes).
PANKAJ SHARMA...
