How to Manually Configure FSMO Roles to Separate DC’s

How can I determine who are the current FSMO Roles holders in my domain/forest

Windows 2000/2003 Active Directory domains utilize a Single Operation Master method called FSMO (Flexible Single Master Operation), as described in Understanding FSMO Roles in Active Directory.

The five FSMO roles are:

Schema master - Forest-wide and one per forest.
Domain naming master - Forest-wide and one per forest.
RID master - Domain-specific and one for each domain.
PDC - PDC Emulator is domain-specific and one for each domain.
Infrastructure master - Domain-specific and one for each domain

In most cases an administrator can keep the FSMO role holders (all 5 of them) in the same spot (or actually, on the same DC) as has been configured by the Active Directory installation process. However, there are scenarios where an administrator would want to move one or more of the FSMO roles from the default holder DC to a different DC. The transferring method is described in the Transferring FSMO Roles article, while seizing the roles from a non-operational DC to a different DC is described in the Seizing FSMO Roles article
In order to better understand your AD infrastructure and to know the added value that each DC might possess, an AD administrator must have the exact knowledge of which one of the existing DCs is holding a FSMO role, and what role it holds. With that knowledge in hand, the administrator can make better arrangements in case of a scheduled shut-down of any given DC, and better prepare him or herself in case of a non-scheduled cease of operation from one of the DCs.

How to find out which DC is holding which FSMO role? Well,

one can accomplish this task by many means. This article will list a few of the available methods.

Method #1: Know the default settings

The FSMO roles were assigned to one or more DCs during the DCPROMO process. The following table summarizes the FSMO default locations

FSMO Roll -  Schema   

Number of DC's Holding this Role- One per forest

Original DC Holding this Role  - The first DC in the first Domin                   

Domain Naming	One per forest	forest (i.e. the Forest Root Domain)
RID	One per domain	The first DC in a domain (any domain,
PDC Emulator	One per domain	including the Forest Root Domain, any
Infrastructure	One per domain	Tree Root Domain, or any Child
		Domain)

Method #2:Use The GUI

The FSMO role holders can be easily found by use of some of the AD snap-ins. Use this table to see which tool can be used for what FSMO role

Fsmo Role                   Which snap-in should I use?

Schema                     Schema snap-in

Domain Naming           AD Domains and Trusts-in

RID                            AD User and Computers snap-in

PDC emulator

Infrastructure

Finding the RID Master, PDC Emulator, and Infrastructure Masters via GUI 

To find out who currently holds the Domain-Specific RID Master, PDC Emulator, and Infrastructure Master 

FSMO Roles: 

1.Open the Active Directory Users and Computers snap-in from the Administrative Tools folder. 

2.Right-click the Active Directory Users and Computers icon again and press Operation Masters. 

3.Select the appropriate tab for the role you wish to view. 

4.When you're done click Close.

Finding the Domain Naming Master via GUI 

To find out who currently holds the Domain Naming Master Role: 

1.Open the Active Directory Domains and Trusts snap-in from the Administrative Tools folder. 

2.Right-click the Active Directory Domains and Trusts icon again and press Operation Masters. 

3.When you're done click Close. 

Finding the Schema Master via GUI 

To find out who currently holds the Schema Master Role: 

1.Register the Schmmgmt.dll library by pressing Start > RUN and typing: 

2.Press OK. You should receive a success confirmation. 

3.From the Run command open an MMC Console by typing MMC. 

4.On the Console menu, press Add/Remove Snap-in. 

5.Press Add. Select Active Directory Schema. 

6.Press Add and press Close. Press OK. 

7.Click the Active Directory Schema icon. After it loads right-click it and press Operation Masters. 

8.Press the Close button. 

Method #3: Use the Ntdsutil command 

The FSMO role holders can be easily found by use of the Ntdsutil command. 

Caution: Using the Ntdsutil utility incorrectly may result in partial or complete loss of Active Directory functionality

1.On any domain controller, click Start, click Run, type Ntdsutil in the Open box, and then click OK. 

2.Type roles, and then press ENTER. 

Note:To see a list of available commands at any of the prompts in the Ntdsutil tool, type ?, and then press ENTER

1.Type connections, and then press ENTER. 

2.Type connect to server <servername>, where <servername> is the name of the server you want to use, and then press ENTER. 

3.At the server connections: prompt, type q, and then press ENTER again. 

4.At the FSMO maintenance: prompt, type Select operation target, and then press ENTER again.

At the select operation target: prompt, type List roles for connected server, and then press ENTER again. select operation target: List roles for connected server 

Server "server100" knows about 5 roles Schema - CN=NTDS Settings,CN=SERVER100,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=C  

onfiguration,DC=dpetri,DC=net 

Domain - CN=NTDS 

Settings,CN=SERVER100,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=C 

onfiguration,DC=dpetri,DC=net PDC - CN=NTDS 

Settings,CN=SERVER100,CN=Servers,CN=Default-First-Site

Name,CN=Sites,CN=Conf 

iguration,DC=dpetri,DC=net 

RID - CN=NTDS Settings,CN=SERVER100,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Conf iguration,DC=dpetri,DC=net 

Infrastructure - CN=NTDS 

Settings,CN=SERVER100,CN=Servers,CN=Default-First-Site-Name,CN=Si 

tes,CN=Configuration,DC=dpetri,DC=net 

Select operation target:

8.Type q 3 times to exit the Ntdsutil prompt

Note: You can download THIS nice batch file that will do all this for you (1kb). 

Another Note: Microsoft has a nice tool called Dumpfsmos.cmd, found in the Windows 2000 Resource Kit (and can be downloaded here: Download Free Windows 2000 Resource Kit Tools). This tool is basically a one-click Ntdsutil script that performs the same operation described above

Method #4: Use the Netdom command 

The FSMO role holders can be easily found by use of the Netdom command

Netdom.exe is a part of the Windows 2000/XP/2003 Support Tools. You must either download it separately (from here Download Free Windows 2000 Resource Kit Tools) or by obtaining the correct Support Tools pack for your operating system. The Support Tools pack can be found in the \Support\Tools folder on your installation CD (or you can Download Windows 2000 SP4 Support Tools, Download Windows XP SP1 Deploy Tools). 

