380 likes | 989 Views
Guide to MCSE 70-291, Enhanced. 2. Objectives. Install WINSConfigure WINS replicationManage WINS server settingsCreate static WINS mappingsBack up and restore a WINS databaseUnderstand when to use a WINS proxyTroubleshoot the WINS service. Guide to MCSE 70-291, Enhanced. 3. Installing WINS. Windows Server 2003 has the ability to act as a WINS server via the WINS serviceWINS is never installed automatically on Windows Server 2003Install the service using Add/Remove Windows Components.
E N D
1. 70-291: MCSE Guide to Managing a Microsoft Windows Server 2003 Network, Enhanced Chapter 8: Windows Internet Naming Service
2. Guide to MCSE 70-291, Enhanced 2 Objectives Install WINS
Configure WINS replication
Manage WINS server settings
Create static WINS mappings
Back up and restore a WINS database
Understand when to use a WINS proxy
Troubleshoot the WINS service
3. Guide to MCSE 70-291, Enhanced 3 Installing WINS Windows Server 2003 has the ability to act as a WINS server via the WINS service
WINS is never installed automatically on Windows Server 2003
Install the service using Add/Remove Windows Components
4. Guide to MCSE 70-291, Enhanced 4 Installing WINS (continued)
5. Guide to MCSE 70-291, Enhanced 5 Activity 8-1: Installing WINS Objective: Install WINS on your server
Use the Add/Remove Windows Components utility
6. Guide to MCSE 70-291, Enhanced 6 Activity 8-2: Configuring a WINS Client Objective: Configure your server to be a WINS client
Add the WINS client settings by using the TCP/IP configuration utilities
A WINS server must be configured as a WINS client
7. Guide to MCSE 70-291, Enhanced 7 Configuring WINS Replication A WINS server can handle at least 5000 WINS clients
Multiple WINS servers can be used to control network traffic and provide fault tolerance
You must configure replication if there are multiple WINS servers on the network
8. Guide to MCSE 70-291, Enhanced 8 Configuring WINS Replication (continued) WINS servers that replicate information between themselves are called replication partners
There are three ways replication can be configured:
Push
Pull
Push/Pull
9. Guide to MCSE 70-291, Enhanced 9 Configuring WINS Replication (continued)
10. Guide to MCSE 70-291, Enhanced 10 Configuring WINS Replication (continued)
11. Guide to MCSE 70-291, Enhanced 11 Configuring WINS Replication (continued)
12. Guide to MCSE 70-291, Enhanced 12 Configuring WINS Replication (continued) Push replication occurs based upon changes in the WINS database
Pull replication occurs based upon a set time schedule
A combination of push and pull replication is used by default
Both push and pull replication strategies can use persistent connections
Persistent connections result in faster replication
13. Guide to MCSE 70-291, Enhanced 13 Configuring WINS Replication (continued)
14. Guide to MCSE 70-291, Enhanced 14 Configuring WINS Replication (continued)
15. Guide to MCSE 70-291, Enhanced 15 Configuring WINS Replication (continued)
16. Guide to MCSE 70-291, Enhanced 16 Activity 8-3: Configuring Replication Partners Objective: Configure your server to replicate WINS information with a partner
Use the WINS snap-in to add a replication partner and complete this activity
17. Guide to MCSE 70-291, Enhanced 17 Managing WINS Default settings usually provide adequate service
The renewal interval refers to the TTL given to WINS clients after a name is registered
The extinction interval refers to how long an unused record exists before being marked extinct
The extinction timeout refers to how long an extinct record is kept in the database
The verification interval refers to how long a WINS server waits before validating a record replicated from another server
18. Guide to MCSE 70-291, Enhanced 18 Managing WINS (continued)
19. Guide to MCSE 70-291, Enhanced 19 Managing WINS (continued)
20. Guide to MCSE 70-291, Enhanced 20 Managing WINS (continued)
21. Guide to MCSE 70-291, Enhanced 21 Managing WINS (continued)
22. Guide to MCSE 70-291, Enhanced 22 Viewing Database Records You can directly view the contents of the WINS database
To view the records, right-click Active Registrations and click Display Records
You have the option to delete records
A tombstoned record is deleted from all servers
23. Guide to MCSE 70-291, Enhanced 23 Viewing Database Records (continued)
24. Guide to MCSE 70-291, Enhanced 24 Activity 8-4: Viewing WINS Records Objective: View WINS records on your server
Use the WINS snap-in
25. Guide to MCSE 70-291, Enhanced 25 Adding Static Records Non-Microsoft servers may not be able to use a WINS server
To create a static WINS record, right-click Active Registrations and click New Static Mapping
For each static mapping, you must enter:
Computer name
Record type
IP address
26. Guide to MCSE 70-291, Enhanced 26 Adding Static Records (continued)
27. Guide to MCSE 70-291, Enhanced 27 Activity 8-5: Adding a Static Mapping Objective: Add a static mapping to the WINS database
You will be creating a static configuration for a UNIX machine
View the records in the database to ensure the configuration was successful
28. Guide to MCSE 70-291, Enhanced 28 Backing up the Database As a critical resource, the WINS database needs to be backed up regularly
A corrupted WINS database can be easily repaired if a backup exists
By default, a WINS server is not automatically backed up
29. Guide to MCSE 70-291, Enhanced 29 Backing up the Database (continued)
30. Guide to MCSE 70-291, Enhanced 30 Activity 8-6: Backing up and Restoring the WINS Database Objective: Back up and restore the WINS database on your server
Create a directory to hold the backup
Enable backup on shutdown
Manually backup the database
Delete and restore the database in order to test the backup capabilities
31. Guide to MCSE 70-291, Enhanced 31 Compacting the WINS Database There is no limit on the size of the database
Compacting can reduce the size of the WINS database and improve performance
Dynamic compacting is performed automatically on a periodic basis
Offline compacting may be used to manually compact a database
Use the jetpack utility for manual compacting
32. Guide to MCSE 70-291, Enhanced 32 Activity 8-7: Compacting the WINS database Objective: Compact a WINS database
Stop the WINS service
Use the jetpack utility to compact the database
Restart the WINS service
33. Guide to MCSE 70-291, Enhanced 33 Removing WINS Servers Ensure that there are no NetBIOS applications that are required on the network before removing WINS
You may choose to remove a WINS server if you already have several other servers
34. Guide to MCSE 70-291, Enhanced 34 Activity 8-8: Removing WINS Objective: Remove WINS from your server
Remove the service using the Add/Remove Windows Components utility
Remove the WINS client configuration
35. Guide to MCSE 70-291, Enhanced 35 WINS Proxy Used for computers that cannot be configured to use WINS
UNIX clients often require a proxy
36. Guide to MCSE 70-291, Enhanced 36 WINS Proxy (continued)
37. Guide to MCSE 70-291, Enhanced 37 Troubleshooting WINS Most problems result from improperly configured TCP/IP settings on client computers
NetBIOS name resolution problems are sometimes the result of a faulty NetBIOS name cache
Problems may lie with records in the WINS database itself
Failed replication may also cause problems
Backup of the WINS database on a server may fail
38. Guide to MCSE 70-291, Enhanced 38 Summary When two or more WINS servers exist on a network, replication must be configured between them to synchronize their contents
There are two types of WINS replication: push and pull
A static mapping can be configured for resources that are unable to register themselves with WINS
You can view the records in a WINS database, as well as delete them
39. Guide to MCSE 70-291, Enhanced 39 Summary (continued) The WINS database should be backed up like any other critical resource on a network
A WINS Proxy lets non-WINS clients use the WINS Service and verify the validity of NetBIOS names over the network