Configuring Network Services and Protocols Lecture 2

Windows Server 2003 Network Architecture  4 major components in networking: client, service, protocol and adapter.  Server 2003 has 2 interfaces to make it easier for developers to create clients, services, protocols and adapter software: Network Device Interface Specification (NDIS) and Transport Device Interface (TDI).

NDIS Developers of network card drivers and protocols can independently write code that communicates with NDIS Acts as intermediary for all communication between protocol and network card driver Bindings between protocols and adapters are controlled by NDIS A single adapter can be bounded to multiple protocols and vise versa

TDI Transport Driver Interface Provides clients and services with access to network services Emulates two network access methods: Network Basic Input/Output System (NetBIOS) Windows Sockets (WinSock) NetBIOS is the older network interface WinSock is used by Internet Explorer, Outlook Express, and other internet applications

Examples of some network services Dynamic Host Configuration Protocol (DHCP) Domain Name System (DNS) Windows Internet Naming System (WINS) Routing and Remote Access Service (RRAS) Network Address Translation (NAT) Internet Connection Sharing (ICS) IP Security (IPSec) Internet Connection Firewall (ICF)

Examples of some network protocols TCP/IP IPX/SPX AppleTalk

TCP/IP TCP/IP became a standard protocol suite: Compatibility Scalability Heterogeneity Availability – open standards

TCP/IP basics IP address Subnet mask Default gateway IPCONFIG

Static vs Dynamic Addressing Static Addressing info doesn’t change – “hard-coded” Needs to be configured manually Can’t be used by any other device – “sharing” is not allowed Easy to make a mistake when entering Labor-intensive to change/update Dynamic Addressing info can change dynamically Not configured manually IP addresses can be “shared” – IP address pool Easy to make changes/updates Avoid manual configurations and errors In Server 2003 it’s possible to specify alternate (static) IP configuration to use if DHCP is not available

DHCP DHCP server is installed and address ranges (pools) are configured Clients are configured for dynamic addressing IP information is “leased” Newer clients (XP, Vista) that are unable to contact a DHCP server generate an APIPA address in the /16 network. As an alternative, a client can be confgured to use an alternate IP configuration.

DNS WINS is outdated – only older OS clients require it (WinNT or 98) DNS is the industry standard way to resolve names to IP addresses DNS requires planning and configuration – forward and reverse lookup zones Clients need to be configured to point to DNS server(s). This can be accomplished through DHCP Multiple DNS servers with zone replication can be configured for fault-tolerance and performance improvement

DNS

Make sure to review and understand all relevant DNS concepts, such as forward and reverse resolution, types of records and DNS caching.

DNS and DHCP integration DHCP can be configured to register clients with Dynamic DNS.

TCP/IP tools Ping Tracert Nslookup Ipconfig