Course 2277C: Implementing, managing, and maintaining a Microsoft Windows Server 2003 network infrastructure: Network services - Module 7

Chia sẻ: Nothing Nothing | Ngày: | Loại File: PPT | Số trang:30

Thêm vào BST

Báo xấu

51
lượt xem 4
download

Download Vui lòng tải xuống để xem tài liệu đầy đủ

Module 7: Resolving NetBIOS names by using windows internet name service. This module provides you with the knowledge and skills to use WINS to register NetBIOS names and resolve them to IP addresses.

Chủ đề:

Bình luận(0) Đăng nhập để gửi bình luận!

Lưu

Nội dung Text: Course 2277C: Implementing, managing, and maintaining a Microsoft Windows Server 2003 network infrastructure: Network services - Module 7

Module 7: Resolving NetBIOS Names by Using Windows Internet Name Service
Overview • Multimedia: The Role of WINS in the Network Infrastructure • Installing and Configuring a WINS Server • Managing WINS Records • Configuring WINS Replication • Managing the WINS Database
Multimedia: The Role of WINS in the Network Infrastructure • The objective of this presentation is to provide an overview of WINS • At the end of this presentation, you will be able to: – Explain the role of WINS in the network infrastructure – Describe how WINS resolves NetBIOS names – Describe the WINS registration process – Describe how WINS replication works
Lesson: Installing and Configuring a WINS Server • Components of WINS • What Is a NetBIOS Node Type? • How a WINS Client Registers and Releases NetBIOS Names • How Burst Handling Works • How a WINS Server Resolves NetBIOS Names • Practice: Installing and Configuring a WINS Server
Components of WINS WINS Server Subnet 2 WINS Databa se WINS Client Subnet 1 WINS Proxy
What Is a NetBIOS Node Type? A NetBIOS node type determines the method that a computer uses to resolve a NetBIOS name Node Registr Description type y value Uses broadcasts for name B-node registration 1 and resolution Uses a NetBIOS name server such as P-node 2 WINS to resolve NetBIOS names Combines B-node and P-node, but M-node 4 functions as a B-node by default Combines P-node and B-node, but H-node 8 functions as a P-node by default
How a WINS Client Registers and Releases NetBIOS Names Name Registered Name Released WINS Client WINS Server WINS client sends request to register 1 WINS server returns registration message with TTL value, indicating when the registration expires WINS client sends request to release name 2 WINS server sends a positive name release response
How Burst Handling Works Burst handling allows a WINS server to handle a high number of simultaneous name registration requests WINS client WINS 1registrations 2 acknowledges exceed the burst registrations queue threshold with a short renewal interval
How a WINS Server Resolves NetBIOS Names Up to 3 attempts WINS Server A Client 1 Subnet 2 Subnet 1 2 WINS Server B 3 Subnet 2 Client makes three attempts to contact WINS 1 server, but does not receive a response Client attempts to contact all WINS servers until 2 contact is made If name is resolved, IP address is returned to the 3 client
Practice: Installing and Configuring a WINS Server In this practice, you will: Install WINS Configure a WINS client Configure burst handling
Lesson: Managing WINS Records Client Records What Is a Static Mapping? Methods for Filtering and Viewing Records in WINS Practice: Managing WINS Records
Client Records A WINS client record includes the following information: The The The registered service IP The Displays address The that WINS state NetBIOS registered that “x” server ofAto the corresponds unique name, indicate database from the Shows which hexadecimal which whether when tocan thebe the entry the number a entry entrywill that unique entry, registered including is originates entry, static name the which andthedisplays can WINS beexpire active, “null” server or assigns is blank during if name, hexadecimal or athe released, group, type entryinternet identifier is orname not tombstoned static group, registration or multihomed computer
What Is a Static Mapping? A static mapping is a manual entry in the WINS database Administrator enters computer name-to-IP Non-WINS Clients address entry WINS Database
Methods for Filtering and Viewing Records in WINS Display Filter records based on filter NetBIOS name and NetBIOS name and/or an IP address IP address Record WINS server that owns the record owners Record Record type such as workstation, types messenger, or server
Practice: Managing WINS Records In this practice, you will: Display and filter WINS records Create a static mapping
Lesson: Configuring WINS Replication • How WINS Replication Works • How Push Replication Works • How Pull Replication Works • What Is Push/Pull Replication? • WINS Replication Partner Properties • Practice: Configuring WINS Replication
How WINS Replication Works WINS replication occurs between two WINS servers to maintain consistent WINS data ServerB ServerA WINS Replicati on Subnet Subne 1 t2 Client Client 1 2
How Push Replication Works AApush pushpartner partner notifies replication notifies replication partners partnersbased basedon the onnumber of changes the number in itsin of changes database its database Push Pushreplication replicationmaintains maintains aahigh highlevel ofof level synchronization synchronization Notification Replication ServerA ServerA 3 Replicas 4 2 sent request sent ServerB ServerB Subnet 1 50 1 Subne changes Subnet2 Subnet t1 occur in occur in 2 database ServerA reaches set threshold of 50 changes in 1 1itsServerA indatabase reaches set threshold of 50 changes its database ServerA notifies ServerB that threshold is ServerA notifies ServerB that the threshold is 2 2reached reached ServerB responds to ServerA with a replication ServerB responds to ServerA with a 3 3request replication request ServerA sends replicas of its new database ServerA sends replicas of its new database 4 4entries entries
How Pull Replication Works A pull partner requests replication based on a A pullinterval time partner requests replication based on a time interval Pull replication limits frequency of replication Pull replication traffic limits across slow frequency of replication links traffic across slowRequests links Replicas ServerA ServerA 2 1 changes sent ServerB ServerB every 8 hours Subnet 1 Subn Subnet Subnet2 et 1 2 ServerA requests ServerA requests database database changes changes every every 88 11 hours hours ServerB sends ServerB sends replicas replicas of of its its new new database database 22 entries entries
What Is Push/Pull Replication? Push/pull replication ensures that the databases on multiple WINS servers are nearly identical at any Notifying replication partners whenever given the time by: reaches a set threshold of database changes - And - Requesting replication based on a set time