Configuring TCPIP Addressing and Names Resolution

1
Configuring TCP/IP Addressing and Names
Resolution

• ICS-023
• Lab 6

2
Lab Overview

• Transmission Control Protocol/Internet Protocol
  (TCP/IP) for Microsoft Windows XP offers a
  standard, routable, enterprise networking
  protocol that is the most widely accepted
  protocol available.
• Most current network operating systems offer
  TCP/IP support, and large networks rely on TCP/IP
  for much of their network traffic.

3
Lab Overview

• TCP/IP identifies source and destination
  computers by their IP addresses.
• To communicate on a network, each computer must
  have a unique IP address and conform to a
  standard format.
• Understanding IP address configuration options
  and basic IP address troubleshooting is necessary
  to successfully connect to the network.

4
Lab Overview

• A device name is generally a user-friendly name
  that uniquely identifies a device on the network.
  An example of a user-friendly name is the name
  that you provide when you install Windows XP.
• For applications that use names instead of IP
  addresses, Windows XP has several possible
  methods to map these names to IP addresses.
• Without the ability to map names to IP addresses,
  applications that use names would not be able to
  communicate in a TCP/IP environment.

5
Lab Overview

• After completing this module, you will be able
  to
• Configure IP addresses and alternate IP settings
  in Windows XP Professional.
• Troubleshoot IP addressing problems by using
  TCP/IP utilities.
• Differentiate between the various name resolution
  methods used by Windows XP Professional.
• Configure a computer running Windows XP
  Professional to use Domain Name System (DNS).
• Describe how to use TCP/IP utilities to connect
  to a remote host.

6
Configuring IP Addresses

• Windows XP provides two methods for assigning IP
  addresses to devices on TCP/IP networks
• Dynamic addressing by using Dynamic Host
  Configuration Protocol (DHCP) to assign an IP
  address.
• Static or manual addressing by physically
  entering the IP address at the client computer.

7
Configuring IP Addresses

• In this lesson you will learn about the following
  topics
• Assigning static IP addresses
• Overview of dynamic address assignment
• Using DHCP to automate IP address assignments
• Enabling alternate IP configuration

8
Configuring IP Addresses

• If a DHCP server is not available and
  communication with hosts outside of a single
  subnet is required, you must use static
  addressing.
• A subnet is a segment of a network that shares a
  network address with other portions of the
  network but is distinguished by a subnet number.
• If static addressing is used, the administrator
  must also determine the IP addresses that will be
  assigned to the network devices.
• DHCP is the preferred method for assigning IP
  addresses.

9
Configuring IP Addresses

• Windows XP provides a new feature for clients
  that use DHCP.
• If a client computer is configured to obtain an
  IP address automatically, we can specify
  alternate IP settings for the same client.
• Whenever the DHCP server is unavailable, the
  alternate IP configuration will be used to
  connect to the network.
• This feature enables portable computers to easily
  switch between an environment in which DHCP is
  available, such as your office, and one that does
  not provide DHCP, such as an Internet service
  provider (ISP).
• After you set the IP address, you can view its
  TCP/IP configuration by using either the Internet
  Protocol (TCP/IP) Properties sheet or the
  ipconfig command.

10
Assigning Static IP Addresses

• Static IP addressing refers to configuring IP
  addresses manually.
• In this method, you assign an IP address to the
  host or network device.
• Windows XP provides the Internet Protocol
  (TCP/IP) Properties sheet to manually assign an
  IP address.

11
Assigning Static IP Addresses

• In addition to specifying the IP address, you
  must specify a subnet mask and a default gateway
  address, if necessary.
• A subnet mask is used to identify whether a
  destination address is on the local subnet or a
  remote subnet. If the destination address is on a
  remote subnet, the local computer will use the
  address of the default gateway for forwarding the
  information outside of the local subnet. If a
  destination address is on the local subnet, the
  information is forwarded to the specified device
  without going through the gateway.
• Therefore, a default gateway address is not
  needed if you only have a single subnet on your
  network and with no requirements to communicate
  outside that local subnet.

