Tcp/Ip

UNIX clients won't be able to get the DHCP options.

The RIP service/protocol is required for dynamic updates of routing tables.

All computers must be capable of running Microsoft NT Server 4.0 and meet the NT 4.0 Hardware Compatibility List (HCL).

Request for Comments (RFCs) describe the internal workings of the Internet.

All the steps have been taken to enable dynamic routing and the interface addresses are compatible with the mask that has been assigned. They have properly configured their NT server as a router whose route table will be updated automatically. By installing the WINS server service and configuring the MS clients to use WINS, they have met the first optional objective. They will be able to communicate with the NT machines using the NetBIOS or Machine names because the WINS service will resolve and return the IP addresses. They have accomplished the second optional objective by installing a DNS server. The MS machines may resolve the host name to IP address of the UNIX machines because the records will be part of the zone file. This will allow them to initiate an FTP session using the host name. The UNIX machines will be able to resolve the MS machine names because the DNS zone will be configured to query the WINS server for the IP address of the MS machines.

UDP is a transport layer protocol that provides connectionless delivery of datagrams.

A thorough discussion of many of the IP stack protocols is included in the Student Manual, Module 2: Architectural Overview of the TCP/IP Protocol Suite.

TCP is a transport layer protocol that uses sequence numbers and acknowledgements to achieve a connection oriented delivery service.

These publications are published in a series of documents called Request for Comments which describe the internal workings of the Internet.

The Computer Browser service uses NetBIOS broadcasts to obtain lists of network resources.

Applications create a Socket by specifying three items: The IP address of the host, the type of service (TCP for connection-based service, UDP for connectionless) and the port the application is using.

TCP/IP protocols follow a four-layer conceptual model: Application, Transport, Internet and Network Interface. These protocols provide a set of standards for how computers communicate and how networks are interconnected.

TCP/IP is an industry-standard suite of protocols designed for wide area networks.

When you want to connect with another network a default gateway is necessary.

Review the RFC 1723 and requirements for multihomed computers.

A computer running Windows NT can be configured with multiple network adapters and route between them. This type of system is ideal for small intranets and is referred to as a multihomed computer.

"#DOM:domainname" denotes a domain controller and can be used by the local machine to validate logon requests and to exchange master browser lists with the domain master browser.

"#INCLUDE" is used to include the location of LMHOSTS files on other hosts on the network. This can be used to include a centrally maintained LMHOSTS file in the path of the local machine.

The faster the better. Configure a push partner when servers are connected by fast links, because push replication occurs when the configured number of updated WINS database entries are reached.

Resolving the Host name given an IP adress requires the creation of a reverse lookup zone consisting of pointer records. The zone must have the name Y.X.in_addr.arpa, where Y and X are the reverse order of the octets values that define the default network. The actual resolver must reverse the IP address so that lookup may be understood by the Name Server.

When TCP/IP hosts try to communicate, they use the subnet mask to determine whether the destination host is on a local or remote network. To communicate with a host on another network, you must configure an IP address for the default gateway.

Static routes may be added to the local routing table with the ROUTE command.

Network address. The network ID or network name of the destination network. If a network name is used for the destination, it is looked up in the Networks file. Netmask. The subnet mask for the network address. Gateway address. The IP address or host name of the interface to the destination network. If a host name is used for the gateway, it is looked up in the Hosts file.

Static routing is a function of Internet Protocol.

DHCPNAK is a negative acknowledgement of a request.

Packets that are local may be sent to the gateway and packets that are remote may stay local. Before a packet is sent the destination IP address is ANDED with the source host's subnet mask. This is compared with the results of the source host's IP address ANDED with the subnet mask. If the values differ, the packet is sent to the gateway.

If the administrator had entered a static entry for SERVER2 then IP would continue to use this hardware address. However when a NIC card changes usually the hardware address changes also. If the administrator had not entered a static entry, ARP would have broad-casted for the hardware address and there would have been no problem. A thorough discussion of Arp and the Arp Cache is included in the Student Manual in Module 2: Architectural Overview of the TCP/IP Protocol Suite.

Arp discovers the hardware address of the local destination host by issuing an Arp Request broadcast requesting the hardware or MAC address of the destination. If IP determines that the destination host is remote then Arp sends a broadcast requesting the hardware address of the default gateway. A thorough discussion of Arp is included in the Student Manual in Module 2: Architectural Overview of the TCP/IP Protocol Suite.

If duplicate addresses exist on the same network, the second NT host will not initialize. An error message is sent to the host and the other owner of the IP address. Implementations on other operating systems could lead one or both of the hosts to hang.

Host name resolution is generally needed when a TCP/IP client utility needs to connect to a TCP/IP server. Telnet, FTP clients as well as the PING utility all require host name resolution.