1.On any domain controller, click Start, click Run, type CMD in the Open box, and then click OK. 

2.In the Command Prompt window, type netdom query /domain:<domain> fsmo (where <domain> is the name of YOUR domain)

Close the CMD window

Note: You can download THIS nice batch file that will do all this for you (1kb).  

Method #5: Use the Replmon tool 

The FSMO role holders can be easily found by use of the Netdom command. 

Just like Netdom, Replmon.exe is a part of the Windows 2000/XP/2003 Support Tools. Replmon can be used for a wide verity of tasks, mostly with those that are related with AD replication. But Replmon can also provide valuable information about the AD, about any DC, and also about other objects and settings, such as GPOs and FSMO roles. Install the package before attempting to use the tool. 

1On any domain controller, click Start, click Run, type REPLMON in the Open box, and then click OK. 

2.Right-click Monitored servers and select Add Monitored Server. 

3.In the Add Server to Monitor window, select the Search the Directory for the server to add. Make sure your AD domain name is listed in the drop-down list. 

4.In the site list select your site, expand it, and click to select the server you want to query. Click Finish. 

5.Right-click the server that is now listed in the left-pane, and select Properties. 

6.Click on the FSMO Roles tab and read the results. 

7.Click Ok when you're done.

Read More

Troubleshooting Startup Issues after configuration change on IBM x3550M2, x3650 M2 Servers

Scenario: IMM or system fails after configuration change or IMM reboot -IBM System x3550 M2, x3650 M2.
Symptom
After changing the hardware configuration of System x3550 M2 or System x3650 M2, most often when adding options such as memory, hard drives, and Central Processing Units (CPUs), the system may become unresponsive after about 30 minutes.
Some cases prevented the box from powering on again, and in some cases, power on was possible, but network connectivity to the Integrated Management Module (IMM) was not possible. The issue may also occur when rebooting the IMM while the system is powered on with certain hardware configurations

Affected configurations 
System x3550 M2, type 4198, any model
System x3550 M2, type 7946, any model
System x3650 M2, type 4199, any model
System x3650 M2, type 7947, any model
IMM firmware versions older than YUOO24I version 1.04

Solution 
A fix was provided in IMM firmware yuoo24I (version 1.04).
All users of System x3550 M2 and System x3650 M2 should update to this IMM firmware or later to avoid the possibility of replacing the system board.
The file is available from the 'Software and device drivers ¬IBM System x' web site at the following
URL: http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4JTS2T

Additional information 
An internal buffer overrun issue in the IMM code caused the IMM firmware to repeatedly crash. The internal buffering issue was corrected in yuoo24I. Hardware configurations with large numbers of memory DIMMs and hard disk drives could result in unresponsive systems if the system was powered on and the IMM was rebooted with older firmware

Read More

Windows & systen admin Interview Questions and Answers- Part 1

Difference between 2000 &2003
Application Server mode is introduced in windows 2003 Possible to configure stub zones in windows 2003 DNS Volume shadow copy services is introduced Windows 2003 gives an option to replicate DNS data b/w all DNS servers in forest or All DNS servers in the domain.

Difference between PDC & BDC
PDC contains a write copy of SAM database where as BDC contains read only copy of SAM database. It is not possible to reset a password or create objects with out PDC in Windows NT.

Difference between DC &ADC
There is no difference between in DC and ADC both contains write copy of AD. Both can also handles FSMO roles (If transfers from DC to ADC). It is just for identification. Functionality wise there is no difference.

What is DNS & WINS
DNS is a Domain Naming System, which resolves Host names to IP addresses. It uses fully qualified domain names. DNS is a Internet standard used to resolve host names
WINS is a Windows Internet Name Service, which resolves Netbios names to IP Address. This is proprietary for Windows

Types of DNS Servers
Primary DNS Secondary DNS Active Directory Integrated DNS Forwarder Caching only DNS

If DHCP is not available what happens to the client
Client will not get IP and it cannot be participated in network . If client already got the IP and having lease duration it use the IP till the lease duration expires.

what are the different types of trust relationships
Implicit Trusts Explicit Trusts—NT to Win2k or Forest to Forest

what is the process of DHCP for getting the IP address to the client
There is a four way negotiation process b/w client and server DHCP Discover (Initiated by client) DHCP Offer (Initiated by server) DHCP Select (Initiated by client)
DHCP Acknowledgement (Initiated by Server)
DHCP Negative Acknowledgement (Initiated by server if any issues after DHCP offer)

Difference between FAT,NTFS &amp; NTFSVersion5
NTFS Version 5 features
Encryption is possible We can enable Disk Quotas File compression is possible Sparse files Indexing Service NTFS change journal In FAT file system we can apply only share level security. File level protection is not
possible. In NTFS we can apply both share level as well as file level security NTFS supports large partition sizes than FAT file systems NTFS supports long file names than FAT file systems
What are the port numbers for FTP, Telnet, HTTP, DNS
FTP-21, Telnet – 23, HTTP-80, DNS-53, Kerberos-88, LDAP-389

what are the different types of profiles in 2000
Local Profiles Roaming profiles Mandatory Profiles

what is the database files used for Active Directory
The key AD database files—edb.log, ntds.dit, res1.log, res2.log, and edb.chk—all of which reside in \%systemroot%\ntds on a domain controller (DC) by default. During
AD installation, Dcpromo lets you specify alternative locations for these log files and database files

What is the location of AD Database
%System root%/NTDS/NTDS&gt;DIT