12
Assigning Static IP Addresses

• To manually configure the IP address
• On the Start menu, click Control Panel, click
  Network and Internet Connections, and then click
  Network Connections.
• Right-click Local Area Connection, and then click
  Properties.
• In the Local Area Connection Properties sheet,
  click Internet Protocol (TCP/IP), and then click
  Properties.
• In the Internet Protocol (TCP/IP) Properties
  sheet, click Use the following IP address to
  enter values for IP address, Subnet mask, and
  Default gateway, and then click OK twice.

13
Overview of Dynamic Address Assignment

• Dynamic addressing is the default addressing
  method in Windows XP.
• In dynamic addressing, the DHCP server supplies
  an IP address subnet mask, and default gateway to
  the client.

14
Overview of Dynamic Address Assignment

• If DHCP is unavailable, an alternate address is
  provided depending on the client configurations
  found in the Alternate Configuration tab of the
  Internet Protocol (TCP/IP) Properties sheet. The
  following options are available for alternate
  configuration
• Automatic private IP address. The computer will
  use a specified IP address range.
• User configured. The computer will use the
  alternate static IP configuration that is
  specified in the Alternate Configuration tab.
• If a static address is specified, this will be
  the only address that Windows XP Professional
  uses to communicate, and alternate address
  methods will not be available.

15
Using DHCP to Automate IP Address Assignments

• To enable DHCP, you must click Obtain an IP
  address automatically. If you need to change a
  host from static to dynamic addressing
• On the Start menu, click Control Panel, click
  Network and Internet Connections, and then click
  Network Connections.
• Right-click Local Area Connection, and then click
  Properties.
• In the Local Area Connection Properties sheet,
  click Internet Protocol (TCP/IP), and then click
  Properties.
• In the Internet Protocol (TCP/IP) Properties
  sheet, click Obtain an IP address automatically,
  and then click OK.

16
Enabling Alternate IP Configuration

• When you select dynamic addressing on the General
  tab of the Internet Protocol (TCP/IP) Properties
  sheet, you can also specify an alternate IP
  address in the event that DHCP is unavailable.
  After you select Obtain and IP address
  automatically, the Alternate Configuration tab
  becomes available.

17
Enabling Alternate IP Configuration

• In the Internet Protocol (TCP/IP) Properties
  sheet, on the Alternate Configuration tab, the
  options for alternative configuration are
• Automatic private IP address.
• This option assigns an address from the reserved
  address pool for private IP addresses. This pool
  of addresses ranges from 169.254.0.1 through
  169.254.255.254. With this option enabled, DNS,
  Windows Internet Name Service (WINS), or a
  default gateway are not assigned because
  automatic private IP addressing is designed only
  for a small network that consists of a single
  subnet.
• User configured.
• This option assigns the static TCP/IP
  configuration that is specified on the Alternate
  Configuration tab. Settings for IP address and
  Subnet mask are required. All other settings
  (Default gateway, DNS server, and WINS server)
  may be necessary based on your network
  configuration.

18
Troubleshooting IP Addresses

• Windows XP contains several utilities that you
  can use to diagnose network problems.
• For example, you can use TCP/IP troubleshooting
  utilities to modify the Address Resolution
  Protocol (ARP) cache, verify the host name of
  your computer, determine whether a router or link
  is causing network problems, and determine
  whether a router is forwarding packets
  successfully.
• In addition, you can use the ipconfig command to
  verify and modify TCP/IP configuration, and use
  the ping command to test TCP/IP configuration and
  connections.

19
Using TCP/IP Troubleshooting Utilities

• Windows XP provides a number of TCP/IP diagnostic
  utilities that assist users in detecting and
  resolving networking problems. Some of the common
  diagnostic utilities are
• arp
• hostname
• ipconfig
• ping
• pathping
• tracert

20
arp

• Displays and modifies the ARP cache. ARP is
  responsible for identifying the MAC address of
  the destination machine.
• Type arp a to display the information in your
  ARP cache.