Unique names are typically used to send network communication to a specific process on a computer with the net use command. NetBIOS Names are assigned at installation. The NetBIOS Name is the machine name.

When a user initiates Windows NT command, such as net use, the NetBIOS name resolution process begins.

Unique names are typically used to send network communication to a specific process on a computer with the net use command. NetBIOS Names are assigned at installation. The NetBIOS Name is the machine name.

Windows NT 4.0 provides support for all of the NetBIOS over TCP/IP nodes defined in RFCs 1001 and 1002. WINS can reduce network traffic by removing the B-node Broadcasts.

The loopback adress starts with 127.
Class "B" 128 - 191
Class "C" 192 - 223
Class "D" 224 - 239 Multicast
Class "E" 240 - 254 Experimental

The first two octets contain class B network address.

You can identify the class of address by the number in the first octet. The 32-bit IP addressing scheme supports a total of 3,720,314,628 hosts.

127 is reserved for analysis, all ones or zeros are not permitted.

First three octets address the network.

32 bits is standard TCP/IP address. Each of the four octets contain 8 bits. 10001011.10101010.00000111.10000001 = 139.162.7.129

Defined as the last class A network address even though it is used for loopback.

Class C addresses are used for small LANs. The three high-order bits in a Class C address are always set to binary 1 1 0. The next 21 bits (completing the first three octets) complete the network ID. The remaining 8 bits (last octet) represent the host ID. this allows for approximately 2 million networks and 254 hosts per network.

Class D addresses are use for multicast group usage.

Class B addresses are assigned to medium-sized to large-sized networks. Actual number is 65,534 for available hosts on a Class B address. It is 16,777,214 for Class A and only 254 for Class C.

To convert a number to binary use the highest numbers possible, e.g., 255 is 11111111 since 128+64+32+16+8+4+2+1=255. Note that the binary position second from the left cannot be used since the value of 170 would be exceeded, i.e., 11000000=192, etc.

Use a calculator or write out a table, starting with the value for 2 to the zero power, thence for values up to 2 to the 7th power. This can be used for a table that associates these values with subnet masks and digit position values. Starting from the left the decimal numbers are 128, 64, 32, 16, 8, 4, 2 and 1. By looking at the binary number you can see that 10001011 is equal to 128+8+2+1 or 139.

The network address ending with a node zero or 255 address could be a broadcast for your network. Although this is a class B address, the first three numbers are masked, thus 137.4.142 is the network portion.

An address with a 192 value in the first octet is a Class C address because it ranges between 192 and 223. In a Class C address the first 3 octets define the network portion. In this example the network portion is 192.200.254. The network address is 192.200.254.0

First you recognize that you are dealing with a Class C address. Next, you know that a subnet mask ending value of 252 accommodates 2 hosts per subnet, 248 - 6, 240 - 14, 224 - 30 and 192 - 62, thus the only correct choices to allow for at least 10 hosts per subnet are 224 and 240. Note, also, that a subnet mask of 255.255.255.192, while accommodating 62 hosts per subnet, only allows for two subnets.

Addresses of zero or 255 could be broadcast address for your network and are not allowed.

The three choices are for a class A, class B and class C address. Since 2 raised to the power of 5 is 32, there are 30 subnets available for this subnet mask. Also note that 2 to the power of 3 equals 8 and 256-248=8, i.e., the spread, step, or block is 8. Use this to calculate all the subnets, e.g., 8, 16,24,32,40, etc. up to 248.

Address listings;
Class A 1.0.0.0 - 127.0.0.0
Class B 128.0.0.0 - 191.0.0.0
Class C 192.0.0.0 - 223.0.0.0
Class D 224.0.0.0 - 239.0.0.0 Multicasting
Class E 240.0.0.0 - 255.0.0.0 Experimental

255.255.255.0 is the default subnet mask for a Class C address. Class C addresses have 2,097,152 networks available and can have 254 hosts per network.

The address shown must be recognized as a Class B address, thus the subnet mask is 255.255.0.0.

62 subnets are accommodated with a subnet mask of 255.255.255.252 for a Class C IP address where you can have two hosts per subnet. This question appears to assume a Class B address and thus the subnet mask of 255.255.254.0 would work since it accommodates 126 subnets with 510 hosts per subnet. Also the subnet mask of 255.255.252.0 will work since it can have 62 subnets with 1022 hosts per subnet.

The Class B subnet mask 255.255.252.0 will allow a maximum of 62 subnets with up to 1022 valid nodes or IP addresses on each. This meets the stated requirements.

An invalid IP address will prevent proper name resolution. The proper format for the entry is to list the IP address first then the host name.

This address is a Class B address because the value of the first octet ranges between 128 and 191. The default subnet mask for a Class B address is 255.255.0.0. The network portion of the address is the value of the first 2 octets, 131.2.0.0.