What is the authentication protocol used in NT
NTLM (NT LAN Manager

What is subnetting and supernetting
Subnetting is the process of borrowing bits from the host portion of an address to provide bits for identifying additional sub-networks
Supernetting merges several smaller blocks of IP addresses (networks) that are continuous into one larger block of addresses. Borrowing network bits to combine several smaller networks into one larger network does supernetting

what is the use of terminal services
Terminal services can be used as Remote Administration mode to administer remotely as well as Application Server Mode to run the application in one server and users can login to that server to user that application

what is the protocol used for terminal services
RDP

what is the port number for RDP
Port Number-3389    


what is the difference between Authorized DHCP and Non Authorized DHCP
To avoid problems in the network causing by mis-configured DHCP servers, server in windows 2000 must be validate by AD before starting service to clients. If an authorized DHCP finds any DHCP server in the network it stop serving the clients

Difference between inter-site and intra-site replication. Protocols using for replication.
Intra-site replication can be done between the domain controllers in the same site. Inter-site replication can be done between two different sites over WAN links
BHS (Bridge Head Servers) is responsible for initiating replication between the sites. Inter-site replication can be done B/w BHS in one site and BHS in another site.
We can use RPC over IP or SMTP as a replication protocols where as Domain partition is not possible to replicate using SMTP

How to monitor replication 

We can user Replmon tool from support tools

Brief explanation of RAID Levels 

Microsoft Windows XP, Windows 2000 and Windows Server 2003 offer two types of disk storage: basic and dynamic

Basic Disk Storage
Basic storage uses normal partition tables supported by MS-DOS, Microsoft Windows 95, Microsoft Windows 98, Microsoft Windows Millennium Edition (Me), Microsoft Windows NT, Microsoft Windows 2000, Windows Server 2003 and Windows XP. A disk initialized for basic storage is called a basic disk. A basic disk contains basic volumes, such as primary partitions, extended partitions, and logical drives. Additionally, basic volumes include multidisk volumes that are created by using Windows NT 4.0 or earlier, such as volume sets, stripe sets, mirror sets, and stripe sets with parity. Windows XP does not support these multidisk basic volumes. Any volume sets, stripe sets, mirror sets, or stripe sets with parity must be backed up and deleted or converted to dynamic disks before you install Windows XP Professional

Dynamic Disk Storage
Dynamic storage is supported in Windows XP Professional, Windows 2000 and Windows Server 2003. A disk initialized for dynamic storage is called a dynamic disk. A dynamic disk contains dynamic volumes, such as simple volumes, spanned volumes, striped volumes, mirrored volumes, and RAID-5 volumes. With dynamic storage, you can perform disk and volume management without the need to restart Windows.
Note: Dynamic disks are not supported on portable computers or on Windows XP Home Edition-based computers.
You cannot create mirrored volumes or RAID-5 volumes on Windows XP Home Edition, Windows XP Professional, or Windows XP 64-Bit Edition-based computers. However, you can use a Windows XP Professional-based computer to create a mirrored or RAID-5 volume on remote computers that are running Windows 2000 Server, Windows 2000 Advanced Server, or Windows 2000 Datacenter Server, or the Standard, Enterprise and Data Center versions of Windows Server 2003.
Storage types are separate from the file system type. A basic or dynamic disk can contain any combination of FAT16, FAT32, or NTFS partitions or volumes.
A disk system can contain any combination of storage types. However, all volumes on the same disk must use the same storage type.

To convert a Basic Disk to a Dynamic Disk

Use the Disk Management snap-in in Windows XP/2000/2003 to convert a basic disk to a dynamic disk. To do this, follow these steps: 

1Log on as Administrator or as a member of the Administrators group. 

2Click Start, and then click Control Panel. 

3Click Performance and Maintenance, click Administrative Tools, and then double-click Computer Management. You can also right-click My Computer and choose Manage if you have My Computer displayed on your desktop. 

4In the left pane, click Disk Management. 

5In the lower-right pane, right-click the basic disk that you want to convert, and then click Convert to Dynamic Disk. You must right-click the gray area that contains the disk title on the left side of the Details pane. 

6Select the check box that is next to the disk that you want to convert (if it is not already selected), and then click OK. 

7Click Details if you want to view the list of volumes in the disk. Click Convert. 

8Click Yes when you are prompted to convert the disk, and then click OK. 

Warning: After you convert a basic disk to a dynamic disk, local access to the dynamic disk is limited to Windows XP Professional, Windows 2000 and Windows Server 2003. Additionally, after you convert a basic disk to a dynamic disk, the dynamic volumes cannot be changed back to partitions. You must first delete all dynamic volumes on the disk and then convert the dynamic disk back to a basic disk. If you want to keep your data, you must first back up the data or move it to another volume. 

Dynamic Storage Terms 

A volume is a storage unit made from free space on one or more disks. It can be formatted with a file system and assigned a drive letter. Volumes on dynamic disks can have any of the following layouts: simple, spanned, mirrored, striped, or RAID-5. 

A simple volume uses free space from a single disk. It can be a single region on a disk or consist of multiple, concatenated regions. A simple volume can be extended within the same disk or onto additional disks. If a simple volume is extended across multiple disks, it becomes a spanned volume. 

A spanned volume is created from free disk space that is linked together from multiple disks. You can extend a spanned volume onto a maximum of 32 disks. A spanned volume cannot be mirrored and is not fault-tolerant. 

A striped volume is a volume whose data is interleaved across two or more physical disks. The data on this type of volume is allocated alternately and evenly to each of the physical disks. A striped volume cannot be mirrored or extended and is not fault-tolerant. Striping is also known as RAID-0. 

A mirrored volume is a fault-tolerant volume whose data is duplicated on two physical disks. All of the data on one volume is copied to another disk to provide data redundancy. If one of the disks fails, the data can still be accessed from the remaining disk. A mirrored volume cannot be extended. Mirroring is also known as RAID-1. 

A RAID-5 volume is a fault-tolerant volume whose data is striped across an array of three or more disks. Parity (a calculated value that can be used to reconstruct data after a failure) is also striped across the disk array. If a physical disk fails, the portion of the RAID-5 volume that was on that failed disk can be re-created from the remaining data and the parity. A RAID¬5 volume cannot be mirrored or extended. 

The system volume contains the hardware-specific files that are needed to load Windows (for example, Ntldr, Boot.ini, and Ntdetect.com). The system volume can be, but does not have to be, the same as the boot volume. 

The boot volume contains the Windows operating system files that are located in the %Systemroot% and %Systemroot%\System32 folders. The boot volume can be, but does not have to be, the same as the system volume. 

RAID 0 – Striping 

RAID 1- Mirroring (minimum 2 HDD required) 

RAID 5 – Striping With Parity (Minimum 3 HDD required) 

RAID levels 1 and 5 only gives redundancy 

What are the different backup strategies are available 

Normal Backup 

Incremental Backup 

Differential Backup 

Daily Backup 

Copy Backup 

What is a global catalog 

Global catalog is a role, which maintains Indexes about objects. It contains full information of the objects in its own domain and partial information of the objects in other domains. Universal Group membership information will be stored in global catalog servers and replicate to all GC’s in the forest. 

What is Active Directory and what is the use of it 

Active directory is a directory service, which maintains the relation ship between resources and enabling them to work together. Because of AD hierarchal structure windows 2000 is more scalable, reliable. Active directory is derived from X.500 standards where information is stored is hierarchal tree like structure. Active directory depends on two Internet standards one is DNS and other is LDAP. Information in Active directory can be queried by using LDAP protocol 

What is the physical and logical structure of AD 

Active directory physical structure is a hierarchal structure which fallows Forests— Trees—Domains—Child Domains—Grand Child—etc 

Active directory is logically divided into 3 partitions 

1.Configuration partition 2. Schema Partition 3. Domain partition 4. Application Partition (only in windows 2003 not available in windows 2000) 

Out of these Configuration, Schema partitions can be replicated between the domain controllers in the in the entire forest. Where as Domain partition can be replicated between the domain controllers in the same domain 

What is the process of user authentication (Kerberos V5) in windows 2000 

After giving logon credentials an encryption key will be generated which is used to encrypt the time stamp of the client machine. User name and encrypted timestamp information will be provided to domain controller for authentication. Then Domain controller based on the password information stored in AD for that user it decrypts the encrypted time stamp information. If produces time stamp matches to its time stamp. It will provide logon session key and Ticket granting ticket to client in an encryption format. Again client decrypts and if produced time stamp information is matching then it will use logon session key to logon to the domain. Ticket granting ticket will be used to generate service granting ticket when accessing network resources 

What are the port numbers for Kerberos, LDAP and Global catalog 

Kerberos – 88, LDAP – 389, Global Catalog – 3268 

What is the use of LDAP (X.500 standard?) 

LDAP is a directory access protocol, which is used to exchange directory information from server to clients or from server to servers 

What are the problems that are generally come across DHCP 

Scope is full with IP addresses no IP’s available for new machines 

If scope options are not configured properly eg default gateway 

Incorrect creation of scopes etc 

what is the role responsible for time synchronization 

PDC Emulator is responsible for time synchronization. Time synchronization is important because Kerberos authentication depends on time stamp information 

What is TTL & how to set TTL time in DNS 

TTL is Time to Live setting used for the amount of time that the record should remain in cache when name resolution happened. 

We can set TTL in SOA (start of authority record) of DNS 

How to take DNS and WINS,DHCP backup 

%System root%/system32/dns 

%System root%/system32/WINS 

%System root%/system32/DHCP 

What is recovery console 

Recovery console is a utility used to recover the system when it is not booting properly or not at all booting. We can perform fallowing operations from recovery console 

We can copy, rename, or replace operating system files and folders Enable or disable service or device startup the next time that start computer Repair the file system boot sector or the Master Boot Record Create and format partitions on drives 

What is DFS & its usage 

DFS is a distributed file system used to provide common environment for users to access files and folders even when they are shared in different servers physically. 

There are two types of DFS domain DFS and Stand alone DFS. We cannot provide redundancy for stand alone DFS in case of failure. Domain DFS is used in a domain environment which can be accessed by /domain name/root1 (root 1 is DFS root name). Stand alone DFS can be used in workgroup environment which can be accessed through /server name/root1 (root 1 is DFS root name). Both the cases we need to create DFS root ( Which appears like a shared folder for end users) and DFS links ( A logical link which is pointing to the server where the folder is physically shared) 

The maximum number of Dfs roots per server is 1. 

The maximum numbers of Dfs root replicas are 31. 

The maximum number of Dfs roots per domain is unlimited. 

The maximum number of Dfs links or shared folders in a Dfs root is 1,000 

Read More

Difference Between NT & 2000 - YuvaTips

Difference Between NT & 2000 - YuvaTips

Read More

Difference Between NT & 2000

NT SAM database is a flat database. Where as in windows 2000 active directory

database is a hierarchical database. In windows NT only PDC is having writable copy of SAM database but the BDC is only read only database. In case of Windows 2000 both DC and ADC is having write copy of the database

Windows NT will not support FAT32 file system. Windows 2000 supports FAT32

Default authentication protocol in NT is NTLM (NT LAN manager). In windows 2000 default authentication protocol is Kerberos V5. Windows 2000 depends and Integrated with DNS. NT user Netbios names Active Directory can be backed up easily with System state data

Read More

Resolution of SKU011 Error in Ms Office

It happens to most Windows users; one day out of the blue your PC decides it doesn't want to let you run any of the Microsoft Office applications. Most likely, you have receive the "Installation Error: File not Found" error message as seen in below snapshot

This is another classic misleading windows error message, which causes you to rummage the internet for the file sku011.cab when in fact; you didn't have this file on your computer when Microsoft Office was working! In the next section, we will discuss the overall approach to fixing the problem at hand. All though Microsoft’s error messages reads "A required installation SKU011.CAB could not be found" and the dialogue box prompts for the location of this file, this is not the underlying cause of the problem, it is just a symptom. The root of the problem lies within the Window's Registry. Part of the initialization of Microsoft Office, values are pulled out of the registry in order for the application to execute as the user would expect the program to run. When the CDCache is set to a value other than 0, Windows tries to perform a supplemental install that http://www.sku011cab.com deems to be unnecessary. Updating the CDCache value in the registry to 0, fixes the issue pertaining to sku011.cab. In short, no additional file needs to be downloaded and the next section gives a step by step instruction to update your Microsoft Office CDCache value to 0. In start / execute : Regedit HKEY_LOCAL_MACHINE -> Software -> Microsoft -> Office -> 11.0 -> Delivery You should have this key 90000409-6000-11D3-8CFE-0150048383C9 Click on it and (at the

right of your screen), right clik on CDCache key. and type 0 as new value