21
hostname

• Displays the hostname of your computer.
• Type hostname at command prompt to see the
  computer name.

22
ipconfig

• Displays and updates the TCP/IP configuration,
  including the IP address.
• Type ipconfig /all to display a detailed
  configuration report for all the interfaces.

23
ping

• Tests IP connectivity between two computers.
• Type ping computer_name or ping ip_address at the
  command prompt.

24
tracert

• Traces the route that a packet takes to a
  destination.
• The tracert command displays a list of IP routers
  that are used to deliver packets from source to
  destination, and the amount of time needed.

25
pathping

• It combines the features of ping and tracert
  along with additional features.

26
Using ipconfig to Troubleshoot IP Addressing

• Additional commands useful for troubleshooting an
  IP address are
• ipconfig /release. Releases all connections for
  the computer's adapter.
• ipconfig /renew. Renews the connections for the
  computer's adapter according to the Internet
  Protocol (TCP/IP) Properties sheet.
• These commands are useful when moving from a
  static address to a dynamic address with DHCP.
  The release command releases the static address
  from the adapter, and the renew command sends a
  request to DHCP to assign an address.

27
TCP/IP Name Resolution Methods

• Windows XP has several name resolution methods
  that provide the ability to map names to IP
  addresses.
• You will learn about the following topics
• Types of names
• Mapping names Dynamic or static tables
• Dynamic IP mapping
• Static IP mapping
• Selecting a name resolution method
• Host name resolution process
• NetBIOS name resolution process

28
TCP/IP Name Resolution Methods

• Mapping information is stored in a dynamic table,
  which automatically updates mapping information,
  or in a static table, which must be updated
  manually.
• There are two name resolution methods that
  automatically update mapping information
• Domain Name System (DNS). Translates computer
  names to IP addresses.
• Windows Internet Name Service (WINS). Translates
  NetBIOS names to IP addresses.

29
Types of Names

• There are two types of user-friendly names host
  names and NetBIOS names.
• A host name is a user-friendly name that
  identifies a computer as a TCP/IP host.
• A NetBIOS name is a unique name that is used to
  identify a NetBIOS-enabled computer (for example,
  a computer running Microsoft Windows 98 or
  Microsoft Windows NT version 4.0) on a local
  network.

30
Host Names

• Host names are used in virtually all TCP/IP
  environments. The following list provides a
  description of a host name
• A host name is an alias assigned to a computer by
  an administrator to identify a TCP/IP host.
  Multiple host names can be assigned to the same
  host.
• The host name can be up to 255 characters in
  length and can contain alphabetic and numeric
  characters, hyphens, and periods.
• Host names are easier to remember than IP
  addresses.
• A host name can be used in place of an IP address
  when using ping or other TCP/IP utilities.
• When you append a host name to your computer's
  domain name, you have a fully qualified domain
  name. For example, computer1 in the
  nwtraders.msft domain would have the fully
  qualified domain name, computer1.nwtraders.msft

31
NetBIOS Names

• Although Windows XP does not require NetBIOS
  names, Windows NT 4.0 and other earlier operating
  systems require NetBIOS names to support
  networking capabilities.
• The following list provides a description of a
  NetBIOS name
• A NetBIOS name is a 16-byte name.
• In Windows XP, you cannot configure a NetBIOS
  name as a separate task.
• The NetBIOS name is created by using the first 15
  letters of the host name. The sixteenth and final
  character of the NetBIOS name is used to identify
  the resource or service that is being referred to
  on the computer.

32
Mapping Names Dynamic or Static Tables

• A dynamic table is automatically updated by
  network services with names and IP addresses. To
  accomplish an automatic update, one or both of
  the following services are used
• DNS for host names.
• WINS for NetBIOS names.
• A static table is one in which you manually enter
  names and IP addresses. In a static table,
  mappings are stored in one of two text files
• HOSTS file for host names.
• LMHOSTS file for NetBIOS names.

33
Dynamic IP Mapping

• To accomplish automatic update, the dynamic
  tables use one of two services