A different mask in this case causes your PC to send all traffic to the default gateway as if your target was remote. For comprehensive documentation on monitoring NT Server performance, see the NT Server Resource Kit version 4.0.

A different mask in this case causes your PC to send all traffic to the default gateway as if your target was remote.

If IP checks the destination IP address and determines that it is remote it will then check to see if a specific path is designated in the local routing table. If no particular entry is designated for the destination network then IP uses the default gateway. The source host first checks the Arp Cache for the default gateway's MAC or hardware address. If there is no entry then the ARP protocol broadcasts a request for the gateway's MAC address. The gateway issues an ARP reply containing its MAC address.

If a network is using TCP/IP as its protocol then it must use IP addresses. IP addresses are used by the INTERNET layer to identify the proper network and node that represents a destination host. On broadcast based networks such as Ethernet and Token Ring it is necessary to include the MAC or hardware address in another header of the destination packet. The destination host reads packets that are addressed to its hardware address and does not read packets addressed to other hardware addresses. Hardware addresses are resolved using the Address Resolution Protocol (ARP).

Type arp at the command prompt to see the proper syntax. ARP is used to display and modify the IP to MAC address translation tables, i.e., the IP to NIC address tables. ARP -a displays current ARP entries. You may enter a static entry into the Arp cache by using the arp -s command.

The default is a 2 minute life for unused entries and a maximum 10 minute life for used entries. This may be changed by setting the "ARPCacheLife" parameter in the registry.

Both of these commands display the contents of the Arp Cache.

046 Specifies the type of NetBIOS over TCPO/IP name resolution to be used by the client. 044 Specifies the IP address of a WINS server available to clients.

Before you install WINS, you must determine that your sever and clients meet the configuration protocol.

Each host entry is limited to 255 characters, and entries in the HOSTS file are not case sensitive.

To be a client of a DHCP server the client machine must be configured to obtain an address from a DHCP server. The DHCP server must be configured with a scope that will provide at least the IP address and subnet mask. The client must be configured to get an address from a DHCP server. To receive an address the Client sends a broadcast called a DHCP Discover packet that will not go through a router unless the router is configured to forward it. The scenario is a routed environment. They have configured forwarding of BootP packets at the routers. This achieves the primary objective without having to include a DHCP server on each subnet. Neither of the optional objectives are achieved because they set up the WINS server but they did not configure the clients to use WINS.

To be a client of a DHCP server the client machine must be configured to obtain an address from a DHCP server. The DHCP server must be configured with a scope that will provide at least the IP address and subnet mask. The client must be configured to get an address from a DHCP server. To receive an address the Client sends a broadcast called a DHCP Discover packet that will not go through a router unless the router is configured to forward it. The scenario is a routed environment. They have configured forwarding of BootP packets at the routers. This achieves the primary objective without having to include a DHCP server on each subnet. To be a WINS client the machine needs to be configured with the address of a WINS server. If the WINS address is coming from a DHCP server, the DHCP must also configure the client to be an H-node. H-node means that the client will check the WINS server for name resolution before it tries using a subnet broadcast.

Since DHCP is in use, typing "ipconfig /release" at the command line on Lee's computer will release that IP address and allow DHCP to re-assign it to another user.

DHCP assigns IP addresses, and DNS assigns host names; but, DHCP does not inform DNS of the host names DNS assigns.. Systems that use DNS and DHCP and supply Internet access to local users often have conflicts when DHCP assigns a client a different IP address from the one DNS is expecting. Use DHCP Manager to view and change parameters for Microsoft DHCP servers on the network. You must have administrative privileges. With it you can view DHCP scopes and reserve leases with unlimited durations for clients.

DHCP allows the dynamic assignment of IP addresses and can be configured with different lease durations. Client reservations can be made which designate a particular IP address for a particular host. They do not allow for setting IP addresses by time of day. With only 45% utilization of the network, DHCP with short lease durations should minimize the problems with keeping 164 users supplied with IP addresses, even with only 128 IP addresses available.

The Ping command is used to validate TCP/IP communication.

Arp -a will display the ARP cache and also allow the addition of ARP entries. Entries unused are removed from the ARP cache after 2 minutes and used entries are removed after 10 minutes.

Arp -a will display the ARP cache and also allow the addition of ARP entries. Entries unused are removed from the ARP cache after 2 minutes and used entries are removed after 10 minutes.

Arp tables only display MAC addresses from the local subnet. Therefore when you ping a remote site, the gateway is in the Arp cache. Arp -a will display the ARP cache and also allow the addition of ARP entries. Entries unused are removed from the ARP cache after 2 minutes and used entries are removed after 10 minutes.

The HOSTS file provide name resolution for IP host names for Unix environments. This file is located in \system32\drivers\etc

