Windows Server 2003

1. WINDOWS SERVER 2003 2. Windows Server 2003 different Versions 3. Hardware requirement for Windows Server 2003 4. HCL - Hardware Compatibility List 5. Keep following points in mind before Upgrade Migrate 6. Upgrade from previous OS 7. WINDOWS SERVER 2003 INSTALLATION 8. Windows Server 2003 Activation 9. MANAGING LICENSING 10. Administrating License Logging Services 11. Managing Software Installation and Maintenance 12. Essential Administration Tools 13. Difference between RAID & WINDOW BACKUP 14. RAID Redundant Array of Inexpensive DISK 15. Disk Mirroring & Disk Duplexing 16. Disk partition and File System FAT, FAT32, NTFS 17. Remote Desktop for Administration & Terminal services 19. To connect to Remote Desktop Pc from Client PC do as follow 20. Remote Assistance 21. Difference between RAID & WINDOW BACKUP 22. SYSTEM STATE DATA 23. IP-ADDRESSING and IPV4 24. IPV6 [Internet Protocol Version 6] 25. Signed & Unsigned Driver 26. Hardware Profile 27. CHKDSK.EXE (Check Disk) 28. Disk Defragmenter(DFRG.MSC) 29. Introduction to AD [Active Directory] 30. Difference between WORKGROUP & DOMAIN 31. Operating System that support Active Directory 32. FSMO [Flexible Single Master Operation] 33. GC (GLOBAL CATALOG) Server 34. Site 35. Disk Defragmenter (DFRG.MSC) 36. AD replication 37. AUTHORITATIVE Restore 38. TOOLS to Troubleshoot Active Directory Installation 39. Understanding USER, GROUP & COMPUTER 40.GROUP ACCOUNTS 41. User Profile 42. Roaming User Profile 43. Mandatory User Profile 44. Attrib (Attribute) 45. Taking Ownership 46. Copying and Moving Files and Folders 47. Server Roles for WINDOWS SERVER 2003 48. AVAILABILITY & SECURITY 49. General Server Security Issues 50. OSI MODEL 51. Data Encapsulation 52. TCP/IP or DoD Model 53. Protocol Working at Host to Host (Transport) layer 54. NETWORK MONITOR 55. Internet Information Services 55. Monitoring Tools 54. DNS [Domain Name System] 55. DNS ZONE 56. Remote Access Authentication Process 57. Remote Access
Pr.Pg Next Pg

Remote Access Authentication Process tutorails

  • When you connect to the Internet, remote access authentication is a one-step process. Your computer presents credentials, typically a user name and password, that are acceptable to a remote access server at the Internet Service Provider(ISP), and you are granted a connection to the Internet.

  • When you connect to a corporate network that uses a Windows domain, a similar remote access authentication occurs. But in this case, a second step of authentication is required. After you have connected to the network, resources that you access, such as file and print servers, will ask your computer for its domain credentials on each attempt to access them. These domain network credentials may not be the same as the credentials required by the remote access server.


Password Authentication Protocol (PAP)

  • Password Authentication Protocol (PAP) is a simple authentication protocol in which the user name and password is sent to the remote access server in a plaintext (unencrypted) form. Using PAP is strongly discouraged because your passwords are easily readable from the Point-to-Point Protocol (PPP) packets exchanged during the authentication process. PAP is typically only used when connecting to older UNIX-based remote access servers that do not support any additional authentication protocols.


CHAP (Challenge Handshake Authentication Protocol)

  • An authentication protocol used by Microsoft remote access and Network Connections. Using CHAP, a remote access client can send its authentication credentials to a remote access server in a secure form. Microsoft has created a Windows-specific variant of CHAP called MS-CHAP.


Microsoft Challenge Handshake Authentication Protocol (MS-CHAP)

  • Microsoft created MS-CHAP to authenticate remote Windows workstations, providing the functionality to which LAN-based users are accustomed while integrating the hashing algorithms used on Windows networks. Like CHAP, MS-CHAP uses a challenge-response mechanism to keep the password from being sent during the authentication process.

  • MS-CHAP uses the Message Digest 4 (MD4) hashing algorithm and the Data Encryption Standard (DES) encryption algorithm to generate the challenge and response and provides mechanisms for reporting connection errors and for changing the user's password


Microsoft Challenge Handshake Authentication

  • Windows XP supports Microsoft Challenge Handshake Authentication Protocol version 2 (MS-CHAP v2). MS-CHAP v2 provides mutual authentication, the generation of stronger initial data encryption keys for Microsoft Point-to-Point Encryption (MPPE), and different encryption keys for sent and received data. To minimize the risk of password compromise during a password change, support for older methods of the MS-CHAP password change are not supported.

  • Because MS-CHAP v2 is more secure than MS-CHAP, it is offered before MS-CHAP (if enabled) for all connections.

  • MS-CHAP v2 is supported by computers running Windows XP, Windows 2000, Windows 98, Windows Millennium Edition, and Windows NT 4.0. For computers running Windows 95, MS-CHAP v2 is only supported for VPN connections, not for dial-up connections.


Extensible Authentication Protocol (EAP)

  • The Extensible Authentication Protocol (EAP) is an extension to the Point-to-Point Protocol (PPP) that allows arbitrary authentication methods using credential and information exchanges of arbitrary lengths. EAP was developed in response to an increasing demand for authentication methods that uses other security devices and provides an industry-standard architecture for support of additional authentication methods within PPP. EAP is used while using SMART CARD & CERTIFICATES


Shiva Password Authentication Protocol (SPAP)

  • The Shiva Password Authentication Protocol (SPAP) is a simple encrypted password authentication protocol supported by Shiva remote access servers. With SPAP, the remote access client sends an encrypted password to the remote access server. SPAP uses a two-way encryption algorithm. The remote access server decrypts the password and uses the plaintext form to authenticate the remote access client.


Pr.Pg border                                              Next Pg