• DNS for host names and
• WINS for NetBIOS names.

34
Domain Name System

• The purpose of the DNS database is to translate
  computer names into IP addresses. When a user
  enters a domain name in an application, the DNS
  service maps the name to an IP address.
• Each computer that stores the domain name-to-IP
  address mapping records has mappings for only its
  area.
• These computers, known as DNS servers, only
  process queries for computers located in their
  respective areas.
• As the mappings in the area change, DNS servers
  can be updated automatically with the new
  information.

35
Windows Internet Name Service

• In Windows XP, the primary means for client
  computers to locate and communicate with other
  computers on a TCP/IP network is by using DNS.
• However, clients using previous versions of
  Windows, such as computers running Microsoft
  Windows 98 or Microsoft Windows NT 4.0, also use
  NetBIOS names for network communication. As a
  result, these clients require a method of
  resolving NetBIOS names to IP addresses.
• WINS maps NetBIOS names to IP addresses and
  enables NetBIOS names to be used across routers.

36
Static IP Mapping

• If you implement a HOSTS file or LMHOSTS file, a
  copy of this file resides on each computer in the
  network.
• The advantage of using the text file is the
  ability to customize it.
• However, if the file contains a large number of
  IP address mappings or if the IP addresses
  change, the maintenance task becomes equally
  large.

37
HOSTS File

• The following list describes the HOSTS file
• A single entry consists of an IP address
  corresponding to one or more host names.
• A HOSTS file must reside on each computer.
• The HOSTS file is used by ping and other TCP/IP
  utilities to resolve a host name to an IP address
  on both local and remote networks.
• The HOSTS file can be edited with any text
  editor. When first viewing the HOSTS file, its
  content is empty. It requires an administrator to
  add entries. The directory location
  issystemroot\system32\drivers\etc\

38
LMHOSTS File

• The LMHOSTS file is a text file that contains the
  IP address-to-NetBIOS name mappings.
• The LMHOSTS file has the following
  characteristics
• It resolves NetBIOS names used in Windows NT and
  other NetBIOS applications.
• Entries consist of one NetBIOS name and its
  corresponding IP address.
• Each computer has its own file. A sample file,
  Lmhosts.sam, is provided with Windows XP.
• After modifying the sample file with LMHOSTS
  entries, the file must be renamed as Lmhosts
  without an extension to be recognized by NetBIOS.
  The directory location issystemroot\system32\
  drivers\etc\lmhosts.sam

39
Selecting a Name Resolution Method

• You need to determine whether your environment
  and client requirements must be configured with
  DNS only, or DNS and WINS.
• DNS is required when the client computer
• Is a member of an Active Directory domain.
• Needs to communicate over the Internet.
• WINS is required when the client computer
• Is a member of a Windows NT 4.0 or earlier
  domain.
• Uses applications or services that require
  NetBIOS name resolution.

40
Host Name Resolution Process

• The default host name resolution process is as
  follows
• The user issues a command on Computer A, such as
  ftp, specifying the host name of Computer B.
• Computer A checks to determine whether the
  specified name matches a local host name.
• Computer A checks to determine whether the
  specified name is in its DNS name cache.
• If the name does not match, Computer A checks its
  HOSTS file looking for Computer B's name.
• If Computer A does not find Computer B's host
  name in the HOSTS file, it sends a query to the
  DNS server.
• If the host name is not found on the DNS server,
  Windows XP Professional checks for the name in
  the NetBIOS name cache.
• If the NetBIOS name cache does not have the
  NetBIOS name, a query is sent to the WINS
  server.
• If the WINS server cannot resolve the name, a
  broadcast message is sent out on the network.
• If no host responds to the broadcast, the LMHOSTS
  file is checked for the host or NetBIOS name.
• If the name is not found, an error message is
  returned to Computer A.

41
Configuring a DNS and WINS Client

• Windows XP uses DNS as its primary method for
  name resolution and to locate services, including
  domain controllers that provide user
  authentication.
