Download - Ebooks - Rapidshare - Music

My Note

2010-01-16T09:31:00.003+07:00

http://hotfile.com/dl/27881686/9c0389d/Presenting_for_Success.part1.rar.html
http://hotfile.com/dl/27881753/d1bdbb7/Presenting_for_Success.part2.rar.html
http://hotfile.com/dl/27881816/ca6a86e/Presenting_for_Success.part3.rar.html
http://hotfile.com/dl/27881840/b6a38cc/Presenting_for_Success.part4.rar.html

http://hotfile.com/dl/20149099/aaacdc6/Study.3nglish.I3LTS.Pre.Series1_2.part01.rar.html
http://hotfile.com/dl/20149237/49d671d/Study.3nglish.I3LTS.Pre.Series1_2.part02.rar.html
http://hotfile.com/dl/20149248/0602586/Study.3nglish.I3LTS.Pre.Series1_2.part03.rar.html
http://hotfile.com/dl/20149424/d2e6fec/Study.3nglish.I3LTS.Pre.Series1_2.part04.rar.html
http://hotfile.com/dl/20149430/25121cb/Study.3nglish.I3LTS.Pre.Series1_2.part05.rar.html
http://hotfile.com/dl/20149714/131adda/Study.3nglish.I3LTS.Pre.Series1_2.part06.rar.html
http://hotfile.com/dl/20149716/888c2c7/Study.3nglish.I3LTS.Pre.Series1_2.part07.rar.html
http://hotfile.com/dl/20149951/b18f7e7/Study.3nglish.I3LTS.Pre.Series1_2.part08.rar.html
http://hotfile.com/dl/20149958/0841737/Study.3nglish.I3LTS.Pre.Series1_2.part09.rar.html
http://hotfile.com/dl/20150165/ea235e6/Study.3nglish.I3LTS.Pre.Series1_2.part10.rar.html
http://hotfile.com/dl/20150168/e55fb14/Study.3nglish.I3LTS.Pre.Series1_2.part11.rar.html
http://hotfile.com/dl/20150336/6dba34b/Study.3nglish.I3LTS.Pre.Series1_2.part12.rar.html
http://hotfile.com/dl/20150351/d4d7339/Study.3nglish.I3LTS.Pre.Series1_2.part13.rar.html
http://hotfile.com/dl/20150499/3f260b9/Study.3nglish.I3LTS.Pre.Series1_2.part14.rar.html
http://hotfile.com/dl/20150526/d95ab69/Study.3nglish.I3LTS.Pre.Series1_2.part15.rar.html
http://hotfile.com/dl/20150647/e5f921a/Study.3nglish.I3LTS.Pre.Series1_2.part16.rar.html
http://hotfile.com/dl/20150661/e015b5b/Study.3nglish.I3LTS.Pre.Series1_2.part17.rar.html
http://hotfile.com/dl/20150885/6bb6baf/Study.3nglish.I3LTS.Pre.Series1_2.part18.rar.html
http://hotfile.com/dl/20150894/dd3aff5/Study.3nglish.I3LTS.Pre.Series1_2.part19.rar.html
http://hotfile.com/dl/20151037/b8d6c47/Study.3nglish.I3LTS.Pre.Series1_2.part20.rar.html
http://hotfile.com/dl/20151042/66346b4/Study.3nglish.I3LTS.Pre.Series1_2.part21.rar.html
http://hotfile.com/dl/20151256/d5f2c53/Study.3nglish.I3LTS.Pre.Series1_2.part22.rar.html
http://hotfile.com/dl/20151262/ca1e5e3/Study.3nglish.I3LTS.Pre.Series1_2.part23.rar.html
http://hotfile.com/dl/20151413/92e281e/Study.3nglish.I3LTS.Pre.Series1_2.part24.rar.html
http://hotfile.com/dl/20151442/ba37c1d/Study.3nglish.I3LTS.Pre.Series1_2.part25.rar.html
http://hotfile.com/dl/20151555/7b7cbb3/Study.3nglish.I3LTS.Pre.Series1_2.part26.rar.html
http://hotfile.com/dl/20151566/0134140/Study.3nglish.I3LTS.Pre.Series1_2.part27.rar.html
http://hotfile.com/dl/20151671/6367ba7/Study.3nglish.I3LTS.Pre.Series1_2.part28.rar.html
http://hotfile.com/dl/20151716/5b58e59/Study.3nglish.I3LTS.Pre.Series1_2.part29.rar.html
http://hotfile.com/dl/20149098/65ee94b/Study.3nglish.I3LTS.Pre.Series1_2.part30.rar.html

LinuxCBT Samba Edition

2009-06-10T16:01:00.001+07:00

Price: $295 for Single-Computer License - licensing details
5-Computer License: $695
Duration: 13 hours/50 Videos on 1-DVD
Content Size: 714MB (748,496,896 bytes)

LinuxCBT Samba Edition - Disc 1

* Introduction to Samba & Clients
o Explore Samba server configuration
o Identify key Samba packages & contents
o Explore the SMB workgroup implementation
o Discuss the roles of Local Master Browsers (LMBs) & Domain Master Browsers (DMBs)
o Use findsmb & smbclient to reveal the active browse lists
o Discuss NETBIOS naming rules
o Identify system broadcast address & discuss broadcast-based NETBIOS name resolution
o Identify & discuss the roles of the key Samba daemons
o Use smbtree to enumerate the active workgroups, hosts & file & print shares
o Install rdesktop client for remote desktop connectivity to Windows 2003 Server
o Explore browse list & SMB clients from Windows 2003
o Share file resource on Windows 2003 Server for use by Samba clients
o Join common workgroup from Windows 2003 host
o Use smbclient to enumerate & connect to shared resources on XP/2003 hosts
o Explore anonymous and authenticated share enumeration using smbclient
o Transfer files between Samba and Windows 2003 hosts using smbclient
o Use smbget to download files non-interactively from remote SMB server
o Use smbclient with credentials stored in a hidden file
o Create tarball archive using tar & discuss Samba's smbtar utility
o Create tar-compatible archives of remote SMB-share using smbtar
*
* Samba File System (SMBFS) Integration
o Discuss the features & benefits of SMBFS
o Identify package & files
o Create temporary mount point for remote SMB share
o Mount remote SMB share into local Linux file system using SMBFS
o Examine resultant Linux file-system permissions post SMBFS mount
o Transfer files to mount point (Remote Windows 2003 system) & examine results
o Identify SMBFS process footprint
o Mount remote SMB share with previously-defined hidden credentials file
o Modify system startup file to facillitate automatic SMBFS mounts upon system restart
*
* Workgroup & Windows Internet Naming System (WINS) Integration
o Identify key Samba configuration file & package membership
o Use findsmb to reveal available workgroups
o Alter Samba configuration file to join available workgroup
o Identify key TCP/UDP ports used by key Samba daemons
o Use findsmb & browse list to confirm workgroup membership
o Enumerate default Samba shares on primary Linux system using smbclient
o Introduction to smbpasswd utility and database
o Use smbpasswd to add Windows user to database & confirm authentication from Windows host
o Install WINS Server on Windows 2003 Server for use by SMB-clients
o Explain default Samba NETBIOS name resolution order
o Identify name resolution order directive in primary Samba configuration file
o Configure Samba server to be a WINS client via Samba configuration file
o Confirm WINS NETBIOS registrations of Samba & Windows hosts
*
* Samba Share-Level File & Print Security Implementation
o Discuss Samba's security modes
o Discuss the features & benefits of share-level security
o Alter primary Samba configuration file to support share-level security
o Define and publish a public read-only share
o Reload key Samba daemons & confirm connectivity to read-only share
o Enumerate & connect to public read-only share from a remote Samba client
o Define & publish an anonymous read-write share
o Use chmod & chown to define appropriate permissions and ownership on the directory
o Confirm the ability to write to read-write share from remote Windows 2003 system
o Examine applied permissions & ownership of created objects on the Linux file system
o Define & publish a private read-write share
o Confirm authentication to private read-write share from remote Windows 2003 host
o Update Samba back-end database to reflect new user - test connectivity
o Compare & contrast Windows & Samba hidden share definition
o Define hidden share & explore browse list from Samba & Windows hosts
o Convert existing shares to hidden shares and examine updated browse list
o Discuss default Samba print sharing implementation
o Explore Common UNIX Printing System (CUPS) interface
o Install and configure a printer
o Discuss various CUPS back-end capabilities
o Discuss the CUPS-generated printcap file
o Explore key Samba print-related configuration directives
o Share the printer using Samba
o Connect to printer from Windows host and test printing
*
* Samba Web Administration Tool (SWAT)
o Discuss the features & benefits of Samba SWAT
o Explore XINETD system configuration for the presence of Samba SWAT
o Install Samba SWAT from the local package repository
o Update XINETD configuration to enable Samba SWAT & confirm TCP listener
o Authenticate to Samba SWAT as non-privileged and privileged users
o Examine current smbd & nmbd connections
o Explore & discuss the key tools included with Samba
o Correlate Samba's primary configuration file to Samba SWAT's web interface
o Discuss the key directives in the global section of the Samba SWAT web interface
o Discuss additional directives in the advanced view of the Samba SWAT global area
o Adjust the OS Level and examine the changes to the role in the browse list
o Discuss Samba WINS server rules & limitations
o Explore shares configuration
o Correlate shares section of main config file to Samba SWAT's shares interface
o Discuss the effects of various share directives
o Discuss the variable homes share and its applications
o Explain Samba's create mask directive & examine its application
o Examine the advanced Samba SWAT shares view & discuss key directives
o Define valid & invalid users per share & test connectivity from remote Windows host
o Force ownership of file & directory objects using the force user directive
o Explore & discuss advanced printer share directives
o Define multiple NETBIOS names and view results in the browse list
*
* Samba User-Level Security Mode
o Explain the advantages and features of user-level security
o Discuss the user-accounts back-ends supported by Samba
o Convert Samba from share-level to user-level security mode
o Test user-level connectivity to Samba shares/services
o Discuss IPC$ connections and applications
o Explore passwd & shadow user-accounts databases
o Explore the smbpasswd database
*
* Samba - Active Directory (AD) - BIND Integration
o Discuss the DNS requirements of Active Directory
o Install BIND from RPM repository
o Configure BIND as a caching-only name server
o Define usable BIND named.conf configuration file with appropriate zones
o
o Define required Active Directory dynamically updateable zones
o Install Active Directory on Windows server
o Confirm BIND DNS connectivity
o Configure Kerberos to support Active Directory Realm & test connectivity
o Convert Samba from basic user-level to ADS security mode
o Use the net command to create Samba machine account in the Active Directory
o Confirm authentication against Active Directory when accessing resources
o Create AD -> Linux corresponding users for transparent access
*
* Samba - Winbindd
o Discuss the features & advantages of Winbind
o Discuss the accounts resolutions process
o Alter the name server switch process to facilitate winbind
o Discuss UNIX/Linux uids & gids
o Explain the application of idmaps - uids & gids
o Configure Samba to use Winbind
o Enumerate remote Active Directory users using wbinfo & getent
o Examine auto-assigned uids & gids via idmap
o Connect to Samba server using Active Directory users & Winbind
o Configure SSHD to support Winbind-provided users from Active Directory
o Configure Winbind to use the default Active Directory domain for authentication
o Configure VSFTPD to use the default Active Directory domain for authentication
*
* Samba - Linux File System & Share/Service Permissions
o Explain how Samba interacts with file-system permissions
o Explain UNIX/Linux file-system permissions - UGO
o Use chown/chmod to adjust file-system permissions
o Discuss the applicable Samba share/service permissions directives
o Apply various share/service permissions & test results
*
* Samba - Miscellaneous
o Create share/service with appropriate permissions for collaborations
o Examine collaborative permission from Windows client
o Configure Samba as a WINS server & discuss capabilities
o Configure Samba a print server for SMB(Windows/Linux/UNIX) clients
o Explore Samba logging
o Mount remote CIFS shares into the Linux file system
o Share mounted CIFS directories using Samba

http://rapidshare.com/files/242900747/LinuxCBT.Samba.Edition.7z.001
http://rapidshare.com/files/242897182/LinuxCBT.Samba.Edition.7z.002
http://rapidshare.com/files/242897189/LinuxCBT.Samba.Edition.7z.003
http://rapidshare.com/files/242901042/LinuxCBT.Samba.Edition.7z.004
http://rapidshare.com/files/242901036/LinuxCBT.Samba.Edition.7z.005
http://rapidshare.com/files/242903378/LinuxCBT.Samba.Edition.7z.006
http://rapidshare.com/files/242900104/LinuxCBT.Samba.Edition.7z.007

LinuxCBT OpenLDAP Edition

2009-06-09T17:17:00.000+07:00

LinuxCBT OpenLDAP Edition | 762 MB
Price: $195 | 15 hours on 1-DVD

LinuxCBT feat. OpenLDAP Edition focuses on the common Linux | Unix directory services application: OpenLDAP. It is a module of LinuxCBT Directory Services Edition.

OpenLDAP provides a lightweight, central information directory service for countless applications, including general user authentication services. This results in reduced administrative overhead. OpenLDAP also supports replication and encryption, promoting high-availability and security. Furthermore, knowledge of OpenLDAP prepares you to work comfortably with Open Source and commercial LDAP variants.

Let LinuxCBT feat. OpenLDAP Edition cost-effectively teach you Linux | Unix directory skills.

Recommended Prerequisites for:

- Any LinuxCBT Operating System Course (Classic/EL-4|5/SUSE/Debian Editions)
- Open mind & determination to master Linux and related open-source applications
- Access to a Linux or Solaris system to follow the exercises

http://rapidshare.com/files/241919473/d-lcldap.iso.001
http://rapidshare.com/files/241919456/d-lcldap.iso.002
http://rapidshare.com/files/241919468/d-lcldap.iso.003
http://rapidshare.com/files/241921538/d-lcldap.iso.004
http://rapidshare.com/files/241928919/d-lcldap.iso.005
http://rapidshare.com/files/241928902/d-lcldap.iso.006
http://rapidshare.com/files/241928903/d-lcldap.iso.007
http://rapidshare.com/files/241928917/d-lcldap.iso.008
http://rapidshare.com/files/241934260/d-lcldap.iso.009
http://rapidshare.com/files/241934253/d-lcldap.iso.010
http://rapidshare.com/files/241934266/d-lcldap.iso.011
http://rapidshare.com/files/241916059/d-lcldap.iso.012

Linux CBT Mail Edition Video Trainning

2009-02-28T18:59:00.003+07:00

LinuxCBT Mail Edition focuses on the 3 leading Mail Transfer Agents (MTAs) and ancillary components:

Sendmail - LinuxCBT Sendmail Edition
Postfix - LinuxCBT Postfix Edition
qmail - LinuxCBT qmail Edition.

Linux/UNIX systems are responsible for moving the overwhelming majority of electronic mail across private and public networks. Consequently, savvy Systems Admins. are expected to have a solid foundation in MTAs and ancillary components for general and automated mail-based applications.

Let LinuxCBT Mail Edition help to solidify your understanding of key MTAs and ancillary components.

Recommended Prerequisites:

Familiarity with electronic mail concepts (MUA/MTA/etc.)
Access to a GNU/Linux-based PC to install the MTAs and ancillary components used

Disc 1
http://rapidshare.com/files/203494098/LinuxCBTMailEditionCD1.part01.rar
http://rapidshare.com/files/203495235/LinuxCBTMailEditionCD1.part02.rar
http://rapidshare.com/files/203496385/LinuxCBTMailEditionCD1.part03.rar
http://rapidshare.com/files/203497389/LinuxCBTMailEditionCD1.part04.rar
http://rapidshare.com/files/203498416/LinuxCBTMailEditionCD1.part05.rar
http://rapidshare.com/files/203499556/LinuxCBTMailEditionCD1.part06.rar
http://rapidshare.com/files/203500670/LinuxCBTMailEditionCD1.part07.rar
http://rapidshare.com/files/203501748/LinuxCBTMailEditionCD1.part08.rar
http://rapidshare.com/files/203502850/LinuxCBTMailEditionCD1.part09.rar
http://rapidshare.com/files/203503446/LinuxCBTMailEditionCD1.part10.rar
Disc 2
http://rapidshare.com/files/203539374/LinuxCBTMailEditionCD2.part01.rar
http://rapidshare.com/files/203504752/LinuxCBTMailEditionCD2.part02.rar
http://rapidshare.com/files/203505970/LinuxCBTMailEditionCD2.part03.rar
http://rapidshare.com/files/203507251/LinuxCBTMailEditionCD2.part04.rar
http://rapidshare.com/files/203508526/LinuxCBTMailEditionCD2.part05.rar
http://rapidshare.com/files/203509709/LinuxCBTMailEditionCD2.part06.rar
http://rapidshare.com/files/203510875/LinuxCBTMailEditionCD2.part07.rar
http://rapidshare.com/files/203512194/LinuxCBTMailEditionCD2.part08.rar
http://rapidshare.com/files/203513311/LinuxCBTMailEditionCD2.part09.rar
http://rapidshare.com/files/203514550/LinuxCBTMailEditionCD2.part10.rar
http://rapidshare.com/files/203493050/LinuxCBTMailEditionCD2.part11.rar
Disc 3
http://rapidshare.com/files/204732180/LinuxCBTMailEditionCD3.part01.rar
http://rapidshare.com/files/204733559/LinuxCBTMailEditionCD3.part02.rar
http://rapidshare.com/files/204735065/LinuxCBTMailEditionCD3.part03.rar
http://rapidshare.com/files/204736490/LinuxCBTMailEditionCD3.part04.rar
http://rapidshare.com/files/204737951/LinuxCBTMailEditionCD3.part05.rar
http://rapidshare.com/files/204739368/LinuxCBTMailEditionCD3.part06.rar
http://rapidshare.com/files/206324883/LinuxCBTMailEditionCD3.part07.rar
http://rapidshare.com/files/204741086/LinuxCBTMailEditionCD3.part08.rar
http://rapidshare.com/files/204742725/LinuxCBTMailEditionCD3.part09.rar
http://rapidshare.com/files/204744466/LinuxCBTMailEditionCD3.part10.rar
http://rapidshare.com/files/204746064/LinuxCBTMailEditionCD3.part11.rar
http://rapidshare.com/files/204747547/LinuxCBTMailEditionCD3.part12.rar