In start / execute : Regedit HKEY_LOCAL_MACHINE -> Software -> Microsoft -> Office -> 11.0 -> Delivery You should have this key 900004

09-6000-11D3-8CFE-0150048383C9 Click on it and (at the right of your screen), right clik on CDCache key. and type 0 as new value

Read More

Port Number list

Port Number:

This is a list of Internet socket port numbers used by protocols of the Transport Layer of the Internet Protocol Suite for the establishment of host-to-host communications

1. Number      port
2. 1         tcpmux
3. 5          rje
4. 7        echo
5. 9       discard
6. 11       systat
7. 13      daytime
8. 15      netstat
9. 17     qotd
10. 18     send/rwp
11. 19     chargen
12. 20    ftp-data
13. 21    ftp
14. 22    ssh, pcAnywhere
15. 23   Telnet
16. 25   SMTP
17. 27   ETRN
18. 29   msg-icp
19. 31  msg-auth
20. 33  dsp
21. 37  time
22. 38  RAP
23. 39  rlp
24. 42  nameserv, WINS
25. 43  whois, nickname
26. 49 TACACS, Login Host Protocol
27. 50 RMCP, re-mail-ck
28. 53 DNS
29. 57 MTP
30. 59 NFILE
31. 63 whois++
32. 66 sql*net
33. 67 bootps
34. 68 bootpd/dhcp
35. 69 Trivial File Transfer Protocol (tftp)
36. 70 Gopher
37. 79 finger
38. 80 www-http
39. 88 Kerberos, WWW
40. 95 supdup
41. 96 DIXIE
42. 98 linuxconf
43. 101 HOSTNAME
44. 102 ISO, X.400, ITOT
45. 105 cso
46. 106 poppassd
47. 109 POP2
48. 110 POP3
49. 111 Sun RPC Portmapper
50. 113 identd/auth
51. 115 sftp
52. 117 uucp
53. 119 NNTP
54. 120 CFDP
55. 123 NTP
56. 124 SecureID
57. 129 PWDGEN
58. 133 statsrv
59. 135 loc-srv/epmap
60. 137 netbios-ns
61. 138 netbios-dgm (UDP)
62. 139 NetBIOS
63. 143 IMAP
64. 144 NewS
65. 152 BFTP
66. 153 SGMP
67. 161 SNMP
68. 175 vmnet
69. 177 XDMCP
70. 178 NextStep Window Server
71. 179 BGP
72. 180 SLmail admin
73. 199 smux
74. 210 Z39.50
75. 218 MPP
76. 220 IMAP3
77. 259 ESRO
78. 264 FW1_topo
79. 311 Apple WebAdmin
80. 350 MATIP type A
81. 351 MATIP type B
82. 363 RSVP tunnel
83. 366 ODMR (On-Demand Mail Relay)
84. 387 AURP (AppleTalk Update-Based Routing Protocol)
85. 389 LDAP
86. 407 Timbuktu
87. 434 Mobile IP
88. 443 ssl
89. 444 snpp, Simple Network Paging Protocol
90. 445 SMB
91. 458 QuickTime TV/Conferencing
92. 468 Photuris
93. 500 ISAKMP, pluto
94. 512 biff, rexec
95. 513 who, rlogin
96. 514 syslog, rsh
97. 515 lp, lpr, line printer
98. 517 talk
99. 520 RIP (Routing Information Protocol)
100. 521 RIPng
101. 522 ULS
102. 531 IRC
103. 543 KLogin, AppleShare over IP
104. 545 QuickTime
105. 548 AFP
106. 554 Real Time Streaming Protocol
107. 555 phAse Zero
108. 563 NNTP over SSL
109. 575 VEMMI
110. 581 Bundle Discovery Protocol
111. 593 MS-RPC
112. 608 SIFT/UFT
113. 626 Apple ASIA
114. 631 IPP (Internet Printing Protocol)
115. 635 mountd
116. 636 sldap
117. 642 EMSD
118. 648 RRP (NSI Registry Registrar Protocol)
119. 655 tinc
120. 660 Apple MacOS Server Admin
121. 666 Doom
122. 674 ACAP
123. 687 AppleShare IP Registry
124. 700 buddyphone
125. 705 AgentX for SNMP
126. 901 swat, realsecure
127. 993 s-imap
128. 995 s-pop
129. 1062 Veracity
130. 1080 SOCKS
131. 1085 WebObjects
132. 1227 DNS2Go
133. 1243 SubSeven
134. 1338 Millennium Worm
135. 1352 Lotus Notes
136. 1381 Apple Network License Manager
137. 1417 Timbuktu
138. 1418 Timbuktu
139. 1419 Timbuktu
140. 1433 Microsoft SQL Server
141. 1434 Microsoft SQL Monitor
142. 1494 Citrix ICA Protocol
143. 1503 T.120
144. 1521 Oracle SQL
145. 1525 prospero
146. 1526 prospero
147. 1527 tlisrv
148. 1604 Citrix ICA, MS Terminal Server
149. 1645 RADIUS Authentication
150. 1646 RADIUS Accounting
151. 1680 Carbon Copy
152. 1701 L2TP/LSF
153. 1717 Convoy
154. 1720 H.323/Q.931
155. 1723 PPTP control port
156. 1755 Windows Media .asf
157. 1758 TFTP multicast
158. 1812 RADIUS server
159. 1813 RADIUS accounting
160. 1818 ETFTP
161. 1973 DLSw DCAP/DRAP
162. 1985 HSRP
163. 1999 Cisco AUTH
164. 2001 glimpse
165. 2049 NFS
166. 2064 distributed.net
167. 2065 DLSw
168. 2066 DLSw
169. 2106 MZAP
170. 2140 DeepThroat
171. 2301 Compaq Insight Management Web Agents
172. 2327 Netscape Conference
173. 2336 Apple UG Control
174. 2427 MGCP gateway
175. 2504 WLBS
176. 2535 MADCAP
177. 2543 sip
178. 2592 netrek
179. 2727 MGCP call agent
180. 2628 DICT
181. 2998 ISS Real Secure Console Service Port
182. 3000 Firstclass
183. 3031 Apple AgentVU
184. 3128 squid
185. 3130 ICP
186. 3150 DeepThroat
187. 3264 ccmail
188. 3283 Apple NetAssitant
189. 3288 COPS
190. 3305 ODETTE
191. 3306 mySQL
192. 3389 RDP Protocol (Terminal Server)
193. 3521 netrek
194. 4000 icq, command-n-conquer
195. 4321 rwhois
196. 4333 mSQL
197. 4827 HTCP
198. 5004 RTP
199. 5005 RTP
200. 5010 Yahoo! Messenger
201. 5060 SIP
202. 5190 AIM
203. 5500 securid
204. 5501 securidprop
205. 5423 Apple VirtualUser
206. 5631 PCAnywhere data
207. 5632 PCAnywhere
208. 5800 VNC
209. 5801 VNC
210. 5900 VNC
211. 5901 VNC
212. 6000 X Windows
213. 6112 BattleNet
214. 6502 Netscape Conference
215. 6667 IRC
216. 6670 VocalTec Internet Phone, DeepThroat
217. 6699 napster
218. 6776 Sub7
219. 6970 RTP
220. 7007 MSBD, Windows Media encoder
221. 7070 RealServer/QuickTime
222. 7778 Unreal
223. 7648 CU-SeeMe
224. 7649 CU-SeeMe
225. 8010 WinGate 2.1
226. 8080 HTTP
227. 8181 HTTP
228. 8383 IMail WWW
229. 8875 napster
230. 8888 napster
231. 10008 cheese worm
232. 11371 PGP 5 Keyserver
233. 13223 PowWow
234. 13224 PowWow
235. 14237 Palm
236. 14238 Palm
237. 18888 LiquidAudio
238. 21157 Activision
239. 23213 PowWow
240. 23214 PowWow
241. 23456 EvilFTP
242. 26000 Quake
243. 27001 QuakeWorld
244. 27010 Half-Life
245. 27015 Half-Life
246. 27960 QuakeIII
247. 30029 AOL Admin
248. 31337 Back Orifice
249. 32777 rpc.walld
250. 40193 Novell
251. 41524 arcserve discovery
252. 45000 Cisco NetRanger postofficed
253. 32773 rpc.ttdbserverd
254. 32776 rpc.spray
255. 32779 rpc.cmsd
256. 38036 timestep