• If your environment has multiple DNS servers, in
  Windows XP, you can specify which DNS servers to
  query and what order to perform the query.
• The reasons to have secondary DNS servers are
• Redundancy. If one of the servers becomes
  unavailable, another server can provide the DNS
  service.
• Faster access for remote locations. If you have a
  number of clients in remote locations, having
  secondary name servers or other primary name
  servers for subdomains prevents these clients
  from communicating across slow links for name
  resolution.
• Reduction of load. Secondary name servers reduce
  the load on the primary server.

42
Specifying Host Names, Domain Names, and
Connection-Specific Names

• To view or change the host name and the primary
  DNS suffix
• Click Start, right-click My Computer, and then
  click Properties. On the Computer Name tab, the
  fully qualified domain name is provided.
• To change the host name, click Change, and then
  type the new name in the Computer name text box.
• To change the primary DNS suffix of the computer,
  click More, and then type a name in the Primary
  DNS suffix of this computer text box.

43
Specifying Host Names, Domain Names, and
Connection-Specific Names
44
Configuring a DNS Client

• A DNS client uses a DNS server to resolve queries
  and locate resources on the network. In Windows
  XP, configuring a computer as a DNS client
  involves only one configuration parameter the IP
  address of the DNS server. The configuration of a
  secondary or alternate server is optional, but
  recommended.To configure a client to use a DNS
  server for name resolution
• Click Start, click Control Panel, click Network
  and Internet Connections, and then click Network
  Connections.
• Right-click the desired network connection, and
  then click Properties.
• In the list box, click Internet Protocol
  (TCP/IP), and then click Properties.
• If you want a DHCP server to provide DNS server
  addresses, click Obtain DNS server address
  automatically.
• If you want to manually configure an IP address
  for a DNS server, click Use the following DNS
  server addresses, and then type the IP address of
  the primary server in the Preferred DNS server
  box.
• If a second DNS server is configured, type the IP
  address of the additional DNS server in the
  Alternate DNS server box.If the primary server
  is unavailable, Windows XP Professional will
  query the second DNS server for host name
  resolution.

45
Configuring DHCP to Dynamically Update DNS

• When a client receives a new IP address from a
  DHCP server, the name-to-IP address mapping
  information that is stored on a DNS server must
  be updated.
• In Windows XP, DHCP servers and clients can
  register with and dynamically update name-to-IP
  address mapping information on DNS servers that
  are configured to support dynamic updates.

46
Configuring Windows XP-based Clients for Dynamic
Updates

• To configure Windows XP Professional-based
  clients to update the DNS database
• In Network Connections, right-click the
  connection that you want to configure, and then
  click Properties.
• In the Properties sheet for the connection, click
  Internet Protocol (TCP/IP), and then click
  Properties.
• On the Internet Protocol (TCP/IP) Properties
  sheet, click Advanced.
• In the Advanced TCP/IP Settings dialog box, on
  the DNS tab, select the appropriate check box
• Register this connection's addresses in DNS.
  Enables the client to register resource records
  in DNS by using the full computer name and the IP
  address of the network connection.
• Use this connection's DNS suffix in DNS
  registration. Enables the client to register
  resource records in DNS by using the first label
  of the computer name in addition to the DNS
  suffix for the connection. Use this option only
  if the DNS suffix differs from the domain name.

47
Troubleshooting DNS Name Resolution
48
Troubleshooting DNS Name Resolution

• In Windows XP, you can use nslookup to assist you
  in locating the origin of the problem.
• nslookup Utility
• nslookup is a command-line utility that you can
  use to query and troubleshoot your DNS
  installation. Name resolution errors can result
  if one or more of the following occur
• DNS client entries are not configured correctly.
• A DNS server is not running.
• There is a problem with network connectivity

49
Troubleshooting DNS Name Resolution

• If the DNS server is offline, the DNS service is
  not enabled on the host computer, or a hardware
  or routing problem exists, the following message
  appearsC\nslookup Can't find server name
  for address ltIP_Addressgt No response from
  server Default servers are not available.
  If a query is successful, the following message
  appearsC\nslookupDefault Server
  ltfully_qualified_domain_namegtAddress w.x.y.z