How to troubleshoot Advanced Client Push Installation issues in Systems Management Server 2003

2008-10-17T17:50:00.002+07:00

View products that this article applies to.
Article ID : 925282
Last Review : November 27, 2007
Revision : 2.7
On This Page
SUMMARY
INTRODUCTION
MORE INFORMATION
Pre-installation phase
Troubleshooting pre-installation issues
Newly discovered client computers are not assigned to the current site
Advanced Client Push Installation is not enabled at the appropriate site
The SMS Client Configuration Manager cannot connect to the client Admin$ share or to the Remote Registry Service (IPC$)
The SMS Advanced Client Push Installation account is configured incorrectly or is missing or is locked out
The SMS Advanced Client Network Access Account is configured incorrectly or is missing or is locked out in a non-Active Directory environment
Installation phase
Troubleshooting installation issues
The SMS Advanced Client cannot access the installation file on the SMS site server
The SMS Advanced Client cannot access the management point during an upgrade
Clients that are deployed by using Capinst.exe are not installed successfully
BITS installation issues
XML file registration is unsuccessful
Post-installation phase
Troubleshooting post-installation issues
The SMS Advanced Client is installed successfully, but does not appear as installed or assigned
The SMS Advanced Client is installed successfully but it does not receive a site assignment
The SMS Advanced Client displays a site assignment but does not appear as installed
SMS Advanced Client does not receive a policy after installation
SMS Advanced Clients are not installed on secondary sites
Troubleshooting management point issues
Tools and procedures to help troubleshoot SMS Advanced Client installation issues
Use a CCR file to manually trigger the client installation
Use the SMS Administrator console to force a full reinstallation of the SMS Advanced Client
Use the Ccmclean.exe tool to remove the SMS 2003 Advanced Client
Gather the SMS server and the SMS Advanced Client log files for analysis
SUMMARY
This article describes how to troubleshoot Microsoft Systems Management Server (SMS) 2003 Advanced Client Installation issues when you use the SMS 2003 Advanced Client Push Installation method.

There are several issues that can occur when you deploy a SMS 2003 Advanced Client by using the Advanced Client Push Installation. This article describes the Advanced Client Push Installation process, some common issues and their solutions, and the tools and procedures for troubleshooting common issues.

Back to the top
INTRODUCTION
When you use the SMS 2003 Advanced Client Push Installation method to automatically install the SMS 2003 Advanced Client on computers in the SMS site, you may encounter one or more of the following issues:
• The SMS Advanced Client is not installed.
• The SMS Advanced Client is installed. However, it cannot obtain an automatic site assignment.
• The SMS Advanced Client is installed and assigned. However, it cannot communicate with the SMS site server.

Back to the top
MORE INFORMATION
In this article, the SMS Advanced Client Push Installation process is divided into three phases. Each phase has its own distinct set of issues.

Note Frequently asked questions and answers about SMS Advanced Client issues can be found in the SMS Client FAQ. To view the SMS Client FAQ, visit the following Microsoft Web site:
http://www.microsoft.com/technet/sms/2003/library/techfaq/tfaq03.mspx (http://www.microsoft.com/technet/sms/2003/library/techfaq/tfaq03.mspx)
• Pre-installation phase

The SMS Client Configuration Manager connects to the target client and verifies the client's operating system and client information. The client installation source files are copied, and then the Setup process downloads the SMS core components to the client computer.
• Installation phase

The SMS Advanced Client copies the installation files from the site server and then starts Setup.
• Post-installation phase

After the Setup program is complete, the SMS Advanced Client obtains a site assignment, sends the heartbeat discovery information to the SMS site server, and then contacts the default management point to retrieve the SMS Advanced Client policy.

Back to the top
Pre-installation phase
1. During the pre-installation phase, SMS discovers the client computer and then generates a client configuration request (CCR) file. The CCR file contains the client computer name and additional information.
2. The SMS Client Configuration Manager connects to the ADMIN$ share on the client. This is based on the information in the CCR file.
3. The Client Configuration Manager connects to the client registry and gathers information about the client. This process is displayed as a log entry in the Ccm.log as connecting to IPC$.
4. The SMS core component files, MobileClient.tcf and Ccmsetup.exe, are located in the SMS\bin\I386\ folder. These files are downloaded to the %windir%\System32\ccmsetup folder on the client computer.
5. The Client Configuration Manager verifies that the Ccmsetup service started successfully before disconnecting. The CCR file is added to the SMS\Inboxes\Ccrretry.box folder for verification that the installation succeeded. On a second verification pass, SMS determines that the SMS Agent Host is running, and then deletes the CCR file.
6. If the Client Configuration Manager encounters any errors during this process, the CCR file is renamed to the name of the target client computer and is put in the SMS\Inboxes\Ccrretry.box folder. The Client Configuration Manager checks for files in this inbox folder every 60 minutes and tries to reprocess them 168 times (7 days) before they are discarded. This information is logged in the Ccm.log.

Back to the top
Troubleshooting pre-installation issues
Newly discovered client computers are not assigned to the current site
This issue typically occurs when the SMS site boundaries are configured incorrectly, or the site boundaries do not align with the type of discovery data that has been gathered. If this is the case, no CCR files are created for the client computers by the SMS Discovery Data Manager, and the installation process does not occur.

For more information about how to configure SMS site boundaries, see the "Client Deployment Planning" section in the Systems Management Server 2003 Concepts, Planning, and Deployment Guide. To view this guide, visit the following Microsoft Web site:
http://www.microsoft.com/technet/prodtechnol/sms/sms2003/cpdg/default.mspx?mfr=true (http://www.microsoft.com/technet/prodtechnol/sms/sms2003/cpdg/default.mspx?mfr=true)
Advanced Client Push Installation is not enabled at the appropriate site
If the Advanced Client Push Installation is not enabled for the site, the SMS Discovery Data Manager does not automatically generate a CCR file for client computers that do not reside within its own site boundaries.
The SMS Client Configuration Manager cannot connect to the client Admin$ share or to the Remote Registry Service (IPC$)
When the Client Configuration Manager cannot connect to Admin$, errors that resemble the following are logged in the Ccm.log file:
7260 (0x1C5C)6/6/2006 7:06:31 AM
Attempting to connect to administrative share '\\\Admin$' using account 'domain\account'SMS_CLIENT_CONFIG_MANAGER 7400 (0x1CE8)6/6/2006 7:06:34 AM
WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account domain\account (000004b3)SMS_CLIENT_CONFIG_MANAGER 7400 (0x1CE8)6/6/2006 7:06:34 AM
WNetAddConnection2 failed (LOGON32_LOGON_INTERACTIVE) using account domain\account (000004b3)SMS_CLIENT_CONFIG_MANAGER 660 (0x0294)6/6/2006 7:06:35 AM
ERROR: Unable to connect to remote registry for machine name "computername", error 53.SMS_CLIENT_CONFIG_MANAGER 660 (0x0294)6/6/2006 7:06:35 AM
ERROR: Unable to access target machine for request: "computername.KRC", machine name: "computername", error code: 53SMS_CLIENT_CONFIG_MANAGER 660 (0x0294)6/6/2006 7:06:36 AMStored request "computername.KRC", machine name "computername", in queue "Retry".SMS_CLIENT_CONFIG_MANAGER
In this situation, an error code 53 is logged when the site server is unable to locate the client:
The network path was not found.
Error code 53 is usually preceded by the following error message:
000004b3 - “No network provider accepted the given network path.”
This log entry may occur before the error 53, or there may be additional information between this log entry and error 53 in the log file.

This issue may occur when one or more of the following conditions are true:
• There are network connectivity problems.
• There are name resolution issues with, for example, Windows Internet Name Service (WINS) or Domain Name System (DNS).
• The Remote Registry service is disabled on the client computer.
• The Microsoft Windows XP or Microsoft Windows Server 2003 firewall is blocking communications between the SMS Advanced Client and the SMS site server.
• The Server service on the client is not started.
• File and Printer Sharing for Microsoft Networks is not installed on the client computer.

Note If File and Printer Sharing for Microsoft Networks is not installed on the client, you receive the following error message:
Error 67 - The network name cannot be found.
The SMS Advanced Client Push Installation account is configured incorrectly or is missing or is locked out
When this issue occurs, an error code 5 message appears in the Ccm.log file on the site server. In the following example, Computer is the computer name of the SMS Advanced Client computer:
Attempting to connect to administrative share '\\COMPUTER1\Admin$' using account 'domain\account'
WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account domain\account (0000052e)
LogonUser failed (LOGON32_LOGON_INTERACTIVE) using account domain\account (0000052e)
ERROR: Unable to connect to remote registry for machine name "Computer", error 5.
ERROR: Unable to access target machine for request: "Computer", machine name: "Computer", error code: 5
Note Error code 5 is an Access Denied error.

Solution The Advanced Client Push Installation account must have administrative credentials on the computers where you want to install the SMS Advanced Client components.

On all potential client computers, the Advanced Client Push Installation process requires that you grant administrator rights and permissions to either of the following accounts:
• The SMS Service account when the site is running in standard security mode
• The Advanced Client Push Installation accounts that you define
You can create multiple Advanced Client Push Installation Accounts. Clients that are not members of a domain cannot authenticate domain accounts. For clients that are not members of a domain, you can use a local account on the client computers.