Read More

Video for Windows Server 2008 DNS Manual Setup

This is how you setup DNS manually. You can le

t windows setup for you or you can manually set it up. This will be a good practice to learn.

Read More

windows 7 advantages and disadvantages

Advantages:

1. Windows 7 is faster than its predecessors, both in terms of installation and boot up time.
2. Calculator has been enhanced with some new features like unit conversion, calculations like fuel economy and auto lease payment.
3. WordPad in Windows 7 has improved much better and look similar to the Microsoft Office Word. It can be used to open, edit file names with docx extension which was earlier introduced with MS-Office 2007. Word prediction is the new feature in Word Pad. Realistic brush has been added in Paint.
4. Microsoft facilitates in windows 7, to download some eye-catching themes and background images from its own Microsoft website or from RSS feed. It allows the user to customize every part of the themes and save for our future use or send to the other windows 7 users.
5. It also supports advanced touch and handwriting recognition.
6. Windows 7 supports Virtual Hard Disks with the support of enhanced performances of multi core processors.
7. Windows Media Player 12 has got much enhanced features in the Windows 7 and drag and drop option has been added which were not there in the previous versions.
8. Windows 7 allows the user to make the best use of graphic cards from the different vendors.
9. Bitlocker is a feature which provides encryption for the internal drives in vista, but it is extended to the external drives in windows 7. This makes backup and restore much easier.
10. Default settings of User Account have been eliminated, to protect form the unauthorized software to be installed.
11. Windows 7 has included a new concept, jumplists which organize the recently used files as well as web pages.
12. More than that, it also allows the user to overcome the clutter in the desktop by introducing three new features Aero Peek, Aero shake and snap.
13. Home networking has been made much easier than its previous operating systems and is probably safe from hackers.

 Disadvantages:


1. Some of the users are not satisfied with the new features, because, they need to buy out additional resources such as RAM, etc to make use of them.
2. It is expensive than the previous Microsoft operating systems.
3. Some of the users have problems such as; their system hangs after installing Windows 7
4. If the user has got an HP multifunction printer, and its driver being upgraded to the Windows 7, then the printer doesn’t response to the print commands. So, the user needs to go to the new HP solution Center to resolve this problem.
5. Windows have specific themes for United Kingdom, Germany, Canada, Japan, South Africa and Australia, if the user is not from the above country and he wish to have a specific theme of his country, he will not get that, hence the user will not satisfied with that feature.
6. Some of the features like Start Menu user interface, Windows Ultimate Extras, InkBall, Windows Photo Gallery, Windows Movie Maker, Windows Calendar Windows Mail called Windows Live Essentials were included in Vista are removed in Windows 7.

Read More

MP3 Cutter

Easy to Use - Cut MP3 music to pieces in few clicks.
40+ Formats Supported - MP3 Cutter supports more than 40 popular audio & video formats
Audio Converter - Convert audio files between MP3 and other formats.
Audio Extractor - Extract music from video files to MP3 forma
Ringtone Maker - Make ringtones from any audio or video files





click to download:http://www.mp3cutter.org/

Read More

Differences between Exchange Server 2003 and Exchange Server 2007

Implementing Exchange Server 2007 for coexistence with Exchange Server 2003

How Exchange Server 2007 can coexist with Exchange Server 2003 and their main differences.