50
Configuring a WINS Client

• WINS provides a method of NetBIOS name resolution
  that reduces broadcast traffic and enables
  clients to resolve NetBIOS names of computers
  that are on different network segments.
• For WINS to function properly on a network, each
  client must register its name in the WINS
  database.

51
Configuring a WINS Client

• To configure a WINS client manually
• On the Internet Protocol (TCP/IP) Properties
  sheet, click Advanced.
• In the Advanced TCP/IP Settings dialog box, on
  the WINS tab, click Add.
• Type the IP address of the WINS server, and then
  click Add.
• Repeat steps 2 and 3 to add additional WINS
  servers.

52
Connecting to a Remote Host

• Working with FTP
• Working with Telnet
• Using HyperTerminal

53
Connecting to a Remote Host

• Windows XP provides access to remote hosts with
  the standard TCP/IP protocol suite of
  applications, including FTP (File Transfer
  Protocol) and Telnet.
• File Transfer Protocol (FTP) is an application
  level protocol, used for transferring files to
  and from remote computer systems.
• Telnet is an application-level protocol that
  enables a user to log on and use a remote
  computer as if that user were sitting directly at
  that computer.
• Windows XP provides both client and server
  services for these two TCP/IP applications.

54
Working with FTP

• FTP sessions require a server and a client.
• The server responds to requests from clients.
  Typically, the server is the repository of files.
  
• Clients either upload files to the server or
  download files from the server.
• Windows XP provides various client FTP interfaces
  along with the tools for hosting FTP sites with
  the use of Internet Information Services (IIS).
• IIS provides an FTP server along with other
  virtual servers to support TCP/IP applications.

55
Working with FTP
56
Windows XP IIS FTP Server

• To configure a computer running Windows XP as an
  FTP server
• From Control Panel, click Add or Remove Programs,
  click Add/Remove Windows Components, click
  Internet Information Services (IIS), and then
  click Details.
• Select the File Transfer Protocol (FTP) Service
  check box, click OK, and then click Next. If
  prompted, insert your Windows XP Professional CD.
  After the necessary files are copied, click
  Finish.
• In the Computer Management console, under
  Services and Applications, under Internet
  Information Service, under FTP Sites, right-click
  Default FTP Site, and then click Properties.
• To establish a secure server, configure the
  following settings
• On the FTP Site tab, select the Enable Logging
  check box.
• On the Security Accounts tab, select Allow
  Anonymous Connections and Allow Only Anonymous
  Connections.
• On the Messages tab, under Welcome, type the
  following warning message All access to this
  server is logged. Access to this server is
  allowed by permission only and unauthorized use
  will be prosecuted.
• When you are finished, click OK.

57
Windows XP Professional FTP clients

• Windows XP comes with three FTP clients.
  Selecting to use one client over another is based
  on user preference.
• The first FTP client is a command-line utility,
  Ftp.exe, which contains the full FTP feature set.
  
• The second FTP client is integrated with Windows
  Explorer. Windows Explorer adds a full-featured
  graphical user interface for FTP, making folders
  and files on an FTP server look and work much
  like files on a local hard disk.
• Microsoft Internet Explorer offers a third
  alternative for interacting with FTP sites a
  text-based view that visually resembles directory
  listings in Microsoft MS-DOS, but contains
  hyperlinks for navigation and downloading.

58
Command-Line FTP

• To use the command-line FTP client
• Click Start, click Run, in the Open box, type ftp
  and then click OK.A command session window
  opens, and the prompt changes to ftp.
• Open FTP sites, browse their contents, and
  download or upload files. The command-line format
  for using FTP is found by typing Help at the ftp
  prompt.

59
Windows Explorer Graphical FTP Client

• To use the Windows XP graphical FTP client in
  Windows Explorer
