Wednesday, January 28, 2009
Happy Republic Day
1618 Languages
6400 Castes
6 Ethic Groups
29 Major Festivals
&
1 Country
Name: INDIA
Proud to be an INDIAN.
HAPPY REPUBLIC DAY.
Monday, January 5, 2009
Understanding Event Viewer
Understanding Event Viewer
Using the event logs in Event Viewer, you can gather information about hardware, software, and system problems. You can also monitor Windows XP security events.
A computer running any version of Windows XP records events in three kinds of logs:
The application log contains events logged by applications or programs. For example, a database program might record a file error in the application log. Program developers decide which events to monitor.
The security log records events such as valid and invalid logon attempts, as well as events related to resource use such as creating, opening, or deleting files or other objects. An administrator can specify what events are recorded in the security log. For example, if you have enabled logon auditing, attempts to log on to the system are recorded in the security log.
The system log contains events logged by Windows XP system components. For example, the failure of a driver or other system component to load during startup is recorded in the system log. The event types logged by system components are predetermined by Windows XP.
A computer running Windows configured as a domain controller records events in two additional logs:
The directory service log contains events logged by the Windows directory service. For example, connection problems between the server and the global catalog are recorded in the directory service log.
The File Replication service log contains events logged by the Windows File Replication service. For example, file replication failures and events that occur while domain controllers are being updated with information about sysvol changes are recorded in the file replication log.
A computer running Windows configured as a Domain Name System (DNS) server records events in an additional log:
The DNS server log contains events logged by the Windows DNS service. Events associated with resolving DNS names to Internet Protocol (IP) addresses are recorded in this log.
Event Viewer displays these types of events:
A significant problem, such as loss of data or loss of functionality. For example, if a service fails to load during startup, an Error event will be logged.
An event that is not necessarily significant, but may indicate a possible future problem. For example, when disk space is low, a Warning event will be logged.
An event that describes the successful operation of an application, driver, or service. For example, when a network driver loads successfully, an Information event will be logged.
An audited security access attempt that succeeds. For example, a user's successful attempt to log on to the system will be logged as a Success Audit event.
An audited security access attempt that fails. For example, if a user tries to access a network drive and fails, the attempt will be logged as a Failure Audit event.
The Event Log service starts automatically when you start Windows. All users can view application and system logs. Only administrators can gain access to security logs.
By default, security logging is turned off. You can use Group Policy to enable security logging. The administrator can also set auditing policies in the registry that cause the system to halt when the security log is full.
Microsoft Certification Program
Microsoft Certification Program
Microsoft Certified Professional (MCP , 1 EXAM)
Microsoft Certified Systems Administrator (MCSA,3EXAM)
Microsoft Certified Systems Engineer (MCSE,3EXAM)
Microsoft Certified Systems Engineer With specialization (1EXAM)
How to earn your MCSE on Windows Server 2003
To earn your MCSE on Windows Server 2003 certification, you must pass seven exams:
1 Four core exams on networking systems
2 One core exam on client operating systems
3 One core design exam
4 One elective exam
Related job titles: systems engineer, network engineer, systems analyst, network analyst, or technical consultant.
Core exams on networking systems (all 4 are required)
Exam 70-290: Managing and Maintaining a Windows Server 2003 Environment.
Exam 70-291: Implementing, Managing, and Maintaining a Windows Server 2003 Network Infrastructure.
Exam 70-293: Planning and Maintaining a Windows Server 2003 Network Infrastructure.
Exam 70-294: Planning, Implementing, and Maintaining a Windows Server 2003 Active Directory Infrastructure.
Core exams on client operating systems (choose one)
Exam 70-6206: TS: Windows Vista, Configuring .
Exam 70-270: Installing, Configuring, and Administering Windows XP Professional.
Exam 70-2101,2 : Installing, Configuring, and Administering Microsoft Windows 2000 Professional.
Core design exams (choose one)
Exam 70-2973: Designing a Windows Server 2003 Active Directory and Network Infrastructure
Exam 70-2983: Designing Security for a Windows Server 2003 Network
Elective exams (choose one)
Exam 70-299: Implementing and Administering Security in a Windows Server 2003 Network
How to earn your MCSE: Messaging on Windows Server 2003
To earn your MCSE: Messaging on Windows Server 2003 certification, you must pass eight exams:
1 Four core exams on networking systems (same as MCSE)
2 One core exam on client operating systems (same as MCSE)
3 One design exam (same as MCSE)
4 Two messaging specialization exams
Messaging exams (both are required)
Exam 70-2844: Implementing and Managing Microsoft Exchange Server 2003
Exam 70-2854: Designing a Microsoft Exchange Server 2003 Organization
How to earn the MCSE: Security on Windows Server 2003
To earn your MCSE: Security on Windows Server 2003 certification, you must pass eight exams:
1 Four core exams on networking systems (same as MCSE)
2 One core exam on client operating systems (same as MCSE)
3 One security design exam (same as MCSE)
4 Two security specialization exams
Security specialization exams (choose two)
Exam 70-299: Implementing and Administering Security in a Windows Server 2003 Network
Exam 70-2272: Installing, Configuring, and Administering Microsoft Internet Security and Acceleration (ISA) Server 2000, Enterprise Edition
Exam 70-350: Implementing Microsoft Internet Security and Acceleration (ISA) Server 2004
Exam 70-351: TS: Microsoft Internet Security and Acceleration (ISA) Server 2006, Configuring
Difference between seeders, peers and leechers ?
A seeder is a peer that has a complete copy of the torrent and still offers it for upload. The more seeders there are, the better the chances are for completion of the file.
Seeders (Uploaders):- The one who are Seeding torrents
Peer
A peer is one instance of a BitTorrent client running on a computer on the Internet to which other clients connect and transfer data. Usually a peer does not have the complete file, but only parts of it. However, in the colloquial definition, "peer" can be used to refer to any participant in the swarm (in this case, it's synonymous with "client").
Leech
A leech is usually a peer who has a negative effect on the swarm by having a very poor share ratio - in other words, downloading much more than they upload. Most leeches are users on asymmetric internet connections and do not leave their BitTorrent client open to seed the file after their download has completed. However, some leeches intentionally avoid uploading by using modified clients or excessively limiting their upload speed. The term leech, however, can be used simply to describe a peer - or any client that does not have 100% of the data.
Leechers (Downloader):- The one who are leeching from Seeders.
What is That which we saw peers 50(120) ?
It means, Total of 120peers & you are connected to 50 of them.