Differences between Exchange Server 2003 and Exchange Server 2007
Let us start by explaining the key differences between Exchange Server 2003 and Exchange

Server 2007, especially for coexistence:

Administrative Groups
Routing Groups
Server Roles

It is possible to install Exchange Server 2007 into an existing Exchange Server 2003 organization that is operating in Exchange native mode. The existing Exchange organization can contain Exchange 2003 servers, and Exchange 2000 servers.
There are many differences between Exchange Server 2007 and Exchange Server 2003. To explain these differences and how the different features can coexist is the main focus of this article.

Understanding Coexistence between Exchange Server 2003 and Exchange Server 2007
Depending on the size of the Exchange Organization in which you are performing a migration to Exchange Server 2007, the migration can consume a lot of time so both versions have to coexist for a time. Second, it is not possible to directly migrate Exchange Server 2003 to Exchange Server 2007. You have to install an additional Exchange Server 2007 into the existing Exchange Server 2003 organization.

Successful coexistence of Exchange 2007 with Exchange Server 2003
Exchange 2003 Server depends on the correct configuration of routing group connectors between Exchange 2007 Hub Transport servers and Exchange Server 2003 Bridgehead servers. When you install Exchange 2007 in a Windows Server 2003 forest with an existing Exchange 2003 organization, you select to join Exchange 2007 to that Exchange 2003 organization.
During Exchange Server 2007 installation, you must specify an Exchange 2003 Bridgehead server in the routing group to which you want to create the initial Routing Group connector.
Because Exchange Server 2003 and Exchange Server 2007 use different Server to Server communication, you must configure routing group connectors to enable message transfer between these two Exchange versions. Exchange Server 2003 uses SMTP as the primary communication protocol between Exchange 2003 servers. Exchange Server 2007 uses RPC for Server to Server communication (like Exchange Server 5.5) and depends on the Hub Transport server role to perform SMTP to send and receive messages. It is no longer possible to use an Exchange Server 2007 organization without a Hub Transport Server because this Exchange Server role is responsible for message conversion and much more.


Administrative Group
Exchange Server 2003 uses administrative groups to delegate permissions to manage parts of the Exchange organization. Exchange 2007 does not use administrative groups as a logical management unit for administrative delegation (there is only one administrative group that all Exchange Server 2007 are members of, and the administrative group exists only for compatibility reasons with Exchange Server 2003).
To allow coexistence between Exchange Server 2003 and Exchange 2007, all Exchange 2007 servers are automatically installed in a single administrative group when Exchange 2007 is installed.
The Exchange Server 2007 administrative group is recognized in the Exchange System Manager of Exchange Server 2003 as Exchange administrative group (FYDIBOHF23SPDLT). The Microsoft Exchange Team had a wonderful idea when they created this name. Do you think the name sounds illogical? It is logical, decoded the administrative Group has the name EXCHANGE12ROCKS. The Exchange team used the well known Caesar cipher. Now you have to research how the name FYDIBOHF23SPDLT corresponds to EXCHANGE12ROCKS!

Administrative groups are not displayed in the Exchange 2007 Exchange Management Console but you can see the default administrative group with ADSIEDIT.




Utilities to manage Exchange Server 2003
You can use the Exchange tasks in Active Directory Users and Computers to manage Exchange Server 2003 mailboxes. In Exchange 2007, you must manage servers and mailboxes by using the Exchange Management Console or the Exchange Management Shell. The related management tasks to configure Exchange 2003 recipients have been moved to the EMS or EMC.



Figure 2: Exchange 2007 User and recipient management with EMC

Routing Groups
Exchange Server 2003 uses routing groups and routing group connectors to route messages between Exchange Servers in different routing groups. A routing group is defined as a boundary of physical sites and to establish a SMTP connection between these sites. Typically a routing group is used to group Exchange Servers which are connected through a high speed network link. Exchange Servers in the same routing group can communicate directly with each other without the use of routing group connectors and possible limitations on connector sites. Typically, there is a 1:1 relationship with Exchange routing groups and Active Directory sites. Exchange 2003 and Windows Administrators always had to configure and maintain two site concepts – Exchange Routing Groups and Active Directory sites.
Exchange Server 2007 uses the existing Active Directory site topology to define the Routing topology. Exchange 2007 Servers that exist in the same Active Directory site can communicate with each other without the use of connectors. E-Mail that must be delivered to Exchange Servers in other Active Directory sites will be transmitted to Hub Transport Servers. The Hub Transport Server is then responsible for transmitting the message to the destination Hub Transport server in the other Active Directory site. Exchange Server 2007 automatically creates these connectors between the Active Directory sites but it is possible to manually configure the routing topology. You can’t see these connectors in the Exchange Management Console.
In the case of coexistence, all of Exchange Server 2007 will be installed in a single Routing Group that is used for coexistence with Exchange Server 2003.
The default Exchange 2007 routing group is displayed in Exchange 2003 System Manager as Exchange Routing Group (DWBGZMFD01QNBJR) within the Exchange Administrative Group (FYDIBOHF23SPDLT) – think again that the Caesar cipher is used here to create the name of the Routing Group.
When the first Exchange 2007 Hub Transport server is installed into an existing Exchange 2003 organization, you must select an Exchange 2003 bridgehead server to which the routing group connector should establish a connection.
The Hub Transport Server from Exchange Server 2007 and the remote Bridgehead server from Exchange Server 2003 are automatically configured with a routing group connector that connects both routing groups. The Exchange Server 2003 Bridgehead Server is automatically added as a member of the Legacy Interop Universal Security Group. This group has the permission to send and receive e-mail through Exchange Server 2007.
You must use the Exchange Management Shell (EMS) with the New-RoutingGroupConnector cmdlet to create additional Routing Group connectors on the Exchange Server 2007 Hub Transport Servers. Please note that Exchange Server 2007 and Exchange Server 2003 cannot exist in the same routing group.


Important: 
If you install Exchange 2007 to build a new Exchange organization and not to install into an existing Exchange 2003 Organization you cannot install Exchange 2003 in the Exchange 2007 organization.