• Open Windows Explorer.
• Type the ftp address in the Address box, for
  exampleftp//sitenameThe graphical FTP
  client is running. The FTP Welcome message is
  available by selecting FTP Server Welcome Message
  from the Help menu. The welcome message appears
  at the left side of the window if you enable Web
  view.

60
Windows Explorer Graphical FTP Client

• The graphical FTP client logs you on anonymously.
  To log on by using another account, use either of
  the following two methods
• Type the account name and password in the ftp
  address in the formftp//usernamepassword_at_site
  name
• On the File menu, click Login As. This opens a
  dialog box for the user name and password.

61
Windows Explorer Text-Based FTP Client

• Enabling the Windows XP text-based FTP client
  will disable the graphical FTP client in Windows
  Explorer. This client enables only browsing and
  downloading. This FTP client does not provide a
  Login As menu command or a command line to enter
  commands. To access an FTP site by using a
  text-based FTP client
• Open Internet Explorer.
• On the Tools menu, click Internet Options, click
  the Advanced tab, and under Browsing, clear the
  Enable folder view for FTP sites check box.
• Type the ftp or IP address in the Address
  bar.The text-based FTP client logs you on
  anonymously.
• To log on by using a user name and password, you
  must enter this information in the Address box in
  the formftp//usernamepassword_at_sitename

62
Working with Telnet

• Telnet is a TCP/IP protocol. Telnet server and
  Telnet client software are installed as part of
  the standard Windows XP installation.
• The Telnet client and the Telnet server work
  together to enable users to communicate with
  other TCP/IP connected hosts and servers.

63
Telnet Client

• The Telnet client enables you to connect to a
  TCP/IP server and interact with that server
  through a terminal window as if you were sitting
  in front of it.
• Typical uses of Telnet include e-mail, file
  transfer, and system administration, all of which
  involve remotely issuing commands to a Telnet
  server.

64
Telnet Server

• The Telnet server is a connection point for
  Telnet clients.
• When the Telnet server is running on a computer
  running Windows XP, users on other workstations
  running Telnet client software can connect to the
  computer running Windows XP.
• When a Telnet client connects to the Telnet
  server running Windows XP, the user is asked to
  enter a user name and password.
• After logging on, a user is given a command
  prompt that can be used as if it had been opened
  in a command prompt window locally.

65
Working with Telnet

• To control the access that Telnet users have to
  files on the server, use only NTFS on the system
  partition.
• Create a Telnet Users Group, add all Telnet users
  to that group, and then assign files and
  directory permission to control the access that
  members have to the files and directories.The
  Telnet server service is not started by default.
  To start the Telnet service
• Click Start, right-click My Computer, and then
  click Manage.
• In Computer Management, expand Services and
  Applications, and then click Services.
• In the details pane, right-click Telnet, and then
  click Start.
• Note The Telnet server included with Windows
  XP Professional supports a maximum of two Telnet
  clients at a time. If you need additional
  licenses, use Telnet server from the Microsoft
  Services for UNIX. Services for UNIX supports up
  to 63 Telnet clients at a time.

66
HyperTerminal Telnet Client

• HyperTerminal is a general-purpose Windows
  application that provides a Windows graphical
  user interface and features to the application
  invoked, in this example, Telnet.
• To start HyperTerminal
• Click Start, click All Programs, click
  Accessories, click Communications, and then click
  HyperTerminal.
• In the New Connection dialog box, type a
  telnet_server host name in the Name text box, and
  then click OK.If the New Connection dialog box
  does not open automatically, click File, and then
  click New Connection.
• In the Connect To dialog box, in the Connect
  using list, select TCP/IP (Winsock), and then
  click OK.This action initiates the Telnet
  connection as a client.
• In the Connect To dialog box, in the Host Address
  box, type the IP address of the remote host or
  the remote_host_name (where remote_host_name is
  the name of the host to which you want to
  connect), and then click OK.
• To close the Telnet session, type quit in the
  command window.

67
(No Transcript)
68
(No Transcript)
69
(No Transcript)
70
(No Transcript)
71
(No Transcript)