The HOSTS file provide name resolution for IP host names for Unix. This file is located in \system32\drivers\etc

The LMHOSTS file provides NetBios name resolution for IP to host names for Microsoft environments. This file is located in \system32\drivers\etc

The LMHOSTS file provides NetBios name resolution for IP to host names for Microsoft environments. This file is located in \system32\drivers\etc

The NETWORKS file provides name resolution for network names to IP network id's. This file is located in \system32\drivers\etc

The Services file will provide resolution from a service name to a port number and protocol name. This file is located in \system32\drivers\etc

If the Mask on WKS01 is not the same then a router or routing entry will be the only way to reach it.

In the same subnet, the IP and MASK are required. In a different subnet, the IP and MASK and Gateway are required.

Because we are dealing with NetBios, we need to support both browsing and domain services. For this reasons, the WINS server must pass added information which include name and domain data.

Remember that NetBios information is not passed through the router there fore name resolution can only be solved by using a WINS server somewhere or an LMHOSTS file on the local system.

The SMS (System Management Server) version of network monitor is required to monitor multiple servers. The version that comes with NT 4.0 only supports the local system and not promiscuous mode.

The SNMP service is required to see the performance monitor objects for TCP/IPThe SNMP service is required to see the performance monitor objects for TCP/IP

Remember that NetBios information is not passed through the router there fore name resolution can only be solved by using a WINS server somewhere or an LMHOSTS file on the local system. For regular HOST name resolution, a Unix or NON-Microsoft specific name resolution system, use a HOSTS file or configure a DNS server.

Even though you are using a Proxy, normal IP rules must still be followed on your network.

A WINS IP address is required because all WINS clients are pointing to a WINS IP address.

Implement a WINS server on the main subnet and configure each client to register to that server, a DHCP server on each subnet supporting the scope and options for the local subnet, and a WINS proxy agent must be added to support name resolution for Non-WINS clients

Implement a WINS server on the main subnet and configure each client to register to that server, a DHCP server on each subnet supporting the scope and options for the local subnet, and a WINS proxy agent must be added to support name resolution for Non-WINS clients

Implement a WINS server on the main subnet and configure each client to register to that server, a DHCP server on each subnet supporting the scope and options for the local subnet, and a WINS proxy agent must be added to support name resolution for Non-WINS clients

Implement a DNS server on the backbone network and configure ALL clients to resolve from it, a single DHCP server on the backbone segment with a IP scope for each subnet, one NT Server with the DHCP relay agent on each non-backbone network, a WINS server on the backbone, and configure ALL subnet clients with the WINS server address

Implement a DNS server on the backbone network and configure ALL clients to resolve from it, a single DHCP server on the backbone segment with a IP scope for each subnet, one NT Server with the DHCP relay agent on each non-backbone network, a WINS server on the backbone, and configure ALL subnet clients with the WINS server address

Implement a DNS server on the backbone network and configure ALL clients to resolve from it, a single DHCP server on the backbone segment with a IP scope for each subnet, one NT Server with the DHCP relay agent on each non-backbone network, a WINS server on the backbone, and configure ALL subnet clients with the WINS server address

A DHCP server must be reachable by a broadcast on a local subnet by the DHCP clients but WINS servers can cross routers because they are direct IP requests. In this case replication should be set up between slow link to keep performance at par.

Of course the default SNMP community is public. This is a standard.

When you are configuring the SNMP agent on your NT Server, a MIB gives access to manageable host objects with SNMP.

Specify an SNMP community name and specify the IP address of valid SNMP managers. This will allow NT to provide MIB information from the NT server to SNMP managers. Remember that NT is NOT an SNMP manager.

This indicates a default class B network.

This indicates a default class C network.

LPQ stands for Line Printer Queue. It displays the status of a UNIX based printq.

DHCP servers require their own IP address.

Hosts and DNS relate to Unix and LMHOSTS and WINS relate to NetBios. WINS and DNS require NT. LMHOSTS and HOSTS are static mapping files locates on the local clients.

Hosts and DNS relate to Unix and LMHOSTS and WINS relate to NetBios. WINS and DNS require NT. LMHOSTS and HOSTS are static mapping files locates on the local clients.

The DHCP server must be reachable by a broadcast on a local subnet by the DHCP clients but WINS server can cross routers because they are direct IP requests.

If you have five modems for example then you would actually need five IP addresses. However, if you lease an address for 8 bits then the IP would be tied up for eight hours. This way IP addresses are available without delay.

DNS or Domain Name Services is a database of Domain and Hosts name information referenced to IP addresses. This evolved from Unix based systems.

A WINS server must have a static manually configured IP address because hosts point to the server by address. If you use a DHCP server then the WINS address will be given out with other IP information.

Creating secondary DNS servers which point to primary servers will facilitate backup domain services in the event that the primary server becomes unavailable.