Link State Routing
Exchange 2003 servers use Link State Routing to exchange routing table entries for the path that messages will take through the exchange organization. A routing group master collects information about the status of other Exchange Servers and creates a small table in memory, the Link State Table (LST). The LST is then distributed to other Exchange Servers and will be updated at fixed intervals. Based on the Information about the status of other Exchange servers, a lost connection to another Exchange Server will be saved in the LST and Exchange tries to route the message over another Exchange server to the destination.
Link state routing is not used by Exchange 2007 Hub Transport servers and Exchange 2007 can't propagate link state updates. When a Hub Transport server sends an e-mail to another Active Directory site where a Hub Transport server cannot be contacted, the Hub Transport server does not recalculate the route. Hub Transport servers always try to communicate directly with other Hub Transport servers.
If there is more than one Hub Transport Server in a site, messaging traffic is automatically load balanced and the sending Hub Transport Server tries to reach each Hub Transport Server in the destination site before the connection fails.
When the connection to the destination site is unavailable, Exchange Server 2007 uses the associated site link costs to an Active Directory site to deternmine the closest site to send the mail to. This behavior is known as queue at point of failure.
If multiple routing paths exist between the default Exchange 2007 Routing Group and any Exchange Server 2003 routing group, Link State updates must be suppressed to ensure that no message loops occur when a route is recalculated. Microsoft recommends suppressing Link State updates if multiple connections exist between Exchange Server 2007 and 2003. It is possible to disable Link State updates through a registry patch. Configuration changes such adding a connector in the Exchange organization is still propagated by using the Link State information.

Send Connectors and Receive Connectors
Exchange Server 2003 uses Virtual SMTP Servers to send and receive messages. An SMTP connector is logically bound to an SMTP Virtual Server.
Exchange Server 2007 doesn’t use SMTP Virtual Servers. Instead Exchange Server 2007 uses the new Hub Transport Server role.
The Exchange 2007 Hub Transport servers provide SMTP transport for the organization. Hub Transport servers use an automatically created connector to route messages between Active Directory sites. You cannot see these connectors in the Exchange Management Console. The connector is called an intra-organization Send connector.
The Exchange Server 2007 setup creates an SMTP receive connector to receive SMTP messages from any sender on Port 25. The Exchange Server 2007 setup process also creates a second connector to receive SMTP traffic from non MAPI clients. This connector listens on Port 587.
If you want to enable your Exchange organization to send e-mail through the Internet you must create an SMTP Send connector to route e-mail to the Internet. If your organization is large, you should implement an Edge Transport Server in the perimeter network. An Exchange Edge Transport Server is a secured, hardened and reduced functionality version of Exchange Server 2007. The SMTP Send connector on the Hub Transport Server should point to the Edge Transport Server.

Message Tracking
Message Tracking is the process of archiving the path messages have taken when they reached or left the Exchange organization. With the help of message tracking you will easily find which routes the message passed.
The message tracking feature in Exchange 2007 is different from the message tracking feature in Exchange Server 2003. The events that are logged by Exchange 2007 message tracking do not correspond directly to the message tracking events that are logged by Exchange Server 2003.
Messages that are sent and received by Exchange 2007 can only be tracked by Exchange 2007 servers. You cannot use the message tracking feature of Exchange Server 2003, because Exchange Server 2007 doesn’t support WMI for this function.
If your Exchange organization is in mixed mode with Exchange Server 2003 and 2007, you have to use the message tracking feature of Exchange Server 2007 to track messages in Exchange Server 2007. If this message is transmitted to Exchange Server 2003, you have to use the message tracking feature in Exchange Server 2003.

Mailbox Server Coexistence
The Mailbox server role can coexist with Exchange Server 2003 and Exchange Server 2007. Exchange 2007 uses the Hub Transport server to send and receive mail. A Hub Transport server must be installed in every Active Directory site that contains an Exchange 2007 Mailbox server. It is possible to move mailboxes between Exchange Server 2003 and Exchange Server 2007.

Client Access Server Coexistence
The Client Access server (CAS) role in Exchange Server 2007 has the same (and more) functionality as a front-end server in Exchange 2003. You must deploy the Client Access Server role if you have e-mail clients that access Exchange by using Microsoft Outlook Web Access (OWA), POP3, IMAP4, or mobile devices with Exchange Active Sync (EAS). The Client Access Server role from Exchange Server 2007 can coexist with Exchange Server 2003 but the right combination of Exchange Server 2003 / 2007 and Exchange 2003 Front End Server and Exchange Server 2007 Client Access Server role is important for which version of Outlook Web Access clients will see. If the user’s mailbox is located on an Exchange Server 2003 Backend server and the Client Access Server is running Exchange 2007, the user will have access to the Exchange Server 2003 version of Outlook Web Access. Only if you use the Exchange Server 2007 version on both Backend Server (Mailbox Server role) and Client Access Server role, users will participate from the new Outlook Web Access version of Exchange Server 2007.

Different URLs to use OWA (Outlook Web Access)
The Outlook Web Access URL that users have to use also depends on the location of the user’s mailbox. If the mailbox is located on an Exchange 2003 back-end server you must use the URL http://<servername>/Exchange.
If the mailbox is located on an Exchange 2007 Mailbox server, you can use http://<servername>/owa or http://<servername>/Exchange.



Figure 3: OWA and Exchange Virtual Directory in Exchange Server 2007

Edge Transport Server coexistence
The Exchange Server 2007 Edge Transport Server role is new in Exchange Server 2007 but this role is not exclusive to Exchange Server 2007. You can use a server with the Edge Transport server role as a smarthost in an Exchange Server 2003 environment with some limitations. One of the most important limitations is that you cannot use the Exchange Server 2007 Edge Subscription to synchronize recipient lists, or safelist senders from Outlook.

Conclusion
There are many more differences between Exchange Server 2003 and Exchange Server 2007. Exchange Server 2007 has many more new and improved features compared to Exchange Server 2003 but I hope that I successfully explained the key differences between the both and how to establish a coexistence between them.

Read More