For example, if you set up a standard account on each computer for administrative purposes, and all the accounts have the same password, you can define an Advanced Client Push Installation account as %machinename%\account. For more information about how to prepare an SMS 2003 site for a Client Push installation, click the following article number to view the article in the Microsoft Knowledge Base:
838436 (http://support.microsoft.com/kb/838436/) How to prepare the Systems Management 2003 site for a Client Push installation
The SMS Advanced Client Network Access Account is configured incorrectly or is missing or is locked out in a non-Active Directory environment
You must configure the SMS 2003 Advanced Client Network Access Account for the SMS 2003 site before you can use the Advanced Client Push Installation method to deploy the SMS 2003 Advanced Client software on client computers in the following non-Active Directory environments:
• A workgroup
• A Windows NT 4.0 domain
• An untrusted forest
The Advanced Client Network Access Account is a domain-level account that you create for Advanced Clients. If you define the account in a non-Active Directory environment, the account is used to access the Client.msi file and related installation files from the SMSClient share on the SMS site server or on the SMS management point.

Note If the SMS Advanced Client Network Access Account is unavailable, SMS uses the currently logged-on user account, the local system account, or the computer account of the destination computer to make this connection.

In this configuration, the SMS Advanced Client Network Access Account resembles the Client Connection account on a SMS Legacy Client computer.

Back to the top
Installation phase
1. Ccmsetup.exe starts, and then scans the MobileClient.tcf file. This file is a configuration file from which Ccmsetup.exe obtains information that is required to locate the Client.msi file on the site server. The MobileClient.tcf file also provides the SMS site code, the management point server name, the site boundary, and other information.
2. Ccmsetup.exe downloads the client.msi file from the SMSClient\i386 shared folder on the SMS management point or from the Client\i386 folder in the SMS_sitecode shared folder on the SMS site server. The Advanced Client Installer runs the Client.msi Setup program by using the parameters that the administrator specifies in the SMS Administrator console.

Back to the top
Troubleshooting installation issues
The SMS Advanced Client cannot access the installation file on the SMS site server
The Client.msi file resides in the SMSClient\i386 folder on management points or in the Client\i386 folder on the SMS site server.

To troubleshoot access to this file, check the following logs on the SMS Advanced Client computer:
• %windir%\System32\Ccmsetup\Ccmsetup.log
• %windir%\System32\Ccmsetup\Client.msi.log
Solution When you try to troubleshoot a failure condition, you can use the SMS Trace utility (Trace32.exe) to review SMS log data and to locate the following error message:
Return Value 3
The lines that come before this error mention why the installation was not completed successfully.

Note When you review the Client.msi.log file on the Advanced Client computer, do not search for the word "Error" to determine why the installation was not completed successfully. The Client.msi.log file includes all the information that is available to the Microsoft Windows Installer application. This information includes error messages and other properties.

The SMS Trace utility is included in the Systems Management Server 2003 Toolkit. To download the Systems Management Server Toolkit, visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/sms/bb676787.aspx (http://technet.microsoft.com/en-us/sms/bb676787.aspx)
The SMS Advanced Client cannot access the management point during an upgrade
When the SMS Advanced Client computer cannot access the management point, the Ccmsetup.log contains the following error:
Server failed to process message and returned status code 404
This problem typically occurs when the management point is not installed or does not start correctly.

Solution To help troubleshoot this issue, see the "Troubleshooting management point issues" section.
Clients that are deployed by using Capinst.exe are not installed successfully
When you deploy the Advanced Client by using Capinst.exe, you must make sure that a server locator point (SLP) is available. The SLP returns a list of management points.

Solution Install a server locator point, and then make sure that the SLP is published in Active Directory or is registered in the WINS database.
1. Install a server locator point. An SLP can be added as a site system role in the SMS Administrator console. To do this, follow these steps:
a. Click Start, point to Programs, point to Systems Management Server, and then click SMS Administrator Console.
b. In the SMS Administrator console, expand Site Database, expand Site Hierarchy, expand SiteCode-SiteName, and then expand Site Settings.
c. Click Site Systems, right-click the server that is acting as the management point, and then click Properties.
d. In the \\ServerName Site Systems Properties dialog box, click the Server Locator Point tab, and then select the Use this site system as a server locator point check box.
e. In the list that is next to Database, you can select the site database or select another database. Make a selection, and then click OK.
2. If the SLP already exists, make sure that it is published in Active Directory or is registered in the WINS database if you have not extended the Active Directory schema. WINS is also used as a fallback if the Lightweight Directory Access Protocol (LDAP) query fails.
BITS installation issues
Background Intelligent Transfer Service (BITS) installation issues can be difficult to detect if the BITS installation that runs as part of Client.msi is causing the Advanced Client Push Installation to fail. If the BITS installation is not successful, the Advanced Client Push Installation will not be successful.

Solution Run the BITS install manually to determine any errors. You can do this by using one of the following methods:
1. Download and install the BITS 1.5 Client (Bits_v15_client_setup.exe). To obtain the BITS 1.5 Client, visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?FamilyID=8c6ef6c8-2abf-43c7-ab51-e0c53303086d&DisplayLang=en (http://www.microsoft.com/downloads/details.aspx?FamilyID=8c6ef6c8-2abf-43c7-ab51-e0c53303086d&DisplayLang=en)
2. Run msiexec /a client.msi at the command prompt to extract the Bits_v15_client_setup.exe file out of the Client.msi file, and then double-click the bitssetup_clnt_installer.exe file. If the BITS installation does not start successfully, you must check the Bitssetup.log file for errors. If the BITS installation is successful, try running Client.msi file again.
XML file registration is unsuccessful
An SMS 2003 Advanced Client computer may not obtain configuration settings from the site server. When this occurs, you may receive an error message that resembles the following in the Ccmexec.log file on the SMS Advanced Client computer:
Error creating XML DOM (0x80040154) CForwarder_Base::Send failed (0x80004005).
In this case, the Msxml3.dll file may not be registered or is missing.

Solution Download the Msxml3.msi file and install it on the computers that require Microsoft XML Parser (MSXML) 3.0 Service Pack 7 (SP7) or later versions to be installed. Installing the Msxml3.msi file also registers the additional DLL files. Note To download the Microsoft XML Parser (MSXML) 3.0 Service Pack 7 (SP7) release, visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?familyid=28494391-052b-42ff-9674-f752bdca9582&displaylang=en (http://www.microsoft.com/downloads/details.aspx?familyid=28494391-052b-42ff-9674-f752bdca9582&displaylang=en)

Back to the top
Post-installation phase
1. By default, if the Advanced Client Push Installation properties specify that the client is automatically assigned to a site by using the property SMSSITECODE=AUTO, the client queries Active Directory for its site assignment.
2. If Active Directory is not installed, or the SMS schema is not extended, the client searches for a server locator point from which to obtain the site assignment and the management point information.
3. If the Active Directory schema is extended, the client obtains its site assignment and management point information by using an LDAP query to Active Directory.
4. When the client uses an SLP lookup or Active Directory lookup to locate the default management point, the client requests the initial policy from the management point.

Back to the top
Troubleshooting post-installation issues
The SMS Advanced Client is installed successfully, but does not appear as installed or assigned
1. You must verify that the SMS Agent Host service is running on the client. If the SMS Agent Host service is not running, the client may not send a heartbeat discovery record to report that the client is installed and assigned.
2. Double-click the SMS Client Control Panel item on the SMS Advanced Client computer, and then click the Advanced tab in the Systems Management Properties box. If no site code is listed, click Automatically Discover. If the discovery fails, it may be because of one or more of the following reasons:
• The Active Directory schema has not been extended for SMS 2003. If you ran ExtADSch.exe manually to extend the Active Directory schema, the ExtADSch.log file will contain information about the Active Directory update and whether Active Directory was extended successfully. This log file is located in the root of the system drive.

Note You must be an Enterprise Administrator to extend the Active Directory schema.
• SMS site systems have not been published in Active Directory. You can view \SMS\Logs\Sitecomp.log on the SMS Server to see whether the SMS site systems have been published. For more information about how to grant permissions on the System Management container in Active Directory, click the following article number to view the article in the Microsoft Knowledge Base:
830022 (http://support.microsoft.com/kb/830022/) Status message 4909, 4912, 4913, or 4915, or error code 8202 after you install Systems Management Server 2003
.
• The server locator point cannot be located. The SLP must be published in Active Directory or registered in WINS in non-Active Directory environments.
The SMS Advanced Client is installed successfully but it does not receive a site assignment
The client computer appears in collections with the following values:
Site Code Client Assigned Client Type
ABC Yes No Advanced
In this case, the SMS Advanced Client may be listed as a client. However, it is not assigned to the site. This occurs for the following reasons:
1. The collection information has not been updated. Collection updates usually run on a daily or weekly schedule. In this case, you must make sure that the collection information has been updated. You can manually update the collection membership, and then update the collection view.
2. The client may also be a client for another site and not assigned to the one that you are viewing in the SMS Administrator console. You must check the Advanced properties of the client's Systems Management item in Control Panel and see whether a different site is listed.
The SMS Advanced Client displays a site assignment but does not appear as installed
The Client computer appears in collections with the following values:
Site Code Client Assigned Client Type
ABC No Yes Advanced
This occurs when one or more of the following conditions are true:
1. The collection information has not been updated. Collection updates usually run on a daily or weekly schedule. In this case, you must make sure that the collection information has been updated. You can manually update the collection membership, and then update the collection view.
2. The client computer shares the same SMSID with another client computer. This issue can occur when you use a disk image to install the SMS Advanced Client. Duplicate SMSIDs are also referred to as duplicate GUIDs. You must determine whether duplicate SMSIDs exist on the client computers. For more information about how to detect duplicate GUIDs and how to use Tranguid.exe to create a New SMS GUID for the affected clients., click the following article number to view the article in the Microsoft Knowledge Base:
837374 (http://support.microsoft.com/kb/837374/) How to locate and clean Advanced Client Duplicate GUIDs in SMS 2003
3. The SMS Advanced Client is assigned. However, the SMS Advanced Client is not installed. You must verify that the SMS Advanced Client is installed successfully and is assigned to the site that you are viewing.
4. The Network Discovery method is enabled. When you use the Network Discovery method in Systems Management Server (SMS), it populates the IsClient fields in the database by using a Null value. If other discovery methods are enabled, the computer will appear in the collection as Assigned with no client installed even though the client is installed. To resolve this issue, disable the Network Discovery method. Also, verify that the Heartbeat Discovery method that is enabled by default has not been disabled. Then, wait for the specified Heartbeat Discovery polling interval to pass. When the clients send up new discovery data, the database is updated to reflect the correct values.

Note Only the Heartbeat Discovery method will set the client installation status to Yes. The Active Directory System discovery method does not update the IsClient field in the SMS database.
5. Heartbeat Discovery has not reported since the client was installed.

Solution
• Verify that a heartbeat has occurred on the client by reviewing the inventoryagent.log. This log is located in the %windir%\System32\ccm\logs folder. You must locate the Inventory: Action=Discovery ReportType=Full string.
• You can use the Advanced Client Spy utility to view the status of discovery data. This utility is part of SMS 2003 Toolkit 1.

To download SMS 2003 Toolkit 1, visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/sms/bb676787.aspx (http://technet.microsoft.com/en-us/sms/bb676787.aspx)
In the discovery record properties, you can view the discovery method that reported the discovery, and the last time that the discovery process ran. You can review the record to determine whether the issue is a failure to run a discovery property. If the data that is provided by Heartbeat Discovery is current, this issue may occur because of a client assignment issue on the SMS Advanced Client computer. If the correct Heartbeat Discovery data is not present, a communication problem may exist between the client, the management point, the site, and the site database.
• Troubleshooting Heartbeat Discovery - You can use Systems Management to manually initiate a Heartbeat Discovery on the client. To do this, follow these steps:
1. Click Start, point to Control Panel, and then double-click Systems Management.
2. Click the Actions tab, select the Discovery Data Collection Cycle, and then click Initiate Action.
Note whether the Clear Install Flag task is selected, and compare the Client Rediscovery interval to the Heartbeat Discovery interval. If the Client Rediscovery interval is less than the Heartbeat Discovery interval, you must change this to make sure that the Client Rediscovery interval is a value that is larger than the Heartbeat Discovery interval. To do this, follow these steps:
1. In the SMS 2003 Administrator console, expand Site Database\Site Hierarchy\your site code\Site Settings\Site Maintenance\Tasks.
2. Double-click Clear Install Flag, make sure that the Schedule interval is a value that is larger than the Heartbeat Discovery interval, and then click OK.
Note The Heartbeat Discovery setting is located in the SMS Administrator console under Site Database\Site Hierarchy\your site code\Site Settings\Discovery Methods.
SMS Advanced Client does not receive a policy after installation
This issue occurs when the SMS management point is not installed or is not functioning. More information about this issue is available in the "Troubleshooting management point issues" section.
SMS Advanced Clients are not installed on secondary sites
When you perform an automatic Advanced Client Push Installation from a primary SMS site, the SMS Advanced Client is installed on computers that reside in the primary site. However, the SMS Advanced Client is not installed on computers that reside in the secondary site.

This issue occurs when the Include only clients assigned to this site option is enabled in the Client Push Installation Properties dialog box. You can resolve this issue by using one of the following methods:
1. Start the Advanced Client Push Installation Wizard, and then clear the Include only clients assigned to this site check box.

Note You cannot enable the Include only clients assigned to this site option at the command line. It must be done manually in the Advanced Client Push Installation Wizard.
2. Make sure that the Advanced Client Push Installation method is turned on at the secondary site. Additionally, make sure that the necessary discovery methods are enabled at the site.

Note When you perform the Advanced Client Push Installation method from a secondary site to install the SMS Advanced Client, you must not set the SMSSITECODE={Secondary Sitecode} site code, where Secondary Sitecode is the secondary site code. If you set the secondary site code in this manner, the SMS Advanced Client is installed to a state where it appears to be assigned and managed by the secondary site.

Back to the top
Troubleshooting management point issues
To help determine whether you are experiencing management point issues, you can have the client computer request a Machine policy from the management point. To request a Machine policy from the management point, follow these steps:
1. Click Start, point to Control Panel, and then double-click Systems Management.
2. Click the Actions tab, select Machine Policy Retrieval & Evaluation Cycle, and then click Initiate Action.
3. To update the Systems Management Control Panel item, you must close and reopen the Systems Management Control Panel item.
When the SMS management point cannot connect to Microsoft SQL server, see the following Microsoft Knowledge Base article:
832109 (http://support.microsoft.com/kb/832109/) New clients do not install and existing clients do not run advertisements after you install a new Management
For more information about how to troubleshoot SMS management point issues, visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/library/cc180193.aspx (http://technet.microsoft.com/en-us/library/cc180193.aspx)

Back to the top
Tools and procedures to help troubleshoot SMS Advanced Client installation issues
To help troubleshoot SMS Advanced Client installation issues, you may have to follow these steps:
• Use a CCR file to manually trigger the client installation.
• Use the SMS Administrator console to force a full reinstallation of the SMS Advanced Client.
• Use the Ccmclean.exe tool to remove the SMS 2003 Advanced Client.
• Gather the SMS server log files and the SMS Advanced Client log files for analysis.
Use a CCR file to manually trigger the client installation
When you enable the Advanced Client Push Installation method, SMS automatically creates a CCR file. The CCR file is useful for troubleshooting issues with client installations. The CCR file can also be created and applied to the server manually. To do this, follow these steps:
1. Click Start, click Run, type notepad, and then click OK.
2. In Notepad, type the following two lines:

[NT Client Configuration Request] Machine Name=NetBIOSName

Note In this example, NetBIOSName is the name of the computer where you want to install the SMS Advanced Client.
3. Click File, and then click Save As.
4. In the Save As dialog box, type "test.ccr", and then click OK. You must include the quotation marks.
5. After the CCR file is manually created, copy and paste it into the SMS\Inboxes\Ccr.box folder on the SMS Site Server. When the CCR file is processed, the file is moved to the SMS\Inboxes\Ccr.box\Inproc folder. When the process is complete, the CCR file is moved to the SMS\Inboxes\Ccrretry.box folder and is renamed to the name of the destination computer.
Use the SMS Administrator console to force a full reinstallation of the SMS Advanced Client
1. Click Start, point to Programs, click Systems Management Server, and then click SMS Administrator Console.
2. Expand Site Database, expand Collections, and then expand All Systems.
3. In the right pane, right-click a discovered SMS 2003 client, click All Tasks, and then click Install Client.
4. On the Welcome to the Client Push Installation Wizard screen, click Next.
5. On the Client Installation Options page, click the Always install (repair or upgrade existing client) check box.
6. Click Next, and then click Finish.
The following log files are used when you perform an Advanced Client Push Installation from the SMS Administrator console:
• The Smsprov.log contains information about CCR creation.
• The Ccm.log contains information about the client installation process.
Note These log files are located in the \SMS\Logs folder on the SMS site server. The SMS Provider log may reside on the remote SQL Server if the SQL Server does not reside on the SMS site server computer. However, if the client is installed from a secondary site, you must review the Ccm.log from the secondary site and not from the parent site.
Use the Ccmclean.exe tool to remove the SMS 2003 Advanced Client
The Ccmclean.exe tool is a component of the SMS 2003 Toolkit. You can use the tool to remove the SMS 2003 Advanced Client, the SMS 2003 management point, or both.

To obtain the SMS 2003 Toolkit, visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/sms/bb676787.aspx (http://technet.microsoft.com/en-us/sms/bb676787.aspx)
The following is the syntax that is used by the Ccmclean tool:
• Ccmclean /client: This removes an SMS Advanced Client.
• Ccmclean /mp: This removes a management point.
• Ccmclean /all: This removes both the SMS Advanced Client and a management point if both are installed.
Gather the SMS server and the SMS Advanced Client log files for analysis
For more information about the SMS log files, click the following article number to view the article in the Microsoft Knowledge Base:
867490 (http://support.microsoft.com/kb/867490/) A list of log files that are created in Systems Management Server 2003
Note We recommend that you use the Trace32 tool (SMSTrace) that is part the SMS Toolkit to view log files because it lets you view the log files in real time. SMSTrace also lets you perform error code lookups. Press CTRL+L in SMSTrace to display the error lookup dialog box. You can then enter the error code. If it is an error code that SMSTrace can decrypt, such as a Win32 error or a WMI error, the text of the error code is also displayed.

To obtain the SMS 2003 Toolkit, visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/sms/bb676787.aspx

Proxy auto-config

2008-10-15T20:50:00.001+07:00

The proxy auto-config file defines how web browsers and other user agents can automatically choose the appropriate proxy server (access method) for fetching a given URL.

A PAC file contains a JavaScript function "FindProxyForURL(url, host)". This function returns a string with one or more access method specifications. These specifications cause the user agent to use a particular proxy server or to connect directly.

Multiple specifications provide a fallback when a proxy fails to respond. The browser fetches this PAC file before retrieving other pages. The URL of the PAC file is either configured manually or determined automatically by the Web Proxy Autodiscovery Protocol.
Contents
[hide]

* 1 Context
* 2 The PAC File
o 2.1 Limitations
* 3 Further reading
* 4 External links

[edit] Context

Modern web browsers implement several levels of automation; you can choose the level that is appropriate to your needs. The following methods are commonly implemented:

* Manual proxy selection: Specify a hostname and a port number to be used for all URLs. Most browsers allow you to specify a list of domains (such as localhost) that will bypass this proxy.
* Proxy auto-configuration (PAC): Specify the URL for a PAC file with a JavaScript function that determines the appropriate proxy for each URL. This method is more suitable for laptop users who need several different proxy configurations, or complex corporate setups with many different proxies, and is discussed in this article.
* Web Proxy Autodiscovery Protocol (WPAD): Let the browser guess the location of the PAC file through DHCP and DNS lookups. This is discussed in a separate article.

[edit] The PAC File

To use PAC, you publish a PAC file on a Web server and instruct a user agent to utilize it, either by entering the URL in the proxy connection settings of your browser or through the use of the WPAD protocol.

A PAC file is a text file that defines at least one JavaScript function, FindProxyForURL(url, host). By convention, this file is normally named proxy.pac. The WPAD standard uses wpad.dat.

Even though most clients will process the script regardless of the MIME type returned in the HTTP request, for the sake of completeness and to maximize compatibility, you should instruct your web server to declare the MIME type of this file to be either application/x-ns-proxy-autoconfig or application/x-javascript-config.

There is little evidence to favor the use of one MIME type over the other. It would be, however, reasonable to assume that application/x-ns-proxy-autoconfig will be supported in more clients than application/x-javascript-config as it was defined in the original Netscape specification, the latter type coming in to use more recently.

A very simple example of a PAC file is:

function FindProxyForURL(url, host) { return "PROXY proxy.foo.com:8080; DIRECT"; }

This function instructs the browser to retrieve all pages through the proxy on port 8080 of the server proxy.foo.com. Should this proxy fail to respond, the browser contacts the WWW directly, without using a proxy.

Here is a more complicated example demonstrating some available JavaScript functions to be used in the FindProxyForURL function:

function FindProxyForURL(url, host) {
// our local URLs from the domains below foo.com don't need a proxy:
if (shExpMatch(url,"*.foo.com/*")) {return "DIRECT";}
if (shExpMatch(url, "*.foo.com:*/*")) {return "DIRECT";}

// URLs within this network are accessed through
// port 8080 on fastproxy.foo.com:
if (isInNet(host, "10.0.0.0", "255.255.248.0")) {
return "PROXY fastproxy.foo.com:8080";
}

// All other requests go through port 8080 of proxy.foo.com.
// should that fail to respond, go directly to the WWW:
return "PROXY proxy.foo.com:8080; DIRECT";
}

[edit] Limitations

The function dnsResolve (and similar other functions) performs a DNS lookup that can block your browser for a long time if the DNS server does not respond.

Caching of proxy autoconfiguration results by domain name in Microsoft's Internet Explorer 5.5 or higher limits the flexibility of the PAC standard. In effect, you can choose the proxy based on the domain name, but not on the path of the URL. Alternatively, you need to disable caching of proxy autoconfiguration results by editing the registry. Refer to the article by de Boyne Pollard (listed in #Further_reading) for more details.

It is recommended to always use IP instead of host domain names in isInNet function for compatibilities with other components in Windows which makes use of Internet Explorer PAC settings, such as .NET 2.0 Framework. For example,

if (isInNet(host, dnsResolve(sampledomain) , "255.255.248.0") // .NET 2.0 will resolve proxy properly

if (isInNet(host, sampledomain, "255.255.248.0") // .NET 2.0 will not resolve proxy properly

The current convention is to fail over to direct connection when a PAC file is unavailable.

Further limitations are related to the JavaScript engine on the local machine.

[edit] Further reading

Jonathan de Boyne Pollard (2004). "Automatic proxy HTTP server configuration in web browsers". Frequently Given Answers.

For more information please visit http://en.wikipedia.org/wiki/Proxy_auto-config

Nero Burning ROM 9

2008-10-01T21:44:00.001+07:00

Nero Burning ROM, commonly called just Nero, is a popular optical disc authoring program for Microsoft Windows and Linux by Nero AG, formerly Ahead Software. Now the program is usually a part of various software suites—such as Nero 7 Premium Reloaded—most of which also bears the designation Nero.
A limited-functionality version of Nero Burning ROM is distributed as Nero Express, mainly aimed at the casual market. It has simplified, stream-lined menus presumably for a less computer-savvy audience.

Nero 9 Highlights:

- Fast and easy rip, burn, Autobackup, and copy functions
- Backup files to CDs, DVDs, and Blu-ray Discs*
- Create professional-looking DVD movies with integrated 3D menus
- Copy, burn, share, upload, and create music mixes like a DJ
- Convert music, photos, and DVDs to play on your iPod® and other mobile devices
- Quick photo and video upload to My Nero, YouTube™, and MySpace
- Watch, record, pause, and customize your live TV experience
- Play AVCHD and other HD formats

Download:
http://rapidshare.com/files/149450865/ANBR_v9.0.9.4_Multilingual-DOOM.part1.rar
http://rapidshare.com/files/149450869/ANBR_v9.0.9.4_Multilingual-DOOM.part2.rar
http://rapidshare.com/files/149450533/ANBR_v9.0.9.4_Multilingual-DOOM.part3.rar

OR

http://www.filefactory.com/file/2e37c0/n/ANBR_v9_0_9_4_Multilingual-DOOM_part1_rar
http://www.filefactory.com/file/9433ef/n/ANBR_v9_0_9_4_Multilingual-DOOM_part2_rar
http://www.filefactory.com/file/fa8492/n/ANBR_v9_0_9_4_Multilingual-DOOM_part3_rar

OR

http://www.megaupload.com/?d=6H9QS47G
http://www.megaupload.com/?d=VBNZ5WZH
http://www.megaupload.com/?d=MWYXFXNA

PASS:
http://irfree.com

Fifa 2009

2008-10-01T21:30:00.001+07:00

Release Date : 01/10/2008
Platform : Wii
Genre : Sport
Origin : PAL
Languages : ENG
Link : www.gamespot.com/wii/sports/fifasoccer09/index.html

Download:
http://rapidshare.com/files/149898388/F09_PAL_Wii-WiiERD.part01.rar
http://rapidshare.com/files/149898546/F09_PAL_Wii-WiiERD.part02.rar
http://rapidshare.com/files/149898299/F09_PAL_Wii-WiiERD.part03.rar
http://rapidshare.com/files/149898513/F09_PAL_Wii-WiiERD.part04.rar
http://rapidshare.com/files/149898452/F09_PAL_Wii-WiiERD.part05.rar
http://rapidshare.com/files/149898559/F09_PAL_Wii-WiiERD.part06.rar
http://rapidshare.com/files/149898438/F09_PAL_Wii-WiiERD.part07.rar
http://rapidshare.com/files/149898499/F09_PAL_Wii-WiiERD.part08.rar
http://rapidshare.com/files/149898551/F09_PAL_Wii-WiiERD.part09.rar
http://rapidshare.com/files/149898531/F09_PAL_Wii-WiiERD.part10.rar
http://rapidshare.com/files/149898510/F09_PAL_Wii-WiiERD.part11.rar
http://rapidshare.com/files/149898525/F09_PAL_Wii-WiiERD.part12.rar
http://rapidshare.com/files/149898883/F09_PAL_Wii-WiiERD.part13.rar
http://rapidshare.com/files/149898848/F09_PAL_Wii-WiiERD.part14.rar
http://rapidshare.com/files/149898827/F09_PAL_Wii-WiiERD.part15.rar
http://rapidshare.com/files/149898882/F09_PAL_Wii-WiiERD.part16.rar
http://rapidshare.com/files/149898824/F09_PAL_Wii-WiiERD.part17.rar
http://rapidshare.com/files/149898895/F09_PAL_Wii-WiiERD.part18.rar
http://rapidshare.com/files/149898840/F09_PAL_Wii-WiiERD.part19.rar
http://rapidshare.com/files/149898863/F09_PAL_Wii-WiiERD.part20.rar
http://rapidshare.com/files/149898843/F09_PAL_Wii-WiiERD.part21.rar
http://rapidshare.com/files/149898786/F09_PAL_Wii-WiiERD.part22.rar
http://rapidshare.com/files/149898706/F09_PAL_Wii-WiiERD.part23.rar

OR

http://netload.in/dateiNTQ2NTAyMT/F09_PAL_Wii-WiiERD.part01.rar.htm
http://netload.in/dateiNzU5MTQ2Nj/F09_PAL_Wii-WiiERD.part02.rar.htm
http://netload.in/dateiMjgyNjYwMz/F09_PAL_Wii-WiiERD.part03.rar.htm
http://netload.in/dateiMjEwNTQ3Mz/F09_PAL_Wii-WiiERD.part04.rar.htm
http://netload.in/dateiMTI4NzM1NT/F09_PAL_Wii-WiiERD.part05.rar.htm
http://netload.in/dateiMjkyMTI0Nj/F09_PAL_Wii-WiiERD.part06.rar.htm
http://netload.in/dateiMzU1MjE5MT/F09_PAL_Wii-WiiERD.part07.rar.htm
http://netload.in/datei40c615c2e0/F09_PAL_Wii-WiiERD.part08.rar.htm
http://netload.in/dateiMTEwNzA5ND/F09_PAL_Wii-WiiERD.part09.rar.htm
http://netload.in/dateiMTI2Mjg1MD/F09_PAL_Wii-WiiERD.part10.rar.htm
http://netload.in/dateiNTA1OTg0Nj/F09_PAL_Wii-WiiERD.part11.rar.htm
http://netload.in/dateiMjE2NjQ3OT/F09_PAL_Wii-WiiERD.part12.rar.htm

PASS:
http://irfree.com

Thiết lập hệ thống mạng Ubuntu quản lý tập trung với LDAP

2008-07-27T19:02:00.002+07:00

Nguồn: http://www.quantrimang.com.vn/view.asp?Cat_ID=5&Cat_Sub_ID=0&news_id=44600

1. Giới thiệu

Trong tương lai không xa, phần mềm mã nguồn mở và miễn phí rất có thể sẽ trở thành một lựa chọn tất yếu đối với các tổ chức/doanh nghiệp. Với ưu điểm mã nguồn mở, dễ dàng mở rộng, hoạt động ổn định… lĩnh vực ứng dụng này đang ngày càng chứng tỏ tính khả dụng và hiệu quả của nó.

Hầu hết các tổ chức/doanh nghiệp đều cần đến một hệ thống mạng nội bộ để hỗ trợ xử lý công việc thường ngày, điều hành hoạt động, phối hợp làm việc…

Bài viết sẽ hướng dẫn các bước xây dựng hệ thống mạng Ubuntu quản lý tập trung với LDAP, một giải pháp hoàn toàn có thể thay thế hệ thống mạng Microsoft Windows với Active Directory.

2. Yêu cầu hệ thống

Chúng ta sử dụng 03 máy tính với thông tin như sau:

Máy tính Ubuntu server:
o Địa chỉ IP: 192.168.10.2
o DNS server: 192.168.10.2
o Tên máy: ubuntu-server

Máy tính Ubuntu desktop 01:
o Địa chỉ IP: 192.168.10.12
o DNS server: 192.168.10.2
o Tên máy: ubuntu-desktop01

Máy tính Ubuntu desktop 02:
o Địa chỉ IP: 192.168.10.14
o DNS server: 192.168.10.2
o Tên máy: ubuntu-desktop02
3. Cấu hình hệ thống

3.1. Cấu hình ubuntu-server

Trên máy ubuntu-server, chúng ta thực hiện:

Cài đặt và cấu hình DNS server với phần mềm BIND.
o Domain name: bits.com.vn
o Bổ sung 02 Host (A) record tương ứng với 02 máy trạm Ubuntu vào DNS server:

ubuntu-desktop01.bits.com.vn 192.168.10.12
ubuntu-desktop02.bits.com.vn 192.168.10.14

Cài đặt và cấu hình LDAP server với phần mềm OpenLDAP.
o Bổ sung 02 account tương ứng với 02 máy trạm Ubuntu vào LDAP server:

Account 01 - tthai:********
Account 02 - ctbach:********
Các bước thực hiện lần lượt như sau:
Cài đặt và cấu hình DNS server với phần mềm BIND
1. Cài đặt Ubuntu server, phiên bản 7.10

Trong quá trình cài đặt, thiết lập các thông số sau:

Địa chỉ IP: 192.168.10.2
DNS server: 192.168.10.2
Netmask: 255.255.255.0
Tên máy: ubuntu-server
Phần mềm: chọn các gói cài đặt cho DNS server
2. Cấu hình DNS server

Phần mềm dùng để xây dựng DNS server trên Ubuntu là BIND (Berkeley Internet Name Domain). Chúng ta sẽ thao tác trên các file của BIND để cấu hình DNS server. Các bước thực hiện như sau:

Sao chép dự phòng các file của BIND:
tthai@ubuntu-server:~$ sudo -i
[sudo] password for tthai:
root@ubuntu-server:~#
root@ubuntu-server:~# mkdir /backup
root@ubuntu-server:~# cp -R /etc/bind /backup

Cấu hình BIND:
Hiệu chỉnh file cấu hình chính của BIND - /etc/bind/named.conf - bằng cách bổ sung các dòng sau vào cuối file:

root@ubuntu-server:~# vim /etc/bind/named.conf
…
// The zone definition
zone “bits.com.vn” {
type master;
file “/etc/bind/zones/bits.com.vn.db”;
};
// The zone definition for reverse DNS
zone “10.168.192.in-addr.arpa” {
type master;
file “/etc/bind/zones/rev.10.168.192.in-addr.arpa”;
};

Hiệu chỉnh file /etc/bind/named.conf.options để chuyển (forward) những yêu cầu mà DNS server này không phân giải được:

root@ubuntu-server:~# vim /etc/bind/named.conf.options
options {
…
forwarders {
10.238.200.1;
10.238.200.8;
10.238.200.12;
};
};

Tạo các file zone:

o /etc/bind/zones/bits.com.vn.db: dùng cho việc lưu trữ các cặp IP address/machine name để DNS server này phân giải.
o /etc/bind/zones/rev.10.168.192.in-addr.arpa: dùng cho mục đích phân giải ngược.

root@ubuntu-server:~# mkdir /etc/bind/zones
root@ubuntu-server:~# vim /etc/bind/zones/bits.com.vn.db
$TTL 604800
@ IN SOA ubuntu-server.bits.com.vn. admin.bits.com.vn. (
1 ; Serial
604800 ; Refresh
86400 ; Retry
2419200 ; Expire
604800) ; Negative Cache TTL
;
; Replace the following line as necessary:
; ns1 = DNS server name
; mail = Mail server name
; bits.com.vn. IN MX 10 mail.bits.com.vn.

@ IN NS ubuntu-server.bits.com.vn.
@ IN A 192.168.10.2
ubuntu-server.bits.com.vn. IN A 192.168.10.2

root@ubuntu-server:~# vim /etc/bind/zones/rev.10.168.192.in-addr.arpa
; The number before IN PTR ubuntu-server.bits.com.vn is
; the machine address of the DNS server. In this case, it’s
; 2, as my IP address is 192.168.10.2.

$TTL 604800
@ IN SOA ubuntu-server.bits.com.vn. admin.bits.com.vn. (
1 ; Serial
604800 ; Refresh
86400 ; Retry
2419200 ; Expire
604800) ; Negative Cache TTL
;
@ IN NS ubuntu-server.bits.com.vn.
2 IN PTR ubuntu-server.bits.com.vn.
Hiệu chỉnh file /etc/resolv.conf để liệt kê danh sách các DNS server trong mạng của mình:

root@ubuntu-server:~# vim /etc/resolv.conf
search bits.com.vn
nameserver 192.168.10.2

Khởi động lại dịch vụ BIND:
root@ubuntu-server:~# /etc/init.d/bind9 restart

Kiểm tra DNS server với tiện ích dig (domain information groper). dig là tiện ích truy vấn dữ liệu trên DNS server (DNS lookup utility). Tiện ích này sẽ tìm kiếm trên DNS server và hiển thị thông tin do DNS server trả về.
root@ubuntu-server:~# dig bits.com.vn

Bên cạnh đó, chúng ta cũng cần sử dụng tiện ích ping để kiểm tra:

root@ubuntu-server:~# ping bits.com.vn
root@ubuntu-server:~# ping ubuntu-server
root@ubuntu-server:~# ping ubuntu-server.bits.com.vn
Cài đặt và cấu hình LDAP server với phần mềm OpenLDAP
1. Cài đặt OpenLDAP

Phần mềm dùng để xây dựng LDAP server trên Ubuntu là OpenLDAP. Chúng ta sẽ cài đặt các phần mềm và tiện ích cần thiết để thiết lập LDAP server, bao gồm:

slapd (OpenLDAP Server - OpenLDAP standalone server): phần mềm này được dùng để tạo ra một standalone directory service và bao gồm cả slurpd replication server.
ldap-utils (OpenLDAP Utilities): gói này chứa các tiện ích dùng để truy cập LDAP server cục bộ hoặc từ xa (local or remote). ldap-utils cũng chứa tất cả các chương trình cần thiết (required client programs) để truy cập các LDAP server.
db4.2-util (Berkeley v4.2 Database Utility): gói này chứa các công cụ (tools) được dùng để thao tác (manipulating) với các cơ sở dữ liệu có định dạng là Berkeley v4.2 Database.
Các bước thực hiện như sau:

Cập nhật danh mục phần mềm (package list) trên Ubuntu và cài đặt OpenLDAP:
tthai@ubuntu-server:~$ sudo -i
[sudo] password for tthai:
root@ubuntu-server:~#
root@ubuntu-server:~# aptitude update
root@ubuntu-server:~# apt-get install slapd
root@ubuntu-server:~# apt-get install ldap-utils
root@ubuntu-server:~# apt-get install db4.2-util

Lưu ý: khi cài đặt các gói slapd, ldap-utils, db4.2-util, hệ thống cần sử dụng đĩa CD chứa Ubuntu server 7.10.
2. Cấu hình LDAP server

Chúng ta sẽ thao tác trên các file của OpenLDAP để cấu hình LDAP server. Các bước thực hiện như sau:

Sao chép dự phòng các file của OpenLDAP:
root@ubuntu-server:~# cp -R /etc/ldap /backup

Sử dụng tiện ích slappasswd để mã hóa mật khẩu admin và lưu chuỗi ký tự mã hóa vào cuối file /etc/ldap/slapd.conf:
root@ubuntu-server:~# slappasswd >> /etc/ldap/slapd.conf
New password:
Re-enter new password:

Cấu hình OpenLDAP:
Hiệu chỉnh file /etc/ldap/slapd.conf (file cấu hình chính của OpenLDAP) như sau:

root@ubuntu-server:~# vim /etc/ldap/slapd.conf
suffix “dc=bits,dc=com,dc=vn”
rootdn “cn=admin,dc=bits,dc=com,dc=vn”
# password này do tiện ích ldappasswd tạo ra.
rootpw {SSHA}AwiGYep3HmBbL5rQka4Bchd4g8ofhnXC
directory “/var/lib/ldap”

# Set change password permission
access to attrs=userPassword,shadowLastChange
by dn=”cn=admin,dc=bits,dc=com,dc=vn” write
by anonymous auth
by self write
by * none

# Ensure read access to the base for things like
# supportedSASLMechanisms.
access to dn.base=”" by * read

# The admin dn has full write access, everyone else can
# read everything.
access to *
by dn=”cn=admin,dc=bits,dc=com,dc=vn” write
by * read

Lưu ý: giữ lại những thiết lập mặc định của file /etc/ldap/slapd.conf không được đề cập ở trên.

Khởi chạy standalone LDAP server:
root@ubuntu-server:~# /etc/init.d/slapd start
Starting OpenLDAP: slapd

Đến bước này, LDAP server đã sẵn sàng. Để bắt đầu đưa server này vào hoạt động, chúng ta cần bổ sung các entry (thực thể - user, group, ou…) khởi tạo trên server.

Bổ sung các initial entry (thực thể khởi tạo):
LDAP server có thể bổ sung các entry bằng câu lệnh hoặc từ các file có định dạng ldif (ldap directory interchange format). Dưới đây, chúng ta tạo ra file init.ldif và lưu vào thư mục /etc/ldap.

root@ubuntu-server:~# vim /etc/ldap/init.ldif
dn: dc=bits,dc=com,dc=vn
objectClass: dcObject
objectClass: organizationalUnit
dc: bits
ou: bits.com.vn

dn: cn=admin,dc=bits,dc=com,dc=vn
objectClass: simpleSecurityObject
objectClass: organizationalRole
cn: admin
description: LDAP administrator
userPassword: {SSHA}AwiGYep3HmBbL5rQka4Bchd4g8ofhnXC

dn: ou=users,dc=bits,dc=com,dc=vn
objectClass: organizationalUnit
ou: users

dn: ou=groups,dc=bits,dc=com,dc=vn
objectClass: organizationalUnit
ou: groups

dn: cn=ktm,ou=groups,dc=bits,dc=com,dc=vn
objectClass: posixGroup
cn: ktm
gidNumber: 5000

Lưu ý: UID/GID trong bài viết này được thiết lập theo qui định sau:
o System account: UID < 500
o Real People in LDAP: 499 < UID < 10.000
o Local users, groups (not in LDAP): UID > 10.000
Thực hiện các bước như sau để bổ sung entry vào LDAP server:

Dừng dịch vụ LDAP:
root@ubuntu-server:~# /etc/init.d/slapd stop

Xóa nội dung đã tự động tạo ra trong khi cài đặt OpenLDAP:
root@ubuntu-server:~# rm -rf /var/lib/ldap/*

Bổ sung entry mới:
root@ubuntu-server:~# slapadd -l init.ldif

Hiệu chỉnh quyền trên cơ sở dữ liệu:
root@ubuntu-server:~# chown -R openldap:openldap /var/lib/ldap

Khởi chạy dịch vụ LDAP:
root@ubuntu-server:~# /etc/init.d/slapd start

Kiểm tra các entry vừa bổ sung:
Chúng ta có thể kiểm tra các entry vừa mới bổ sung vào bằng cách sử dụng tiện ích ldapsearch:

root@ubuntu-server:~# ldapsearch -xLLL -b “dc=bits,dc=com,dc=vn”

Trong đó:
o -x: không sử dụng phương thức thẩm định SASL (mặc định).
o -LLL: vô hiệu hoá việc in thông tin LDIF.
o -b: tìm kiếm cơ bản.
Nếu các thao tác bổ sung entry vào LDAP server được thực hiện một cách chính xác, tiện ích ldapsearch sẽ hiển thị thông tin về các entry này tương tự như nội dung đã tạo trong file /etc/init.ldif.
Với các bước cấu hình như trên, chúng ta đã hoàn thành thao tác cài đặt và cấu hình LDAP server trên máy tính ubuntu-server. Tiếp theo, chúng ta tiến hành các thao tác cài đặt và cấu hình các hệ thống máy trạm Ubuntu.

3.2. Cấu hình ubuntu-desktop01

Để máy trạm đăng nhập với tài khoản được tạo ra trên LDAP server, chúng ta cần thực hiện các bước cấu hình trên các file PAM (Pluggable Authentication Modules) và NSSWITCH (Name Service Switch) trong Ubuntu. Các bước thực hiện như sau:

1. Cài đặt LDAP client

Các phần mềm và tiện ích cần phải cài đặt trên máy trạm Ubuntu là:

libpam-ldap: thư viện dùng để cho phép xác thực (allow for authentication) qua LDAP.
libnss-ldap: thư viện dùng để cho phép truy vấn thông tin về các session (allow session information) qua LDAP.
nss-updatedb: tiện ích dùng để tạo ra một cơ sở dữ liệu tài khoản cục bộ (local database of the user names). Cơ sở dữ liệu này được dùng để khắc phục trường hợp mạng bị giảm tốc độ truy cập (network slowdown), hoặc bị ngưng hoạt động vì sự cố (outage).
Các bước thực hiện như sau:

Cập nhật danh mục phần mềm (package list) trên Ubuntu và cài đặt libpam-ldap, libnss-ldap và nss-updatedb:
ctbach@ubuntu-desktop01:~$ sudo -i
[sudo] password for ctbach:
root@ubuntu-desktop01:~#
root@ubuntu-desktop01:~# aptitude update
root@ubuntu-desktop01:~# apt-get install libpam-ldap

Khi cài đặt thư viện này, chúng ta cần cung cấp các thông số:
o LDAP Server Uniform Resource Identifier: ldap://192.168.10.2
o Distinguished name of the search base: dc=bits,dc=com,dc=vn
o LDAP version to use: 3
o LDAP account for root: cn=admin,dc=bits,dc=com,dc=vn
o LDAP root account password: ******
root@ubuntu-desktop01:~# apt-get install libnss-ldap
Khi cài đặt thư viện này, chúng ta cần cung cấp các thông số:

LDAP account for root: cn=admin,dc=bits,dc=com,dc=vn
LDAP root account password: ******
Chú ý: một hộp thoại xuất hiện, thông báo rằng hệ thống không thể quản lý file nsswitch.conf một cách tự động. Chúng ta nhấn nút OK và sẽ thay đổi cấu hình của file này ở phần sau.

root@ubuntu-desktop01:~# apt-get install nss-updatedb
2. Cấu hình LDAP client

Chúng ta sẽ thao tác trên các file của PAM và NSSWITCH để cấu hình LDAP client. Các bước thực hiện như sau:

Sao chép dự phòng các file của PAM và NSSWITCH:
root@ubuntu-desktop01:~# mkdir /backup
root@ubuntu-desktop01:~# cp /etc/nsswitch.conf /backup
root@ubuntu-desktop01:~# cp -R /etc/pam /backup

Cấu hình NSSWITCH:
Hiệu chỉnh file /etc/nsswitch.conf (file cấu hình chính của NSSWITCH). File này xác định các name service mà hệ thống sử dụng để truy vấn thông tin (search for information). File này cũng chỉ ra thứ thự của các name service để hệ thống ưu tiên tìm kiếm theo một thứ tự đã được lập ra.

root@ubuntu-desktop01:~# vim /etc/nsswitch.conf
passwd: files ldap
group: files ldap

Kiểm tra cấu hình vừa thiết lập bằng cách thực hiện 02 lệnh:

root@ubuntu-desktop01:~# getent passwd
root@ubuntu-desktop01:~# getent group

02 lệnh trên sẽ liệt kê mật khẩu và các nhóm trên Ubuntu desktop và trên LDAP server.

Cấu hình PAM:
Có 04 file cấu hình của PAM liên quan đến LDAP:

o /etc/pam.d/common-account
o /etc/pam.d/common-auth
o /etc/pam.d/common-password
o /etc/pam.d/common-session
Hiệu chỉnh các file này theo các bước như sau:
o root@ubuntu-desktop01:~# cd /etc/pam.d
o root@ubuntu-desktop01:/etc/pam.d# vim ./common-account
account sufficient pam_ldap.so
account required pam_unix.so
o root@ubuntu-desktop01:/etc/pam.d# vim ./common-auth
auth sufficient pam_ldap.so
auth required pam_unix.so nullok_secure use_first_pass
o root@ubuntu-desktop01:/etc/pam.d# vim ./common-password
password sufficient pam_ldap.so
password required pam_unix.so nullok obscure min=4 max=8 md5
o root@ubuntu-desktop01:/etc/pam.d# vim ./common-session
session required pam_unix.so
session required pam_mkhomedir.so skel=/etc/skel/
session optional pam_ldap.so
session optional pam_foreground.so

Tạo thư mục dùng để lưu trữ các thư mục home tương ứng với mỗi tài khoản đăng nhập vào máy trạm:
root@ubuntu-desktop01:~# mkdir /home/users
root@ubuntu-desktop01:~# mkdir /home/users/ktm
Chú ý: nếu không thực hiện bước này sau khi đã tạo tài khoản trên LDAP, chúng ta sẽ gặp thông báo lỗi trong quá trình đăng nhập vào máy trạm Ubuntu.
o “Authentication failed”. Nếu xem trong file /var/log/auth.log, chúng ta sẽ thấy nguyên nhân của lỗi: “Unable to create directory /home/users/ktm/tthai”; “couldn’t open session for tthai”.
3. Tạo tài khoản đăng nhập với phpLDAPadmin

Để đơn giản trong việc quản lý OpenLDAP server, chúng ta sử dụng phpLDAPadmin. Đây là ứng dụng web được sử dụng để thao tác với OpenLDAP server.

Các bước sau đây sẽ giúp chúng ta cài đặt và sử dụng phpLDAPadmin trên máy trạm Ubuntu để quản lý LDAP server.

Cài đặt phpLDAPadmin với lệnh:

root@ubuntu-desktop01:~# apt-get install phpldapadmin

Cấu hình phpLDAPadmin:

root@ubuntu-desktop01:~# cp -R /usr/share/phpldapadmin /var/www/myphpldapadmin
root@ubuntu-desktop01:~# cp /etc/phpldapadmin/config.php /etc/phpldapadmin/first.config.php
root@ubuntu-desktop01:~# rm /var/www/myphpldapadmin/config/config.php
root@ubuntu-desktop01:~# ln -s /etc/phpldapadmin/first.config.php /var/www/myphpldapadmin/config/config.php
root@ubuntu-desktop01:~# chmod +r /etc/phpldapadmin/first.config.php

Truy cập phpLDAPadmin:

Từ cửa sổ trình duyệt, nhập địa chỉ http://localhost/myphpldapadmin.

Nhấn vào nút Login ở panel bên trái, nhập thông tin tài khoản root:

Login DN: cn=admin,dc=bits,dc=com,dc=vn
Password: ******
Nhấn nút Authenticate để đăng nhập.

Nếu đăng nhập vào LDAP server thành công, hệ thống sẽ thông báo:

Tạo tài khoản trên phpLDAPadmin:

Kích vào mục ou=users, chọn Create new entry here, chọn User Account. Nhấn nút Process>>.

Điền thông tin liên quan đến tài khoản và nhấn nút Process>>.

Xem lại thông tin. Sau khi đã chắc chắn, nhấn nút Create Object.

Sau khi tạo xong, màn hình hiển thị thông tin của tài khoản vừa tạo sẽ xuất hiện.

Nhấn nút Add new attribute để thêm thuộc tính LoginShell.

Nhấn nút Add để hoàn thành thao tác tạo và hiệu chỉnh tài khoản. Đến bước này, chúng ta nhấn nút Logout và bắt đầu kiểm tra khả năng hoạt động của hệ thống LDAP trên Ubuntu.

3.3. Cấu hình ubuntu-desktop02

Thực hiện các bước tương tự như với máy tính ubuntu-desktop01.

4. Kiểm tra hệ thống

Để kiểm tra hệ thống sau khi hoàn thành các bước cấu hình, từ máy trạm ubuntu, chúng ta đăng nhập bằng tài khoản được tạo ra trên LDAP server. Trong trường hợp của mình, trên máy ubuntu-desktop01, sau khi hệ thống khởi động, chúng ta nhập:

Username: tthai
Password: ******
Hệ thống sẽ thông báo: “Creating directory ‘/home/users/ktm/tthai’”, chúng ta nhấn nút OK để hoàn thành thao tác đăng nhập.
Kết luận

Sử dụng LDAP để xây dựng mạng nội bộ theo mô hình client/server, với các máy tính Ubuntu là một giải pháp quản lý tập trung hiệu quả và tiết kiệm chi phí. Với các bước cài đặt đơn giản, cấu hình dễ dàng, việc thiết kế hệ thống mạng nội bộ với LDAP và Ubuntu là hoàn toàn khả thi.

Phụ lục 1 - Một số thao tác hữu ích khi cấu hình LDAP trên Ubuntu

1. Cấu hình máy tính Ubuntu để cho phép account trên LDAP server có thể chuyển sang (sudo) account quản trị hệ thống root

Để cho phép account tthai trên LDAP server có thể chuyển sang account root, trên máy trạm Ubuntu, chúng ta thực hiện như sau:
Mở file /etc/group, bổ sung user01 vào dòng admin…

# gedit /etc/group

Tìm đến dòng admin:x:117:ctbach,administrator

Bổ sung user01 vào cuối dòng. Sau khi bổ sung, chúng ta nhận được kết quả tương tự như sau:

admin:x:117:ctbach,administrator,tthai

Tiếp đến, cần cập nhật password LDAP server để hệ thống Ubuntu có thể hiểu được password này:

root@ubuntu-server:~# passwd tthai
Enter login (LDAP) password: ******
New password: ******
Re-enter new password: ******
2. Sử dụng đĩa USB trên Ubuntu server

Để sử dụng được các đĩa USB trên Ubuntu server (giao diện dòng lệnh), chúng ta phải thực hiện thao tác mount đĩa USB vào Ubuntu server.

Đối với đĩa USB thông thường (không có MP3):
root@ubuntu-server:~# mkdir /usb-disk
root@ubuntu-server:~# mount -t vfat /dev/sdb1 /usb-disk

Đối với đĩa USB có tính năng nghe nhạc MP3:
root@ubuntu-server:~# mkdir /usbmp3-disk
root@ubuntu-server:~# mount -t vfat /dev/sdb /usbmp3-disk

Khi đã sử dụng xong, chúng ta nên ngắt kết nối giữa Ubuntu server và đĩa USB một cách an toàn bằng cách:
root@ubuntu-server:~# umount /usb-disk
root@ubuntu-server:~# umount /usbmp3-disk
3. Xem lỗi đăng nhập trên máy trạm Ubuntu

Để xem được các lỗi đăng nhập trên máy trạm Ubuntu nhằm giúp chúng ta xác định nguyên nhân phát sinh lỗi trong quá trình Ubuntu đăng nhập qua LDAP, chúng ta mở file /var/log/auth.log

Tài liệu tham khảo

1. OpenLDAP Server
https://help.ubuntu.com/community/OpenLDAPServer

2. LDAP Client Authentication
https://help.ubuntu.com/community/LDAPClientAuthentication

3. OpenLDAP Client Configuration Guide
http://ubuntuforums.org/showthread.php?t=597056

4. Ubuntu User Document (good)
https://help.ubuntu.com/community/UserDocumentation

5. DNS Server Setup Using Bind in Ubuntu
http://www.ubuntugeek.com/dns-server-setup-using-bind-in-ubuntu.html

6. BIND9 Administrator Reference Manual
http://www.isc.org/index.pl?/sw/bind/index.php

7. Installing phpLDAPadmin
https://help.ubuntu.com/community/InstallingphpLDAPadmin

8. An Introduction to LDAP
http://www.ldapman.org/articles/intro_to_ldap.html

9. Introduction to LDAP (good)
http://quark.humbug.org.uau/publications/ldap/ldap_tut.html

10. LDAP mini HOWTO (good)
http://www.grennan.com/ldap_HOWTO.html

11. OpenLDAP 2.2 Administrator’s Guide
http://www.bind9.net/manual/openldap/2.2/index.html

12. OpenLDAP Everywhere
http://www.linuxjournal.com/article/6266

13. LDAP Attributes
http://www.computerperformance.co.uk/Logon/LDAP_attributes_active_directory.htm

14. Berkeley v4.2 Database Utility
http://packages.ubuntu.com/feisty/utils/db4.2.-util

15. Berkeley Database
http://packages.ubuntu.com/edgy/doc/db3-doc

16. Berkeley Database
http://directory.fsf.org/project/BerkeleyDB/

17. Performing Backup and Recovery with Berkeley DB
http://packages.ubuntu.com/edgy/doc/db3-doc

18. Chapter 19. I/O Redirection (Advanced Bash - Scripting Guide)
http://tldp.org/LDP/abs/html/io-redirection.html

19. /etc/nsswitch.conf — Name Service Switch File
http://www.softpanorama.org/Solaris/Reference/etc/nsswitch.shtml

LinuxCBT Samba Edition

2008-07-20T09:57:00.003+07:00

LinuxCBT Samba Edition focuses on the Samba suite of clients and servers and Windows integration

Samba is the de-facto UNIX/Linux-based software for seamlessly integrating UNIX/Linux environments with MS Windows networks via Samba's implementation of the SMB protocol suite. Samba allows your UNIX/Linux system to emulate a Windows workstation/server in the network neighborhood/my network places browse list. Consequently, your UNIX/Linux-based system appears to be a Windows-based system featuring file & print shares. Additionally, Samba adds many features not included with stock MS Windows systems.

Let LinuxCBT Samba Edition help to solidify your understanding of Samba and ancillary components.

Recommended Prerequisites:

* Familiarity with MS Windows networking (File & Print shares)
* Access to a GNU/Linux-based PC to install Samba and ancillary components used
* Access to a MS Windows-based system connected to the same network

LinuxCBT Samba Edition - Disc 1

* Introduction to Samba & Clients

o

o Explore Samba server configuration
o Identify key Samba packages & contents
o Explore the SMB workgroup implementation
o Discuss the roles of Local Master Browsers (LMBs) & Domain Master Browsers (DMBs)
o Use findsmb & smbclient to reveal the active browse lists
o Discuss NETBIOS naming rules
o Identify system broadcast address & discuss broadcast-based NETBIOS name resolution
o Identify & discuss the roles of the key Samba daemons
o Use smbtree to enumerate the active workgroups, hosts & file & print shares
o Install rdesktop client for remote desktop connectivity to Windows 2003 Server
o Explore browse list & SMB clients from Windows 2003
o Share file resource on Windows 2003 Server for use by Samba clients
o Join common workgroup from Windows 2003 host
o Use smbclient to enumerate & connect to shared resources on XP/2003 hosts
o Explore anonymous and authenticated share enumeration using smbclient
o Transfer files between Samba and Windows 2003 hosts using smbclient
o Use smbget to download files non-interactively from remote SMB server
o Use smbclient with credentials stored in a hidden file
o Create tarball archive using tar & discuss Samba's smbtar utility
o Create tar-compatible archives of remote SMB-share using smbtar
*
* Samba File System (SMBFS) Integration
o Discuss the features & benefits of SMBFS
o Identify package & files
o Create temporary mount point for remote SMB share
o Mount remote SMB share into local Linux file system using SMBFS
o Examine resultant Linux file-system permissions post SMBFS mount
o Transfer files to mount point (Remote Windows 2003 system) & examine results
o Identify SMBFS process footprint
o Mount remote SMB share with previously-defined hidden credentials file
o Modify system startup file to facillitate automatic SMBFS mounts upon system restart
*
* Workgroup & Windows Internet Naming System (WINS) Integration
o Identify key Samba configuration file & package membership
o Use findsmb to reveal available workgroups
o Alter Samba configuration file to join available workgroup
o Identify key TCP/UDP ports used by key Samba daemons
o Use findsmb & browse list to confirm workgroup membership
o Enumerate default Samba shares on primary Linux system using smbclient
o Introduction to smbpasswd utility and database
o Use smbpasswd to add Windows user to database & confirm authentication from Windows host
o Install WINS Server on Windows 2003 Server for use by SMB-clients
o Explain default Samba NETBIOS name resolution order
o Identify name resolution order directive in primary Samba configuration file
o Configure Samba server to be a WINS client via Samba configuration file
o Confirm WINS NETBIOS registrations of Samba & Windows hosts
*
* Samba Share-Level File & Print Security Implementation
o Discuss Samba's security modes
o Discuss the features & benefits of share-level security
o Alter primary Samba configuration file to support share-level security
o Define and publish a public read-only share
o Reload key Samba daemons & confirm connectivity to read-only share
o Enumerate & connect to public read-only share from a remote Samba client
o Define & publish an anonymous read-write share
o Use chmod & chown to define appropriate permissions and ownership on the directory
o Confirm the ability to write to read-write share from remote Windows 2003 system
o Examine applied permissions & ownership of created objects on the Linux file system
o Define & publish a private read-write share
o Confirm authentication to private read-write share from remote Windows 2003 host
o Update Samba back-end database to reflect new user - test connectivity
o Compare & contrast Windows & Samba hidden share definition
o Define hidden share & explore browse list from Samba & Windows hosts
o Convert existing shares to hidden shares and examine updated browse list
o Discuss default Samba print sharing implementation
o Explore Common UNIX Printing System (CUPS) interface
o Install and configure a printer
o Discuss various CUPS back-end capabilities
o Discuss the CUPS-generated printcap file
o Explore key Samba print-related configuration directives
o Share the printer using Samba
o Connect to printer from Windows host and test printing
*
* Samba Web Administration Tool (SWAT)
o Discuss the features & benefits of Samba SWAT
o Explore XINETD system configuration for the presence of Samba SWAT
o Install Samba SWAT from the local package repository
o Update XINETD configuration to enable Samba SWAT & confirm TCP listener
o Authenticate to Samba SWAT as non-privileged and privileged users
o Examine current smbd & nmbd connections
o Explore & discuss the key tools included with Samba
o Correlate Samba's primary configuration file to Samba SWAT's web interface
o Discuss the key directives in the global section of the Samba SWAT web interface
o Discuss additional directives in the advanced view of the Samba SWAT global area
o Adjust the OS Level and examine the changes to the role in the browse list
o Discuss Samba WINS server rules & limitations
o Explore shares configuration
o Correlate shares section of main config file to Samba SWAT's shares interface
o Discuss the effects of various share directives
o Discuss the variable homes share and its applications
o Explain Samba's create mask directive & examine its application
o Examine the advanced Samba SWAT shares view & discuss key directives
o Define valid & invalid users per share & test connectivity from remote Windows host
o Force ownership of file & directory objects using the force user directive
o Explore & discuss advanced printer share directives
o Define multiple NETBIOS names and view results in the browse list
*
* Samba User-Level Security Mode
o Explain the advantages and features of user-level security
o Discuss the user-accounts back-ends supported by Samba
o Convert Samba from share-level to user-level security mode
o Test user-level connectivity to Samba shares/services
o Discuss IPC$ connections and applications
o Explore passwd & shadow user-accounts databases
o Explore the smbpasswd database
*
* Samba - Active Directory (AD) - BIND Integration
o Discuss the DNS requirements of Active Directory
o Install BIND from RPM repository
o Configure BIND as a caching-only name server
o Define usable BIND named.conf configuration file with appropriate zones
o
o Define required Active Directory dynamically updateable zones
o Install Active Directory on Windows server
o Confirm BIND DNS connectivity
o Configure Kerberos to support Active Directory Realm & test connectivity
o Convert Samba from basic user-level to ADS security mode
o Use the net command to create Samba machine account in the Active Directory
o Confirm authentication against Active Directory when accessing resources
o Create AD -> Linux corresponding users for transparent access
*
* Samba - Winbindd
o Discuss the features & advantages of Winbind
o Discuss the accounts resolutions process
o Alter the name server switch process to facilitate winbind
o Discuss UNIX/Linux uids & gids
o Explain the application of idmaps - uids & gids
o Configure Samba to use Winbind
o Enumerate remote Active Directory users using wbinfo & getent
o Examine auto-assigned uids & gids via idmap
o Connect to Samba server using Active Directory users & Winbind
o Configure SSHD to support Winbind-provided users from Active Directory
o Configure Winbind to use the default Active Directory domain for authentication
o Configure VSFTPD to use the default Active Directory domain for authentication
*
* Samba - Linux File System & Share/Service Permissions
o Explain how Samba interacts with file-system permissions
o Explain UNIX/Linux file-system permissions - UGO
o Use chown/chmod to adjust file-system permissions
o Discuss the applicable Samba share/service permissions directives
o Apply various share/service permissions & test results
*
* Samba - Miscellaneous
o Create share/service with appropriate permissions for collaborations
o Examine collaborative permission from Windows client
o Configure Samba as a WINS server & discuss capabilities
o Configure Samba a print server for SMB(Windows/Linux/UNIX) clients
o Explore Samba logging
o Mount remote CIFS shares into the Linux file system
o Share mounted CIFS directories using Samba

Links

http://rapidshare.com/files/130789442/LinuxCBT_Samba_1_Tahaa.exe
http://rapidshare.com/files/130790250/LinuxCBT_Samba_2_Tahaa.rar
http://rapidshare.com/files/130791023/LinuxCBT_Samba_3_Tahaa.rar
http://rapidshare.com/files/130791796/LinuxCBT_Samba_4_Tahaa.rar
http://rapidshare.com/files/130792604/LinuxCBT_Samba_5_Tahaa.rar
http://rapidshare.com/files/130793404/LinuxCBT_Samba_6_Tahaa.rar
http://rapidshare.com/files/130858386/LinuxCBT_Samba_7_Tahaa.rar
http://rapidshare.com/files/130855668/LinuxCBT_Samba_8_Tahaa.rar

Multicast IP

2008-07-05T11:38:00.002+07:00

224.0.0.1 Tất cả các host trên cùng subnet này
224.0.0.2 Tất cả các Router trên cùng subnet này
224.0.0.5 Tất cả Router chạy OSPF
224.0.0.6 OSPF designated routers
224.0.0.9 RIP version 2 routers
224.0.0.10 EIGRP routers
224.0.1.39 Cisco-RP-Announce
224.0.1.40 Cisco-RP-Discovery

Pass4sure BCMSN 642-812v9.93

2008-07-02T09:20:00.002+07:00

http://rapidshare.com/files/84662654/642-812v2.93.rar.html

CCNP full packages

2008-06-30T09:07:00.002+07:00

In this package include all resources needed for you learn and practice to get CCNP certify. Join, download and have fun.

Links
http://rapidshare.com/files/125458765/CCNP.part1.rar
http://rapidshare.com/files/125458732/CCNP.part2.rar
http://rapidshare.com/files/125458731/CCNP.part3.rar
http://rapidshare.com/files/125479009/CCNP.part4.rar
http://rapidshare.com/files/125479019/CCNP.part5.rar

MPLS series ebooks

2008-06-28T02:25:00.003+07:00

A series book of MPLS, if you are interested them, download and read it, have fun.

http://rapidshare.com/files/125411285/MPLS.part1.rar
http://rapidshare.com/files/125411331/MPLS.part2.rar
http://rapidshare.com/files/125426921/MPLS.part3.rar

CCNA 2008 640-802

2008-06-25T00:33:00.002+07:00

http://rapidshare.com/files/124063382/CCNA.part1.rar
http://rapidshare.com/files/124063665/CCNA.part2.rar
http://rapidshare.com/files/124072079/CCNA.part3.rar
http://rapidshare.com/files/124072362/CCNA.part4.rar
http://rapidshare.com/files/124100942/CCNA.part5.rar

Giải thuật chống loop Spanning tree ( STP)

2008-06-22T06:16:00.002+07:00

Để tránh xảy ra hiện tượng loop, các SW sẽ tiến hành bầu chọn ra một SW có nhiệm vụ quản lý, cơ chế này gọi là STP.
Bầu chọn Root Bridge
Việc bầu chọn Root Bridge dựa vào hai yếu tố theo thứ tự sau:
Bridge Priority : nếu Bridge nào có priority thấp nhất sẽ được chọn làm root. Nếu các Bridge có priority bằng nhau, thì tiến hành chọn lựa dựa vào địa chỉ MAC
Địa chỉ MAC: Bridge nào có MAC thấp hơn thì sẽ được chọn làm root. Đây là trường hợp cuối cùng trong việc chọn root vì không có trường hợp các Bridge có địa chỉ MAC giống nhau. Thông số priority có thể được thay đổi:
Switch(config)#spanning-tree vlan vlan-id priority bridge-priority
Thông số priority nằm trong khoảng từ 0 à 65535, và giá trị mặc định là 32768.
Ta cũng có thể lựa chọn root trực tiếp bằng lệnh:
Switch(config)#spanning-tree vlan vlan-id root {primary secondary}
[diameter diameter]
+ primary : sẽ chọn bridge làm root, khi chọn thông số này nếu priority của Root Bridge nhỏ hơn 24567 thì Bridge này sẽ thiết lập priority của nó nhỏ hơn so với priority của root hiện tại một lượng là 4096, và dĩ nhiên bridge này sẽ là root. Còn nếu priority của Root Bridge lớn hơn 24567, bridge sẽ thiết lập priority của nó là 24567.
+ secondary : lựa chọn bridge làm root thứ hai.
+ diameter: số lượng bridge nối tầng, tối đa là 7.
Bầu chọn Root
PortRoot Port : Port thuộc Nonroot Bridge nối về Root Bridge sao cho chi phí nối về là thấp nhất. Root Port được bầu chọn dựa vào thông số Root Path Cost. Path cost được xem như là chi phí của liên kết, tỉ lệ với băng thông của liên kết. Thông số này có thể được cấu hình bằng dòng lệnh.
Switch(config-if)#spanning-tree vlan vlan-id cost cost
Port nào có tổng số path cost về root là thấp nhất sẽ được lựa chọn làm root port.
Bầu chọn Designated Port (DP):Trong trường hợp có hai hay nhiều bridge nối vào chung một mạng (xem hình ở phần bridge loop) sẽ xảy ra trường hợp loop. Để khắc phục thì các bridge có port nối vào mạng sẽ tiến hành lựa chọn designated port. Port này có vai trò quan trọng vì nó có nhiệm vụ chuyển các gói tin đi trong mạng. Việc chọn lựa dựa vào các thông số theo trình tự:
Dựa vào Root Path Cost : port nào có Root Path Cost thấp nhất sẽ được chọn làm DP. Trong trường hợp Root Path Cost bằng nhau, thì chọn dựa vào Bridge ID
Bridge ID : port thuộc bridge nào có Bridge ID thấp hơn sẽ được chọn làm DP. Nếu thông số này cũng giống nào thì chọn dựa vào địa chỉ MACĐịa chỉ MAC : port thuộc bridge nào có địa chỉ MAC thấp hơn sẽ được chọn làm DP

Cấu hình Load balancing với HSRP và VRRP

2008-06-22T06:13:00.001+07:00

Các IP host có thể có vài cách thức khác nhau để quyết định một router nào là router mặc định hoặc là default gateway. Ví dụ DHCP, BootP, ICMP Router Discovery protocol IRDP, cấu hình bằng tay hoặc ngay cả bằng cách dùng một giao thức định tuyến động. Hai cách thức phổ biến nhất là dùng DHCP và thông qua cấu hình bằng tay sẽ giúp cho host có địa chỉ IP của gateway của nó. Giao thức HSRP, VRRP và GLBP tượng trưng cho một số công cụ tốt nhất để khắc phục các vấn đề liên quan đến việc một host chỉ biết một địa chỉ như là đường đi duy nhất của nó ra khỏi subnet. Các giao thức này giúp giải quyết vấn đề dự phòng cho defaultgateway trong một mạng IP.HSRP cho phép nhiều router cùng chia sẽ một địa chỉ IP ảo và các địa chỉ MAC sao cho các máy của người dùng cuối sẽ không nhận ra khi nào có sự cố mạng xảy ra. Một vài đặc điểm chủ chốt của HSRP là:
· Địa chỉ IP là ảo và địa chỉ MAC cũng ảo trên router master.
· Các router dự phòng sẽ lắng nghe các gói hello từ router đang active, mặc định mỗi 3 giây và 10 giây cho khoảng thời gian dead.
· Độ ưu tiên cao nhất (mặc định là 100, trong tầm từ 1-255) sẽ xác định router, với cơ chế pre-emption bị tắt.
· Hỗ trợ tính năng tracking, trong đó độ ưu tiên của một router sẽ bị giảm khi một interface đang bị theo dõi bị hỏng hóc.
· Có thể có tối đa 255 nhóm HSRP trên mỗi interface, cho phép một hình thức cân bằng tải.
· Địa chỉ MAC ảo có dạng 0000.0C07.Acxx trong đó xx là chỉ số của nhóm HSRP.
· Địa chỉ của IP ảo phải trong cùng giá trị subnet của cổng của router trong LAN.
· Địa chỉ của IP ảo phải khác với bất kỳ một địa chỉ thật nào của các cổng tham gia vào HSRP.
· HSRP là một giao thức độc quyền của Cisco. VRRP là một giao thức thực hịên cùng một chức năng.
VRRP có vài sự khác biệt sau so với HSRP: VRRP dùng địa chỉ multicast là 0000.5E00.01xx trong đó xx là dạng hex của chỉ số nhóm của VRRP. VRRP không hỗ trợ tính năng theo dõi cổng. Trong Cisco IOS 12.2T/12.3, mặc định VRRP dùng cơ chế pre-emption nhưng HSRP thì mặc định dùng non pre-empt. Thuật ngữ master trong VRRP có cùng nghĩa với thuật ngữ Active của HSRP. Cấu hình cơ bản HSRPHSRP bầu chọn dựa vào Priority(0 đến 225), Router có priority sẽ được chọn làm active, nếu priority bằng nhau thì router nào có điạ chỉ IP trên interface HSRP cao hơn sẽ được chọn làm active. Đặt độ ưu tiên bằng câu lệnh:Router(config-if)#standby group priority priority Thông thường thì khi một Router đã là active trong HSRP rồi thì cho dù Router mới có Priority cao hơn cũng không được chọn làm active, tuy nhiên ta có thể cho phép router có priority cao làm active với bất kỳ lúc nào bằng cách chuyển sang chế độ preempt:Router(config-if)#standby group preemptDo các router chạy HSRP không tự động nhận biết được khi nào thì các gói của user không còn đi ra bên ngoài được thông qua nó nữa do đó mà ta phải cấu hình để nhận biết được, khi nào thì một giao tiếp của HSRP router bị down không còn khả năng chuyển lưu lượng cho user nữa thì nó sẽ tự động giảm priority của nó xuống.Router(config-if)#standby group track type mod/num decrementvalueDecrementvalue là giá trị của Priority phải giảm xuống khi track thấy một interface nào đó bị down. Mỗi cỗng giao tiếp của HSRP của router sẽ có một địa chỉ IP riêng. Tuy nhiên các Host sẽ thấy router qua một dịa chỉ ảo khác đó là Virtual router address.Router(config-if)#standby group ip ip-address Cấu hình Load balancing với HSRPVới cấu hình loại này, giả sử ta có hai router chay HSRP. Ta tạo ra hai group và hai địạ chỉ IP ảo cho hai group này. Router1 có Priority lớn đối với group thứ nhất và có Priority nhỏ hơn đối với Group thứ hai. Do đó Router 1 sẽ là active cho group 1 và sẽ là Standby cho group 2. Đối với các host thì ta sẽ cấu hình cho một số host có default gateway là Virtual IP address của group 1 và một số host có default gateway là Virtual IP address của group 2. Do đó mà tải sẽ cân bằng ở 2 router. Mỗi router sẽ đảm nhiệm một lượng tải nhất định.

Bài viết này nhằm phân biệt các loại STP

2008-06-22T06:09:00.002+07:00

Tạm thời , có thể chia ra các loại sau :
- CST
- PVST
- PVST+
- MST ( IEEE 802.1s)
- IST- STP ( dạng truyền thống 802.1d )
- RSTP ( IEEE 802.1w)
1 .CST : Common Spanning Tree .
Ta đã biết IEEE 802.1q không chỉ định nghĩa làm sao mà các vlan có thể trunking qua các switch , nó còn chỉ ra rằng chỉ có một tiến trình STP duy nhất chạy trên toàn bộ các vlan mà thôi . Và tiến trình duy nhất này người ta gọi tên là CST . Tất cả các CST BPDUs được vận chuyển trên đường trunk bằng native vlan với các untagged frame . Việc chạy duy nhất một tiến trình STP có lợi ở chỗ nó không tiêu tốn nhiều khả năng xử lí của CPU khi phải tính toán lại STP topology , cũng như làm cho công việc cấu hình của chúng ta trở nên đơn giản . Tuy nhiên , nó hạn chế ở chỗ sẽ không cho phép sẽ đề cập ở các trangàload balancing được thực hiện ( layer 2 loadbalancing dưới ) .
2 . PVST : per VLan Spanning Tree . Đây là một version độc quyền của Cisco , cho phép hoạt động linh hoạt hơn CST . Mỗi vlan sẽ chạy một tiến trình STP riêng biệt và không bị phụ thuộc lẫn nhau . Ưu điểm : làm giảm kích thước của STP topology , chia ra làm các topology nhỏ hơn , dẫn đến thời gian converge của STP giảm xuông . Thêm vào đó , nó còn cung cấp thêm khả năng load balancing . Khuyết điểm : sử dụng nhiều tài nguyên của CPU trong việc quản lí nhiều vlan . PVST sử dụng ISL trunking nên đối với một mạng tồn tại 2 dạng STP là PVST và CST thì sẽ dẫn đến không tương thích về mặt trunking .( CST xài dot1q ) . Do đó BPDUs sẽ không được quảng bá giữa 2 loại STP này .
3 . PVST+ : per Vlan Spanning Tree Plus Cisco tung ra một version khác của STP là PVST+ nhằm giải quyết vấn đề tương thích giữa CST và PVST . PVST+ đảm nhiệm vai trò như là một translator giữa PVST và CST . PVST+ có thể giao tiếp với PVST qua kết nối ISL trunking , ngược lại PVST+ có thể giao tiếp với CST qua kết nối dot1q trunking . Tại biên giới của PVST và PVST+ sẽ diễn ra việc mapping STP one-to-one . Tại biên giới của PVST+ và CST sẽ diễn ra việc mapping giữa một STP của CST và một PVST trong PVST+ ( STP trong CST chỉ có một mà thôi ) . http://tinypic.com/f24o76.jpgTrong hình trên có một kí hiệu là MST , nhưng MST ở đây không phải là Multiple Spanning tree mà là Mono Spanning tree . Ta có thể hiểu MST trong trường hợp này đồng nghĩa với lại CST .
4 . MST : Multiple Spanning Tree . Trong hầu hết các network , một switch đều có kết nối dự phòng tới switch khác . Ví dụ một access-layer switch sẽ có 2 kết nối uplink đến 2 distribution / core switch khác nhau . Khi STP hoạt động ở dạng CST thì chỉ có một kết nối là forwarding và kết nối kia rơi vào trạng thái blocking . Như vậy chúng ta đã lãng phí mất một kết nối . Chúng ta sẽ sắp xếp làm sao đó để sử dụng đồng thời 2 kết nối trên nhằm mục đích load balancing . PVST+ có vẻ là một lựa chọn hấp dẫn , vì nó cho phép các vlan khác nhau tạo ra những loop-free topology khác nhau và chạy trên các đường uplink khác nhau . Tuy nhiên , nếu số lượng Vlan tăng lên , đồng nghĩa với việc xuất hiện nhiều STP instance hơn sẽ làm cho CPU tiêu tốn nhiều resource hơn . Nghĩ xa hơn , ví dụ chúng ta có 100 Vlan tương ứng chúng ta cũng sẽ có 100 loop-free topology . Nhưng 100 topology này có một điểm chung là đều đi qua một trong 2 kết nối uplink .http://tinypic.com/f24obo.jpgTrong hình trên , có 2 STP instance , mỗi instance chạy cho một vlan . Topology cho mỗi instance là độc lập và được chỉ ra như hình vẽ . Vlan A có thể chọn đường uplink bên trái để đi , và blocking đường uplink bên phải . Tương tự , Vlan B có thể chọn đường uplink bên phải để đi và blocking đường uplink bên trái . Như vậy cả 2 đường uplink đều được sử dụng , load balancing đã được thực hiện . Không loại trừ trường hợp cả vlan A và Vlan B đều tính toán và chọn ra đi một đuờng uplink duy nhất ( ví dụ đường uplink bên phải ) . Tuy nhiên chúng ta sẽ phải can thiệp vào quá trình tính toán của chúng bằng cách cấu hình sao cho cả 2 đường đều được sử dụng . Cũng với hình này , nếu chúng ta có 100 vlan thì topology của các instance tính toán được cũng chỉ đi qua một trong 2 kết nối uplink mà thôi . Như vậy việc sử dụng tới 100 STP instance trong khi topology thì chỉ đi qua một trong 2 đường uplink sẽ làm tiêu tốn rất nhiều resource của CPU . Ta sẽ hạn chế số instance lại bằng cách cho instance thứ nhất chạy cho 1 range vlan ( ví dụ từ 1-50 ) , instance thứ 2 chạy cho range vlan từ 51-100 . Chúng ta đã hạn chế được số lượng instance đồng thời vẫn đảm bảo cho load balancing hoạt động . Ví dụ cấu hình load balancing : http://tinypic.com/f24oib.jpgTa sẽ cấu hình sao cho range vlan 3-6 sẽ lấy đường trunk 2 làm forwarding và trunk 1 là blocking . Trong khi đó , range vlan 8-10 sẽ lấy đường trunk 1 làm forwarding và trunk 2 lại là blocking . Nếu một trong 2 kết nối trunk 1 hoặc trunk 2 bị down , toàn bộ traffice trong cả 2 range vlan đều dồn về một phía và chạy . Có thể cấu hình bằng cách gán priority như hình vẽ . Đoạn trên đã mô tả khái niệm của MST . Như vậy MST được xây dựng dựa trên việc mapping một hay nhiều vlan vào một STP instance . Khi triển khai MST , chúng ta cân chú ý những điều sau đây : - Số lượng Instance cần phải dùng là bao nhiêu - Range vlan cần map cho mỗi instance là gì . Để hiểu được các khái niệm kế tiếp , chúng ta cần phải nắm được MST region là gì ? Để switch có thể tham gia vào một MST instance thì nó phải được cấu hình với các thông số nhất quán với nhau . Các thông số này bao gồm MST region , revision number , và MST Vlan map . Tập hợp các switch có cấu hình MST giống nhau tạo thành MST region .
5 . IST , CIST , CST :CST chạy trên toàn bộ domain , CST coi các MST region như là một “ big switch “ tham gia vao CST instance . CST lúc này sẽ tạo ra một loop-free topology cho các MST region . Trong mỗi MST region cũng cần phải có các sub STP instance để tạo ra một sub loop-free tree . Các instance chạy trong một MST region gọi là các MSTIs . Và các MSTIs này được quản lí bởi một IST instance . Trong MST , thì IST được coi như là một locally CST trong MST đó . Các MSTIs được đánh số từ 0-15 . Trong đó , MSTIs 0 ( instance 0 ) chính là IST . IST đại diện cho toàn bộ MST region để giao tiếp với các MST region khác . Chỉ có IST instance là cho phép gửi và nhận các MST BPDUs . Thông tin của các MSTIs khác được đưa vào BPDUs với giá trị M record . Mặc dù MST region có thể có tới 16 MSTIs cùng chạy nhưng chỉ có một BPDUs là mang thông tin của chúng đi . MSTIs chỉ có ý nghĩa cục bộ trong một MST region mà thôi . Nếu MST region 1 có MSTI 2 , MST region 2 cũng có một MSTI được đánh số là 2 thì cũng không hề bị ảnh hưởng . Nếu một MST region kết nối với một PVST+ switch thì nó sẽ nhận biết ngay được điều này bằng cách kiểm tra BPDUs . Nếu BPDUs được nghe thấy từ nhiều VLAN , nghĩa là neighbor đang chạy PVST+ . Khi MST region gửi BPDUs cho PVST+ switch nó se replicate IST BPDUs cho mỗi Vlan trong PVST+ . CIST là một tập hợp các MSTIs trong một MST region . IST trong một MST region lúc converge sẽ tạo ra một IST master ( CIST regional Root ) của region đó . Sau đó các CIST regional root nay sẽ tiếp tục được gửi ra ngoài một Region để tiếp tục đọ sức với các CIST regional root khác . Kết quả của các cuộc đọ sức này là tạo nên được một CST root . http://tinypic.com/f24okk.jpg

Dynamips Full tool

2008-06-22T05:48:00.002+07:00

Bạn nên cài đặt theo các bước sau :
1) Wincap
2) Dynamip
Sau đây là những công cụ hỗ trợ cho bạn khi thực hiện giả lập Router và Switch
TFTPServer1-1-980730 : Đây là chương trình làm TFTP , dùng để giao tiếp với thiết bị Cisco. Như backup và Restore.
IOS
+ c3725-adventerprisek9-mz.124-15.T5 : dùng để giả lập Switch
+ 3660 và 3640 : dùng để giả lập router
putty là chương trình Hyper Terminal
dynagen final là sách hướng dẫn sử dụng dynamips
Tất cả những chương trình có trong link sau :
http://rapidshare.com/files/124110298/dynamips.rar.html

All Cisco Press Ebook Series

2008-06-22T00:35:00.003+07:00

Cisco.Press.ACS.User.Guide.pdf
Cisco.Press.Advanced.MPLS.Design.pdf
Cisco.Press.ASA.All-in-One Firewall.IPS.and.VPN.Adaptive.Security.Appliance.chm
Cisco.Press.ASA.and.PIX.Firewall.Handbook.chm
Cisco.Press.Authorized.Self-Study.Guide.Cisco.Voice.over.IP.CVOICE.chm
Cisco.Press.Catalyst.QoS.in.Campus.Networks.chm
Cisco.Press.CCSP.IPS.Exam.Certification.Guide.pdf
Cisco.Press.CCSP.SNRS.Exam.Certification.Guide.pdf
Cisco.Press.Configuring.BGP.StudentGuide.v.3.2.Vol.1.pdf
Cisco.Press.Configuring.BGP.StudentGuide.v.3.2.Vol.2.pdf
Cisco.Press.Content.Networking.Fundamentals.chm
Cisco.Press.DQOS.Exam.Certification.Guide.pdf
Cisco.Press.Firewall.Fundamentals.Jun.2006.pdf
Cisco.Press.Frame.Relay.Solutions.Guide.chm
Cisco.Press.Internetworking.Troubleshooting.Handbook.pdf
Cisco.Press.Intrusion.Prevention.Fundamentals.chm
Cisco.Press.LAN.Switching.First.Step.chm
Cisco.Press.LAN.Switching.Fundamentals.chm
Cisco.Press.MPLS.and.Next.Generation.Networks.chm
Cisco.Press.MPLS.and.Next.Generation.Networks.pdf
Cisco.Press.MPLS.Configuration.On.Cisco.IOS.Software.chm
Cisco.Press.MPLS.Fundamentals.pdf
Cisco.Press.MPLS.Implementing.Cisco.MPLS.v.2.1.Vol.1.pdf
Cisco.Press.MPLS.Implementing.Cisco.MPLS.v.2.1.Vol.2.pdf
Cisco.Press.MPLS.VPN.Security.chm
Cisco.Press.NAC.Appliance.Aug.2007.pdf
Cisco.Press.Network.Security.Fundamentals.chm
Cisco.Press.Network.Virtualization.chm
Cisco.Press.Next.Generation.Network.Services.chm
Cisco.Press.PacketCable.Implementation.Feb.2007.chm
Cisco.Press.Router.Firewall.Security.chm
Cisco.Press.Routing.First-Step.chm
Cisco.Press.SCND.StudentGuide.v.2.0.Vol.1.pdf
Cisco.Press.SCND.StudentGuide.v.2.0.Vol.2.pdf
Cisco.Press.Security.Threat.Mitigation.and.Response.chm
Cisco.Press.Selecting.MPLS.VPN.Services.chm
Cisco.Press.SNPA.v.4.0.Vol.1.pdf
Cisco.Press.SNRS.LabGuide.v2.0.pdf
Cisco.Press.SNRS.StudentGuide.v2.0.Vol1.pdf
Cisco.Press.SNRS.StudentGuide.v2.0.Vol2.pdf
Cisco.Press.SNRS.StudentGuide.v2.0.Vol3.pdf
Cisco.Press.Storage.Networking.Protocol.Fundamentals.chm
Cisco.Press.TCP.IP.First-Step.chm
Cisco.Press.Top-Down.Network.Design.2nd.Edition.pdf
Cisco.Press.Understanding.Cisco.Security.MARS.chm
Cisco.Press.User.Guide.for.Cisco.Security.MARS.pdf
Cisco.Press.Voice.Gateways.and.Gatekeepers.chm
Cisco.Press.Voice.Over.IP.First-Step.chm
Cisco.Press.Voice.over.IP.Fundamentals.2nd Edition.chm
Cisco.Press.Wireless.Networks.First.Step.chm
CiscoPress.Network.Management.Jun.2007.chm
Telecommunications_Technologies_Reference.pdf
Cisco.Press.CCIE.Professional.Development.BGP.4.Command.and.Configuration.Handbook.chm
Cisco.Press.CCIE.Professional.Development.Cisco.LAN.Switching.chm
Cisco.Press.CCIE.Professional.Development.Network.Security.Principles.and.Practices.chm
Cisco.Press.CCIE.Professional.Development.OSPF.Command.and.Configuration.Handbook.chm
Cisco.Press.CCIE.Professional.Development.Routing.TCP.IP.Volume.I.chm
Cisco.Press.CCIE.Professional.Development.Routing.TCP.IP.Volume.II.chm
Cisco.Press.CCIE.Professional.Development.Troubleshooting.IP.Routing.Protocols.chm
Cisco.Press.CCIE.Self.Study.CCIE.Security.Practice.Labs.chm
Cisco.Press.CCIE.Self.Study.Practical.Studies.Secturity.ISO
Cisco.Press.BGP.Internet.Routing.Architectures.2nd.Edition.2000.pdf
Cisco.Press.CCIE.Professional.Development.Advanced.IP.Network.Design.pdf
Cisco.Press.CCIE.Professional.Development.Inside.Cisco.IOS.Software.Architecture.pdf
Cisco.Press.CCIE.Professional.Development.Large-Scale.IP.Network.Solutions.1999.pdf
Cisco.Press.CCIE.Professional.Development.Routing.TCP.IP.Volume.I.pdf
Cisco.Press.CCIE.Professional.Development.Troubleshooting.IP.Routing.Protocols.pdf
Cisco.Press.CCIE.Professional.Development.Troubleshooting.Remote.Access.Networks.pdf
Cisco.Press.CCIE.Routing.and.Switching.Exam.Certification.Guide.pdf
Cisco.Press.CCIE.Self.Study.CCIE.Practical.Studies.Volume.I.pdf
Cisco.Press.CCIE.Self.Study.CCIE.Practical.Studies.Volume.II.pdf
Cisco.Press.CCIE.Self.Study.CCIE.Security.Exam.Certification.Guide.pdf
Cisco.Press.Cisco.Catalyst.QoS.Quality.of.Service.in.Campus.Networks.pdf
Sybex - CCIE.Cisco.Certified.Internetwork.Expert.Study.Guide.Second.Edition.2003.pdf
Cisco.Press.CCIE.Self.Study.CCIE.Security.Exam.Certification.Guide.zip
Cisco.Press.Cisco.Field.Manual.Catalyst.Switch.Configuration.chm
Cisco.Press.Configuring.Callmanager.and.Unity.a.Step.by.Step.Guide.chm
Cisco.Press.Integrated.Cisco.and.Unix.Network.Architectures.chm
Cisco.Press.IP.Telephony.CIPT.Authorized.Self.Study.Guide.2nd.Edition.Oct.2006.chm
Cisco.Press.Network.Security.Troubleshooting.Handbook.Nov.2005.chm
Cisco.Press.Practical.Service.Level.Management.Delivering.High-Quality.Web-Based.Services.chm
Cisco.Press.Aironet.Wireless.LAN.Fundamentals.AWLF.3.1.pdf
Cisco.Press.Campus.Network.Design.Fundamentals.Dec.2005.pdf
Cisco.Press.CANAC.Implementing.Cisco.NAC.Appliance.Lab.Guide.Ver.2.1.pdf
Cisco.Press.CANAC.Implementing.Cisco.NAC.Appliance.Student.Guide.Ver.2.1.Vol.1.pdf
Cisco.Press.CANAC.Implementing.Cisco.NAC.Appliance.Student.Guide.Ver.2.1.Vol.2.pdf
Cisco.Press.QOS.Implementing.Cisco.QoS.StudentGuide.v.2.2.Vol.I.II.pdf
Cisco.Press.Securing.Hosts.Using.CSA.StudentGuide.v.2.0.pdf
Cisco.Press.Self.Defending.Networks.The.Next.Generation.of.Network.Security.Aug.2006.pdf
Cisco.Press.The.Complete.Cisco.VPN.Configuration.Guide.pdf

Download
http://rapidshare.com/files/123710777/CiscoPress.part01.rar
http://rapidshare.com/files/123713510/CiscoPress.part02.rar
http://rapidshare.com/files/123719204/CiscoPress.part03.rar
http://rapidshare.com/files/123721793/CiscoPress.part04.rar
http://rapidshare.com/files/123727686/CiscoPress.part05.rar
http://rapidshare.com/files/123730578/CiscoPress.part06.rar
http://rapidshare.com/files/124055104/CiscoPress.part07.rar
http://rapidshare.com/files/124055114/CiscoPress.part08.rar
http://rapidshare.com/files/124063344/CiscoPress.part09.rar

CCDA, CCDP, CCIP

2008-06-22T00:25:00.002+07:00

Packet included 640-863, 642-871, 642-691 BGP

http://rapidshare.com/files/123736634/CCDA_CCDP_CCIP.part1.rar
http://rapidshare.com/files/123740571/CCDA_CCDP_CCIP.part2.rar

Cisco Certified Network Associate Study Guide: Exam 640-802, 6th Edition

2008-06-22T00:18:00.000+07:00

Completely Revised for the New 2007 Version of the CCNA Exam (#640-802)

Cisco networking authority Todd Lammle has completely updated this new edition to cover all of the exam objectives for the latest version of the CCNA exam. Todd’s straightforward style provides lively examples, easy-to-understand analogies, and real-world scenarios that will not only help you prepare for the exam, but also give you a solid foundation as a Cisco networking professional.

Packed with updated topics that have been added to the 2007 version of the CCNA exam, this updated study guide features expanded coverage of key topic areas plus new material on switching, network address translation, and OSPF. Inside, find the complete instruction you need, including:

* Full coverage of all exam objectives in a systematic approach, so you can be confident you’re getting the instruction you need for the exam
* Practical hands-on exercises and labs to reinforce critical skills,
* Real-world scenarios that put what you’ve learned in the context of actual job roles
* Challenging review questions in each chapter to prepare you for exam day
* Exam Essentials, a key feature in each chapter that identifies critical areas you must become proficient in before taking the exam

* CD-ROM Includes:
* Chapter Review Questions
* Four Full-Length Practice Exams
* 200 Electronic Flashcards
* Audio and Video Instruction from Todd Lammle
* Full book in searchable PDF format

Download:
http://rapidshare.com/files/123687289/Sybex_CCNA_6th_Edition.part1.rar
http://rapidshare.com/files/123687296/Sybex_CCNA_6th_Edition.part2.rar
http://rapidshare.com/files/123696739/Sybex_CCNA_6th_Edition.part3.rar
http://rapidshare.com/files/123697001/Sybex_CCNA_6th_Edition.part4.rar
http://rapidshare.com/files/123705567/Sybex_CCNA_6th_Edition.part5.rar
http://rapidshare.com/files/123705624/Sybex_CCNA_6th_Edition.part6.rar

TS CCNP ONT 642-845

2008-06-15T05:57:00.000+07:00

http://rapidshare.com/files/122322213/TS_CCNP_ONT_642-845.part1.rar
http://rapidshare.com/files/122322203/TS_CCNP_ONT_642-845.part2.rar

TS CCNP BSCI

2008-06-15T05:54:00.002+07:00

http://rapidshare.com/files/122302349/TS_CCNP_BSCI.part1.rar
http://rapidshare.com/files/122321746/TS_CCNP_BSCI.part2.rar
http://rapidshare.com/files/122322206/TS_CCNP_BSCI.part3.rar
http://rapidshare.com/files/122322051/TS_CCNP_BSCI.part4.rar

TS CCNP BCMSN

2008-06-14T11:55:00.001+07:00

http://rapidshare.com/files/122299789/TS_CCNP_BCMSN.part1.rar.html
http://rapidshare.com/files/122299991/TS_CCNP_BCMSN.part2.rar.html
http://rapidshare.com/files/122300953/TS_CCNP_BCMSN.part3.rar.html

Netmaster Frame-Relay VOD

2008-06-14T11:50:00.001+07:00

http://rapidshare.com/files/122292153/Netmaster_Frame-Relay_VOD.part01.rar.html
http://rapidshare.com/files/122293307/Netmaster_Frame-Relay_VOD.part02.rar.html
http://rapidshare.com/files/122294258/Netmaster_Frame-Relay_VOD.part03.rar.html
http://rapidshare.com/files/122294417/Netmaster_Frame-Relay_VOD.part04.rar.html
http://rapidshare.com/files/122297097/Netmaster_Frame-Relay_VOD.part05.rar.html
http://rapidshare.com/files/122298188/Netmaster_Frame-Relay_VOD.part06.rar.html
http://rapidshare.com/files/122299161/Netmaster_Frame-Relay_VOD.part07.rar.html

IPExpert CCIE Voice Proctor Guide 4.0

2008-06-14T10:31:00.002+07:00

http://rapidshare.com/files/122285101/IPExpert_CCIE_Voice_Proctor_Guide_4.0.part1.rar.html
http://rapidshare.com/files/122285088/IPExpert_CCIE_Voice_Proctor_Guide_4.0.part2.rar.html
http://rapidshare.com/files/122285783/IPExpert_CCIE_Voice_Proctor_Guide_4.0.part3.rar.html
http://rapidshare.com/files/122288580/IPExpert_CCIE_Voice_Proctor_Guide_4.0.part4.rar.html
http://rapidshare.com/files/122288626/IPExpert_CCIE_Voice_Proctor_Guide_4.0.part5.rar.html
http://rapidshare.com/files/122291167/IPExpert_CCIE_Voice_Proctor_Guide_4.0.part6.rar.html
http://rapidshare.com/files/122291490/IPExpert_CCIE_Voice_Proctor_Guide_4.0.part7.rar.html

Getting More Bandwidth Plus 5 Times Tcp/ip Connections, Improve internet speed, BT downloads, online games and media streaming

2008-06-14T10:17:00.002+07:00

Windows by default reserves 20% available Internet bandwidth.
To release this reserved bandwidth carry out the steps below:

Click "Start" button.
Click "Run" and in the "Open:" column enter gpedit.msc and click "OK"
Double click "Computer Configuration"
Double click "Administrative Templates"
Double click "Network"
Double click "QoS Packet Scheduler"
Double click "Limit reservable bandwidth"
Select "Enable" and set the "Bandwidth limit (%) to zero; click Apply and OK.

To increase TCP/IP connections
Windows by default only set 10 connections for TCP/IP to prevant hackers.

To set more connections get the TCP/IP Patcher from:

Home page :
http://www.lvllord.de

Download

http://www.lvllord.de/download.php?url=en/EvID4226Patch223d-en.zip
http://www.lvllord.de/download.php?url=de/EvID4226Patch223d-de.zip

Run the patch, select "yes" to increase TCP/IP connections from 10 to 50.
When MS asks you to restore the system select "Cancel" and "Yes".
You can restore to the original setting by running the program again.

Warning Computers running Windows XP Home Edition cannot join corporate domains. For this reason, features that require machine accounts within a domain, such as Group Policy, are not available in Windows XP Home Edition.

Exam-Pack 70-089: Planning, Deploying, and Managing Microsoft SMS 2003

2008-06-14T10:12:00.002+07:00

For network admins, Microsoft's Systems Management Server (SMS) is one of those things that you don't know you need until you get it... and then you can't live without it.

SMS makes it easy to survey and inventory the software and hardware on your network. Then you can deploy and update software on client machines, offer remote assistance, monitor the health of your network, even install operating systems, and a whole lot more. And it all integrates with the Microsoft Windows Server 2003 infrastructure.

But it takes more than a snap of your fingers to get it all right. Previous versions of SMS had a reputation that it can be difficult to do things right, and sometimes it's way too easy to do things wrong. While SMS 2003 is an improvement on what was there before, there's still a learning curve to using SMS successfully. Lucky for you, this training shortens your learning curve tremendously.

Instructor Greg Shields has years of experience working with SMS, on every version since 2.0. He knows all the fundamentals plus the expert tips, tricks, and secrets to getting SMS to purr like a kitten.

In this series, Greg takes you through the same process you'll follow from not having an SMS infrastructure up to having a fully-managed SMS infrastructure--including what you need to know along the way to get the biggest benefits from the core SMS components plus useful add-on feature packs.

Here's what you'll learn in the videos:

Get a quick overview of the reasons why SMS makes your life as a network admin easier, plus get a primer for what you'll be expected to know on the SMS 2003 70-089 exam. (Video 1)
Planning is the most important aspect of your SMS installation--go through all the factors to consider before you even think about installation, including hardware and software requirements. Then install SMS to your Windows Server, walking along with Greg through the important installation decisions. Finally, make Active Directory ready for SMS by extending the schema. (Video 2)
Even once you've installed SMS you're not quite ready to go. It's time to configure site system roles, sites (including parent, child, primary, secondary, and central sites), boundaries, and roaming in SMS before you can actually get in and start working. (Video 3)
Configure SMS to discover fundamental information about everything connected to your network, using one or more of the seven types of discovery SMS allows. Plus understand the difference between discovery and inventory, and what types of information each gets you. (Video 4)
Install SMS clients to workstations on your network--know which types of clients to use, which functions are available from the different client agents, when and why to use the different installation executables that are available, and methods you can use to install clients across your network, plus interact with clients from your server once they are installed. (Video 5)
Learn exactly what hardware and software are installed on client machines by collecting custom inventory information. Then view this information, uncovering useful data such as which clients have a specific network adapter or un-patched version of software. Finally, configure metering and understand the difference between the information you get from metering and the information you get from inventory. (Video 6)
Make management of multiple clients easier by grouping clients into collections based on parameters you define--including defining collections in a way that they update automatically as your network resources change. Then use queries, reports, and dashboards to interact with, view, and share this information. (Video 7)
Learn the "art" of creating good software packages to distribute software to clients. Learn how packages, programs, and advertisements all factor in to getting the software installed on the client machines--and how they all work together in SMS to make software deployment extremely flexible. (Video 8)
Secure your SMS deployment using class and instance rights. Also, configure and use remote assistance to troubleshoot client computers from your desktop. (Video 9)
Control software updates and patching through SMS, including agent-based and agent-less patching tools, plus compliance-based patching processes. Then, set up software updates using the Security Update Inventory Tool (SUIT) and go through the four-step process of actually doing a software update: synching, scanning, patching, and reporting. (Video 10)
Keeping clients healthy may be the most difficult part of managing your SMS infrastructure. Understand client health, the client health service, and the client health database. Then install the client health tool, and use the ping and pulse tools to identify which clients are "healthy" and which clients are not--plus generate reports on client health network-wide. (Video 11)
Speed up the deployment of operating systems using the OSD feature pack. This video takes you through all the steps: create an image capture CD, capture an operating system image, create the image deployment CD, and then deploy the image. Plus, learn what actions you can take after the deployment to get the deployed system up and running as quick as possible. (Video 12)
Use SMS's inventory and software deployment features on Windows Mobile devices, with the help up the Device Management Feature Pack (DMFP). (Video 13)
Maintain your SMS database to keep your infrastructure healthy using SQL commands and built-in tasks. Backup your data to protect against disaster, and understand the purpose of both the smsbkup.log and smsbkup.ctl files. If disaster strikes, learn how to restore a site using the Recovery Expert and the Site Repair Wizard. (Video 14)
Wrap up your SMS knowledge with miscellaneous topics you need to know, including which SMS logs and inboxes are important, understanding System Status and Status Message Queries, a review of SMS Toolkit 2 and some of the useful tools it contains, plus a final exam review to get you ready to certify your SMS skills. (Video 15)
On-the-job skills for Systems Management Server plus exam prep for MCP, MCSE

Exam-Pack 70-089: Planning, Deploying, and Managing Microsoft SMS 2003 shows you how to use SMS 2003 to make your job as a network admin easier. It also maps to exam objectives for Microsoft exam 70-089, which earns you Microsoft Certified Professional (MCP) certification on SMS 2003 and gives you elective credit toward Microsoft Certified Systems Engineer (MCSE) certification on Windows Server 2003.

Prerequisites

Experience with the Microsoft Windows operating system is recommended before viewing these videos. For in-depth instruction on using Microsoft Windows, check out Exam-Pack 70-270: Windows XP.

Exam-Pack 70-089: Planning, Deploying, and Managing Microsoft SMS 2003 contains:

- Introduction to SMS & the 70-089 Exam
- SMS Planning, Prerequisites, Installation, & Schema Extensions
- Roles, Sites, Boundaries, & Roaming
- Configuring Discovery & Discovering Resources
- SMS Clients & Client Installation
- Collecting Inventory & Metering Data (free video!)
- Collections, Querying & Reporting
- Distributing Software
- Applying Security & Implementing Remote Tools
- Managing Software Updates
- Monitoring Client Health
- Using the OSD Feature Pack
- Using the Device Management Feature Pack
- Backup, Recovery, & Database Maintenance Tasks
- SMS Logs, System Status, External Tools, & Exam Review

Video Technical Specifications

1. Introduction to SMS & the 70-089 Exam - This nugget introduces the 70-089 exam, where it fits in with other components of Microsoft certification, and the topics to discuss to prepare the observer for the SMS exam.

2. SMS Planning, Prerequisites, Installation, & Schema Extensions - Discusses the planning, prerequisites, installation, and Active Directory schema extensions necessary for SMS installation. Includes an SMS installation and schema extension demonstration.

3. Roles, Sites, Boundaries, & Roaming - Discusses SMS roles, SMS sites, SMS boundaries, and SMS client roaming. Configuring SMS site components like parent, child, primary, secondary, and child sites. Creating secondary sites, sender addresses, site boundaries, and roaming boundaries.

4. Configuring Discovery & Discovering Resources - Configuring SMS discovery and discussing the difference between discovery and inventory information. The concept of the SMS GUID and DDR are discussed. Types of discovery like windows user account discovery, windows user group discovery, network discovery, heartbeat discovery, AD system discovery, AD user discovery, and AD system group discovery.

5. SMS Clients & Client Installation - Types of clients and client agents are discussed. SMS installation executables and installation methods. Five client agents like Advertised Programs, Hardware Inventory, Software Inventory, Remote Tools, and Software Metering.

6. Collecting Inventory & Metering Data - Configuring inventory and viewing inventory. Customizing inventory with IDMIF and NOIDMIF files as well as the SMS_DEF.MOF file. SMS Metering is discussed and SMS metering reporting.

7. Collections, Querying & Reporting - SMS Collections, SMS Querying, and SMS Reporting are discussed. Using direct membership and query membership for collections. Creating custom queries using SQL queries and WQL queries. Creating SMS reports and SMS dashboards.

8. Distributing Software - Distributing software and creating software packages. Discussing the software packaging process. SMS packages, SMS distribution points, SMS advertisements are all discussed.

9. Applying Security & Implementing Remote Tools - SMS Security and SMS remote tools are discussed. Windows security vs. SMS security. Creating class rights and creating instance rights. Configuring remote tools and remote assistance settings.

10. Managing Software Updates - Managing software updates and software patching process. Agent-based vs. agentless patching tools. Compliance-based patching processes. Setting up SUIT feature pack, downloading inventory scanning programs, synchronizing mssecure.cab and its compressed mssecure.xml file to update.microsoft.com. Completing client patch scans and pushing patches to clients.

11. Monitoring Client Health - Monitoring client health using Client Health Monitoring Tool. Installing the client health tool. Discussing healthy client, unhealthy client, offline client, obsolete client, and suspected unhealthy client, ping tool, and pulse tool. Reporting using Client Health Summary Report and Client Health Pivot Table Report.

12. Using the OSD Feature Pack - Operating System Deployment Feature Pack. Creating an image capture CD, capturing an operating system image. Creating an image deployment CD. Deploying an operating system image. Deployment actions. Using sysprep and Windows PE. Discussing actions and phases.

13. Using the Device Management Feature Pack - Using the Device Management Feature Pack to manage Windows Mobile, Windows CE, Windows Mobile for Pocket PC solid-state devices. Discussing Device Client Agent and Device Management Point. Distributing software and configurations using the Device Settings Manager.

14. Backup, Recovery, & Database Maintenance Tasks - SMS Backup, SMS Recovery, and SMS SQL database maintenance tasks. Discussing site maintenance, SQL commands, and SQL tasks. SMS site backup and the smsbkup.log and smsbkup.ctl backup control file. Site restore using the Recovery Expert and Site Repair Wizard.

15. SMS Logs, System Status, External Tools, & Exam Review - SMS Logs, SMS System Status Summarizers, SMS Toolkit 2, and 70-089 exam review. Discussion of SMS logs and SMS inboxes. Discussion of System Status and Status Message Queries.

Download files:
http://rapidshare.com/files/122532415/v-cpdamm.part1.rar.html
http://rapidshare.com/files/122532443/v-cpdamm.part2.rar.html

Boson Netsim Version 7.02 and crack

2008-06-14T09:28:00.003+07:00

Download Boson Netsim for CCNP 7.0.2 at boson.com

http://www.boson.com/Product/CIS-NS-CCNP-02.html
or
http://rapidshare.com/files/122288927/ccnp_netsim7.exe

Crack

http://rapidshare.com/files/122289307/mscon43demo.dll

Copy & overwrite existing mscon43demo.dll to:

Vista------- \ProgramData\Boson Software\Boson NetSim for CCNP 7.0\
XP --------- \Documents and Settings\All Users\Application Data\Boson Software\Boson NetSim 7
Now, you can use demo version with all functions of active full version.

CCNP Video Mentor Labs

2008-06-14T09:17:00.002+07:00

Description
CCNP Video Mentor is a CD-ROM software product. The enclosed CDs contain a series of succinct instructional videos that demonstrate how to accomplish various CCNP-level configuration tasks on Cisco routers and switches. The 16 videos contained in this product total between 180-240 minutes of instruction. In each individual 10-15 minute video, senior instructor Kevin Wallace walks users through basic configuration tasks. The videos consist of audio instruction, animations, and router and switch CLI video screen-casts. Each video lab presents suggested reading lists, detailed objectives, lab diagrams, command tables, and video captures. Audio instruction throughout offers tips and shortcuts that truly make learning easy. Animated network diagrams show users lab setup, device addressing, and how traffic flows through the network. Video screen-casts of the router and switch CLI demonstrate command entry, configuration techniques, and device response. For several years now, Cisco has included simulation-based assessment into its CCNP exams. These simulation questions require candidates to perform basic configuration tasks, adding another level of complexity to the certification process. CCNP Video Mentor helps candidates better prepare for this aspect of the exam.

Links
http://rapidshare.com/files/124977607/CCNP_Video_Mentor.part01.rar.html
http://rapidshare.com/files/124977632/CCNP_Video_Mentor.part02.rar.html
http://rapidshare.com/files/124993696/CCNP_Video_Mentor.part03.rar.html
http://rapidshare.com/files/124993764/CCNP_Video_Mentor.part04.rar.html
http://rapidshare.com/files/125007515/CCNP_Video_Mentor.part05.rar.html
http://rapidshare.com/files/125007534/CCNP_Video_Mentor.part06.rar.html
http://rapidshare.com/files/125020043/CCNP_Video_Mentor.part07.rar.html
http://rapidshare.com/files/125020292/CCNP_Video_Mentor.part08.rar.html

CBT CCNA

2008-06-14T08:11:00.000+07:00

http://rapidshare.com/files/122272334/CBT_CCNA.part1.rar.html
http://rapidshare.com/files/122272301/CBT_CCNA.part2.rar.html
http://rapidshare.com/files/122272307/CBT_CCNA.part3.rar.html
http://rapidshare.com/files/122272321/CBT_CCNA.part4.rar.html
http://rapidshare.com/files/122272302/CBT_CCNA.part5.rar.html
http://rapidshare.com/files/122278922/CBT_CCNA.part6.rar.html

My Music

2008-06-13T13:16:00.003+07:00

Some music was recorded by myself.

Con Dau Cuoi Cung.