Windows Sever 2003 System Administration Part 1

Download Report

Transcript Windows Sever 2003 System Administration Part 1

Windows Server 2003
WINS 安裝設定與管理維護
林寶森
[email protected]
Microsoft TCP/IP Protocol Suite
Windows® Sockets
Applications
NetBIOS
Applications
Sockets
NetBIOS
NetBIOS over TCP/IP
TCP
ICMP IGMP
LAN Technologies:
Ethernet, Token Ring,
FDDI
TDI
Transport
UDP
IP
Application
Internet
ARP
WAN Technologies:
Serial Lines, Frame Relay,
ATM
Network
What Is a NetBIOS Name?
• NetBIOS names are 16-byte addresses that
uniquely identify a process for network
identification
• NetBIOS names are registered dynamically and
can be:
– Used only once in a network
– Registered as unique names or group names
• Use browsing to locate shared resources on the
network
NetBIOS Name Resolution
net use x: \\france\public
NetBIOS Name Cache
Empty
1
Not Resolved
2
Primary
WINS Server
Name Query Request
(resend to secondary
server if not available)
Secondary
WINS Server
3
Broadcast
Requested Name
Does Not Exist
NetBIOS Name Resolution Nodes
A NetBIOS node type is a method that a computer uses to
resolve a NetBIOS name into an IP address
Node type
Description
Registry
value
B-node
Uses broadcasts for name registration
and resolution
1
P-node
Uses a NetBIOS name server such as
WINS to resolve NetBIOS names
2
M-node
Combines B-node and P-node, but
functions as a B-node by default
4
H-node
Combines P-node and B-node, but
functions as a P-node by default
8
WINS Service for a LAN
Client B
Client A
Client C
WINS Clients
(H-node)
WINS
Server
H-node
Register, Renew, Release,
and Query by Unicast
traffic then use LMHosts
and Broadcasts
Unicast
reduces
broadcasts
The LMHosts File
Lmhosts File
192.168.1.1
Mexico
# Sales Server
192.168.2.1
France
# Database Server
192.168.3.1
UK
# Training Server
192.168.4.1
Sweden
#PRE
# Main Office Server
192.168.5.1
Australia
#PRE
# MIS Server
WINS Client
Options for NetBIOS Name Resolution
LMHOSTS
Suitable for small environments
Reduces broadcast traffic
Requires static IP addresses
WINS
Suitable for organizations of all sizes
Reduces broadcast traffic
Does not require static IP addresses
WINS Overview
Registration
Renewal
Query
Release
WINS Client
WINS Server
How a WINS Client Registers and
Releases NetBIOS Names
Name Registered
Name Released
WINS Client
1
2
WINS Server
WINS client sends request to register
WINS server returns registration message with TTL value
indicating when the registration expires if not renewed
WINS client sends request to release name
WINS server sends a positive name lease response
How a WINS Client Resolves NetBIOS
Names
Up to 3 attempts
WINS Server A
1
ClientA
Subnet 2
Subnet 1
2
WINS Server B
3
Subnet 2
1
Client makes 3 attempts to contact WINS server, but does not
receive a response
2
Client attempts to contact all WINS servers until contact is made
3
If name is resolved, IP address is returned to the client
The Components of WINS
WINS Server
Subnet 2
WINS Client
Subnet 1
WINS Proxy
WINS
Database
Configuring a WINS Proxy
WINS Database
Broadcast for IP of
Server2
Client1
Server1
192.168.0.11
192.168.0.12
WINS Server
Server2 192.168.0.13
Static Mapping
IP Router
Broadcast
WINS Proxy
Server2 192.168.0.13
Non-WINS Client
Request Forwarded to WINS
Server by WINS Proxy
What Is a Static Mapping?
A static mapping is a manual entry in the WINS database that
maps a NetBIOS name to an IP address
Administrator enters computer
name-to-IP address entry
Non-WINS Clients
WINS Database
Configuring Static Mappings
New Static Mapping
General
Static Mapping
You can add static name-to-address mappings to the WINS
database, but only for computers that cannot register
dynamically in WINS. Static mappings can replicate
throughout your WINS environment and write over records on
other servers.
Computer name:
LONDON
NetBIOS scope (optional):
Type:
Unique
IP address:
192 . 168 . 1 . 200
OK
Cancel
Apply
Integrating WINS and DNS
• DNS Domain Name Used to Locate
Authoritative DNS Server
• DNS Server Queries WINS to Resolve DNS
Host Name to IP Address
Client
DNS Query
DNS
Server
WINS
Server
Configuring DNS to Forward Queries to
WINS Servers
nwtraders.msft Properties
General
WINS
Start of Authority (SOA)
Zone Transfers
Name Servers
Security
You can use WINS to resolve names not found by
querying the DNS namespace.
Use WINS forward lookup
Advanced
Do not replicate this record
To change the default values, provide new values,
and then click OK.
DDDD:HH:MM:SS
Cache time-out:
0
:0 :15 :0
IP address:
Add
192.168.1.1
192.168.1.2
192.168.1.3
Lookup time-out:
Remove
0
:0
:0
:2
Up
Down
OK
Advanced…
OK
Cancel
Apply
Cancel
How Burst Handling Works
Burst handling is the response of a WINS server to a large
number of WINS clients that are trying to simultaneously
register their local names in WINS
1
2
Request to register
Registered
Configuring Advanced WINS Server Options
LONDON [192.168.1.200] Properties
General
Intervals
Database Verification Advanced
Log detailed events to Windows event log
Detailed event logging can degrade system performance
and is recommended only for troubleshooting WINS.
Enable burst handling
Set the number of requests that the server can handle at
one time before clients have to retry registration or renewal.
Low
High
Medium
Custom:
Database path:
%widir%\system32\wins
Starting version ID (hexadecimal)
0
Use computer names that are compatible with LAN
Manager
OK
Cancel
Apply
WINS Service for a Routed Network
WINS Server
WINS Servers
Subnet 1
WINS Clients
Subnet 3
WINS Server
Subnet 2
Washington, D.C.
WAN Link
WINS Client
Santiago
How WINS Replication Works
WINS replication is the process of copying updated WINS data
from a WINS server to other WINS servers in a network to
synchronize the data
WINS Server B
WINS Server A
WINS
Replication
Subnet 1
HostA
Subnet 2
HostB
How Push Replication Works
A push partner notifies replication partners when the database reaches a set
threshold of changes
Push replication maintains a high level of synchronization/use with fast links
Notification
Replication
sent
request
sent
423 Replicas
WINS Server A
Subnet 1
WINS Server B
1
Subnet 2
50 changes occur
in database
1
WINS Server A reaches set threshold of 50 changes in its database
2
WINS Server A notifies WINS Server B that threshold is reached
3
WINS Server B responds to WINS Server A with a replication request
4
WINS Server A sends replicas of its new database entries
How Pull Replication Works
A pull partner requests replication based on a set time
Pull replication limits frequency of replication traffic across slow links
WINS Server A
Requests changes
sent
21 Replicas
every 8 hours
Subnet 1
1
WINS Server A requests database changes every 8 hours
2
WINS Server B sends replicas of its new database entries
WINS Server B
Subnet 2
Configuring WINS Replication
BONN Properties
General Advanced
Replication partner type:
Push/Pull
Push/Pull
Pull replication
Use persistent connection for replication
Start time:
0
0
0
Replication interval:
0
0
30
Set Default
Push replication
Use persistent connection for replication
0
Number of changes in version ID before
replication:
Set Default
OK
Cancel
Apply
Replication Partner Properties
Property
Description
Enable automatic
partner configuration
As WINS servers are discovered
joining the network, they are added as
replication partners
Enable persistent
connections
Increases the speed of replication so
that a server can immediately send
records to its partners
Enable overwrite unique If presented with both a static and
dynamic-type entry for the same name,
static mappings at this
the static mapping is overwritten
server (migrate on)
Replication Strategies
SEA-WINS
1 hour
3 hour
12 hours
ATL-WINS
12 hours
Australia
MEX-WINS
SYD-WINS
WINS Replication Topology
WINS-B
WINS-A
Ring
Fully
Chain
Mesh
WINS-D
WINS-C
Using a Hub-and-Spoke Model
WINS-C
Hub and Spoke
replication minimizes
convergence times
push/pull
WINS-B
WINS-E
push/pull
push/pull
WINS-A
push/pull
WINS-D
How a WINS Database Is Checked for Consistency
Checking WINS database consistency helps maintain database
integrity among WINS servers in a large network
WINS Server
WINS Server
WINS Server
Verifying WINS Database Consistency
LONDON [192.168.1.200] Properties
General
Intervals
Database Verification Advanced
24
Verify database consistency every:
Hours:
Begin verifying at:
2
hours
Minutes: Seconds:
0
0
Maximum number of records verified each period:
30000
Verify against:
Owner servers
Randomly selected partners
OK
Cancel
Apply
What Are Simple Deletion and
Tombstoned Deletion of Records?
To recover unused space that obsolete records
occupy, you can update the WINS database by:
Simple deletion. Records selected by using the WINS
console are removed from the current local WINS server
Tombstoned deletion. Records are marked for deletion,
replicated to other WINS servers, and then removed during
the next scavenging operation
Removing Records from the WINS Database
LONDON [192.168.1.200] Properties
General
Intervals
Database Verification Advanced
Set the rate at which records are renewed, deleted and verified.
Renew interval:
Days
6
Hours
0
Minutes
0
Extinction interval:
4
0
0
Extinction timeout:
6
0
0
Verification interval:
24
0
0
Restore Defaults
OK
Cancel
Apply
How Scavenging Works
6-days
Active
123456
4-days
Released
6-days
Extinct
Removed
The
Released
Names
active
marked
names
names
for
that
that
deletion
the
theWINS
WINS
for
that
which
are
server
server
replicated
the
owns
owns
Extinction
and
and
from
for
for
other
The
Active
scavenging
names
that
timer
are
starts
replicated
when
from
the
other
server
servers
starts
up
and for
which
timeout
servers
the
and
has
Renew
Extinction
for
expired
which
Interval
are
interval
the
deleted
Extinction
has
has
expired
and
expired
removed
timeout
are
are
marked
has
marked
from
expired
as
and
which
is the
equal
Verification
to half
the interval
Renewal
has
interval
expired are revalidated
released
for deletion
the
are
database
deleted
and
removed
from the
database
Why Back Up a WINS Database?
To repair a corrupt WINS database, you can
back up and then restore a WINS database
To back up a WINS database :
Specify a backup directory
Back up manually or configure automatic backups
To restore a WINS database:
Manually delete and restore database files
What Are Dynamic and Offline
Compacting?
Compacting is the process of recovering unused space in a
WINS database that is occupied by obsolete records
Maintain WINS database integrity by using:
Dynamic compacting. Automatically occurs while the
database is in use
Offline compacting. Administrator stops the WINS server
and uses the jetpak command