Chapter 4 Overview q Configure clientserver components o

Chapter 4 Overview q Configure client/server components o o o o Network interface card (NIC) Windows 95 Windows NT (similar to Windows 2000) TCP/IP SNMP mgmt agents Microsoft networks Discussion of Net. BIOS, DNS, etc. Chapter 4 Configuration: Client/Server Components 1

Why Configuration? q Analogy to telephone system o Network components like telephone hardware o Network configuration is like “getting everyone to speak the same language” q Network configuration necessary since o Not all components are plug and play o Networks are heterogeneous (different hardware, OSs, applications, protocols, etc. ) Chapter 4 Configuration: Client/Server Components 2

Configuration q Documentation is important o “The time it takes to troubleshoot a network is usually inversely proportional to the care taken in documenting device configuration” q What to configure? o Protocol stack (configured when OS is installed) o For network mgmt, must enable SNMP o In the past even the NIC had to be configured (today, plug and play) Chapter 4 Configuration: Client/Server Components 3

The LAN used in Textbook Chapter 4 Configuration: Client/Server Components 4

Asynchronous Communication q Each external device has a unique combination of interrupt request (IRQ) number and I/O address o These determine interrupt handler to call o Limited number of IRQs available q Must avoid conflicts o In past, admin had to configure these o Today, plug and play Chapter 4 Configuration: Client/Server Components 5

Network Interface Card q Consider Ethernet adapter o IRQ and I/O address chosen by BIOS Chapter 4 Configuration: Client/Server Components 6

Network Interface Card q Driver and protocol stack info Chapter 4 Configuration: Client/Server Components 7

Windows 95 q Specify IP address or use DHCP Chapter 4 Configuration: Client/Server Components 8

Windows 95 Specify default gateway q In this example, if IP address not in range 192. 241 thru 192. 246, it will go to router at q o 192. 243 Chapter 4 Configuration: Client/Server Components 9

Windows 95 q q DNS Here, DNS server is named server. Raleigh o Not connected to Internet q If connected to Internet, need a fully qualified domain name o server. Raleigh. com, or o server. Raleigh. net, … Chapter 4 Configuration: Client/Server Components 10

Windows 95 q WINS o Windows Internet Name Service o Resolves internal (Net. BIOS) names to IP addresses q q Used in Win NT and earlier Can be used in Win 2000 and later, but by default, these use DNS Chapter 4 Configuration: Client/Server Components 11

Windows 95 q q q “Network Neighborhood” Determines what is visible to hosts on the LAN Uses Net. BEUI (Net. BIOS Extended User Interface) o Prior to Windows 2000 q To get outside of LAN, Net. BIOS over TCP/IP (NBT) Chapter 4 Configuration: Client/Server Components 12

Windows 95 q Configure SNMP agent o Allow mgmt station to see MIB information Chapter 4 Configuration: Client/Server Components 13

Windows NT Server q Server manager o Primary domain controller, SERVER o Login once and access all computers in domain Chapter 4 Configuration: Client/Server Components 14

Windows NT Server q User manager for domains o For configuring server o Lists users and groups Chapter 4 Configuration: Client/Server Components 15

Windows NT Server q TCP/IP protocol stack o Similar to previous example (Windows 95) Chapter 4 Configuration: Client/Server Components 16

Windows NT Server q WINS server o Static mapping of Net. BIOS to IP addresses o Not necessary to statically configure this Chapter 4 Configuration: Client/Server Components 17

Windows NT Server q DNS o Similar to previous Chapter 4 Configuration: Client/Server Components 18

Windows NT Server q Network interface card o Also similar to Windows 95 Chapter 4 Configuration: Client/Server Components 19

Windows NT Server q SNMP o More to configure in server Chapter 4 Configuration: Client/Server Components 20

Windows NT Server q SNMP services configuration (not shown) o Specify which info can be stored in MIB-2 and which is accessible by mgmt station Chapter 4 Configuration: Client/Server Components 21

Windows NT Server q SNMP security configuration o A specified community name must be included in SNMP packet from mgmt station o Each community name is allowed access to specific MIB variables o Can also choose to only accept SNMP packets from specified hosts Chapter 4 Configuration: Client/Server Components 22

Windows NT Server q SNMP security configuration Chapter 4 Configuration: Client/Server Components 23

Windows NT Server q SNMP Traps o Unsolicited msgs from agent to mgmt station o Specify destination mgmt station for traps o In distributed mgmt scenario, can send trap to more than one mgmt station o Example of trap: incorrect community name (might help to detect an attack) Chapter 4 Configuration: Client/Server Components 24

Windows NT Server q SNMP Traps Chapter 4 Configuration: Client/Server Components 25

Chapter 4 Summary q Client/Server configuration o Windows 95 o Windows NT server IRQ and address q TCP/IP q Windows NT domain q Net. BIOS, etc. q Chapter 4 Configuration: Client/Server Components 26