Novell is now a part of Micro Focus

Troubleshooting TCP/IP Communication Issues in the NetWare 5 Environment

Articles and Tips: article

Neil Cashell
Worldwide Support Engineer
Novell, Inc.
ncashell@novell.com

01 Jun 2000


This document addresses TCP/IP communication-related issues that generate about a third of the support calls coming into the TCP/IP group at Novell Technical Support. We recommend that anyone who is implementing TCP/IP in a NetWare 5.x environment read and understand the information presented here.

This AppNote is divided into three parts: understanding the concepts behind IP routing and subnetting, general troubleshooting methods, and solutions to common TCP/IP problems.

For more information, visit Novell's Technical Support Web site at:

http://support.novell.com

Concepts Behind TCP/IP Communication

This section present conceptual information to help you understand how TCP/IP communication works in terms of routing and subnetting.

TCP/IP Routing

The majority of connectivity issues involve problems with routing table entries. Every packet being processed by a TCP/IP host has a source and destination IP address. Upon receiving each packet, the IP protocol examines the destination address of the packet, compares it with entries in its local routing table, and then decides what action to take:

  1. If the destination IP address is itself (that is, to a local application such as GroupWise, BorderManager Proxy Server, and so on), the packet is passed up to a protocol layer above IP.

  2. If the packet is destined for another known network, the packet is forwarded through one of the locally-attached network adapters. (This assumes that the TCP/IP host has multiple interfaces and has routing enabled.)

  3. If neither of the above applies, the packet is discarded.

TCP/IP routing tables can maintain four different types of routes, listed below in the order that they are searched for a match:

  • Host (a route to a single, specific destination IP address)

  • Subnet (a route to a subnet)

  • Network (a route to an entire network)

  • Default (used when there is no other match)

Before we trace this process of searching for routing matches, we need to explain a little more about IP addressing and subnetting.

Subnetting

IP has three classes of addresses: Class A, Class B, and Class C. These classes are further subdivided through a process known as subnetting. In essence, subnetting divides a class of addresses into extra networks.

Subnetting an IP network can be done for a variety of reasons. It can be used to separate organizational boundaries, to segment different physical media (such as Ethernet, FDDI, WAN, and so on), to preserve address space, and to ensure security. But the most common reason for subnetting is to control network traffic.

For example, in an Ethernet network, all nodes on a segment see all the packets transmitted by all the other nodes on that segment. Performance can be adversely affected under heavy traffic loads, due to collisions and the resulting retransmission of packets. To alleviate this, you use a router to connect IP networks and therefore minimize the amount of traffic each segment receives.

Subnet Masks. Each class contains a default subnet mask. The default subnet masks for each class are:


Class
Decimal
Binary

Class A

255.0.0.0

11111111.00000000.00000000.00000000

Class B

255.255.0.0

11111111.11111111.00000000.00000000

Class C

255.255.255.0

11111111.11111111.11111111.00000000

Once a network is subnetted, the IP addresses will no longer have the default subnet mask.

Applying a subnet mask to an IP address allows you to identify the network and node parts of the address. Performing a bit-wise logical AND operation between the IP address and the subnet mask results in the Network Address or Network Number.

For example, if you take a Novell-registered IP address and apply the default Class B subnet mask, you get the Network Address as shown in Figure 1.

Figure 1: Applying the default subnet mask to obtain a Network Address.

You can add additional bits to the default subnet mask for a given class to further subdivide a network. When a bit-wise logical AND operation is performed between the subnet mask and IP address, the result defines the Subnet Address.

To calculate the total possible number of subnets, or nodes, use one of the following formulas, where n is the number of bits in either field:

2n(if your IP stack supports 1-bit subnet masks)

2n- 2 (if your IP stack doesn't support 1-bit subnet masks)

Multiplying the number of subnets by the number of nodes available per subnet gives you the total number of nodes available for your class and subnet mask. In the example shown in Figure 2, a 3-bit subnet mask is used to obtain a Subnet Address.

Figure 2: Using a 3-bit subnet mask to obtain a Subnet Address.

With this size mask, there are eight subnets available (assuming that subnets with all 0s and all 1s are allowed). Each subnet has 8190 nodes. In each subnet, nodes can be assigned any address between the Subnet address and the Broadcast address. This yields a total of 65,520 nodes for the entire class B address. Notice that this is less than the 65,534 nodes that an unsubnetted class B address would have. Subnetting always reduces the number of possible nodes for a given network.

Some Restrictions Apply. There are some restrictions that apply to subnet addresses. First, a subnet address cannot be all 0s or all 1s. Node addresses of all 0s are reserved to specify the local network (when a host does not know its network address). Node addresses of all 1s are reserved to specify all hosts on the network (broadcast address). This restriction also applies to subnets.

Another restriction is that a 1-bit subnet mask is not allowed. This restriction is a holdover from older standards that would not allow 1-bit masks. More recent standards (defined in RFC 1878) that allow 1-bit subnet masks have superceded these older standards. However, many "legacy" devices do not support the newer standards. If you are operating in a controlled environment, such as a lab, you can safely use these restricted 1-bit subnets.

Note: Novell's TCP/IP stack does allow for the 1-bit subnet mask.

Help with Subnetting. If you have trouble thinking in binary, you can download a free IP subnet calculator from http://www.net3group.com/ download.asp. This calculator comes with complete subnet tables available for Class A, Class B and Class C. It also provides tables that list all the possible subnet masks for each class, along with calculations of the number of networks, nodes and total hosts for each subnet.

How IP Routers Locate Nodes

Returning to our explanation of the IP routing process, IP first compares the destination IP address of the packet that it is processing with the entries in the routing table.

  • If IP finds that a host entry exists and matches the destination IP address, it will forward the packet to the next hop associated with that host entry.

  • Host entries are usually found in routing tables when ICMP (Internet Control Message Protocol) has added the entry because of the pathMTU algorithm, or from an "ICMP redirect" call. (To check this, load the TCPCON utility at the server console prompt and look at the IP Routing Table option to verify if the protocol associated with that route is ICMP.)

  • If IP doesn't find a host entry but does find a subnet entry that matches the packet's destination IP address, IP will forward the packet to the next hop associated with that subnet entry.

  • Subnet entries exist when RIP2 (Routing Internet Protocol v2), OSPF (Open Shortest Path First), or static entries have been added to the routing table through a non-default subnet mask.

  • If IP doesn't find a subnet entry in the TCP/IP routing table but does find a network entry that matches the destination IP address, IP will forward the packet to the next hop associated with that network entry.

  • Customers running in default NetWare TCP/IP mode will have network entries.

  • Finally, if IP doesn't find a network entry but does find that a default route entry exists, IP will forward the packet to the next hop associated with that default entry.

  • The default route is most commonly inserted as a static route through NetWare's INETCFG server console utility. However, the route may also be learned via RIP or OSPF. Failure to at least have a default route can often lead to communication problems on the network.

  • If an IP packet match has not been found in the TCP/IP routing table at this stage, the packet is simply dropped and an ICMP "destination unreachable" message is triggered to notify the sender that the host or network is unreachable.

When a TCP/IP communication problem occurs, the most common reason is that a route entry doesn't exist for the network or host with which you are trying to communicate. When this is the case, you can either add a route entry or try to figure out why the route is missing. The remainder of this AppNote provides some guidelines and methods for doing this.

TCP/IP Toubleshooting Methodology

When troubleshooting any networking problem, it is helpful to take a logical approach. Some questions to ask are:

  • What does work?

  • What doesn't work?

  • How are the things that do and don't work related?

  • Have the things that don't work ever worked on this computer/network?

  • If so, what has changed since the last time it did work?

Troubleshooting a problem "from the bottom up" is often a good way to quickly isolate what is wrong and come up with a solution. From an IP routing perspective, the bottom-up approach is as follows:

  • Start by verifying that the problem is not related to the physical layer (cabling, hubs, switches, and so on) or ARP (Address Resolution Protocol).

  • Ensure that the IP routing table is functioning correctly.

  • Check to see whether the problem is at a generic TCP/UDP or application level.

Example Network

To better understand the TCP/IP troubleshooting scenarios covered in this article, we'll use a small example network that illustrates some of the most common IP problems. This example network is shown in Figure 3.

Figure 3: Example network for TCP/IP trouble- shooting scenarios.

In this network, Workstation 1 accesses the Internet/WAN through a NetWare server which contains two network adapters, each with its own IP address: 137.65.43.1 and 137.40.3.1. Workstation 2 accesses the Internet/WAN through the Internet Router with the IP address of 137.40.3.4. The NetWare server also communicates to the Internet/WAN through the Internet Router, as well as the UNIX box (whose IP address is 137.40.3.3), which also communicates to the Internet/WAN through the Internet Router (137.40.3.4). The Internet Router's IP address is 137.30.1.254.

Terminology

It is important that you understand the terms "local host" and "remote host" as used in an IP network environment:

  • A local host is one that has the same IP network address/subnet mask as another host with which you are trying to communicate.

  • A remote host is one that has a different IP network address/subnet mask than another host with which you are trying to communicate.

From the point of view of Workstation 1 in Figure 1, the NetWare server is considered a local host because its network adapter is attached to the same IP subnet as Workstation 1. Workstation 2, whose IP subnet address is different than that of Workstation 1, can be considered a remote host.

TCP/IP Troubleshooting Scenarios

The following scenarios, which represent eight of the most common IP problems, use the example network in Figure 1 as a reference. The most common solutions are given for each of these problems. While this is not a comprehensive list of solutions, they cover most of the TCP/IP routing issues that customers face.

Scenario 1: Cannot PING or Communicate with Local Router

Symptom. The user cannot PING from Workstation 1 (137.65.43.2) to the local segment side of the NetWare server (137.65.43.1).

Solutions. If two nodes on the same subnet cannot successfully PING each other, first check the Address Resolution Protocol (ARP) table entries. To do this, enter the "ARP -A" command at a Windows workstation. (The "-A" parameter displays the ARP entries by interrogating the current protocol data.) If more than one network adapter uses the ARP, you'll see entries for each ARP table.

You can also use the TCPCON utility on the NetWare server to view the IP Address Translations Table. Select the Protocol Information | IP | IP Address Translation options, and see if the computers have the correct MAC addresses listed for each other.

Note: You can use the IPConfig utility (for Windows NT), the WINIPCFG utility (for Windows 95/98), or type "CONFIG "Enter"" at the NetWare server console to determine a host's MAC address (displayed as Node Address).

  1. If an ARP entry exists for the default router's IP address, perform the following troubleshooting steps.

    • Check for duplicate IP addresses. If another host with a duplicate IP address exists on the network, the ARP cache may contain the MAC (node) address for the other computer. If this is the case, change the IP address of one of the hosts so that it is not a duplicate on your subnet.

    • There may be a static (permanent) entry in the ARP cache that does not correspond to the MAC address of the host with which you are trying to communicate. If this is the case, delete that specific entry using the "ARP -D IP_address" command at a Windows workstation DOS prompt.

    You can also use the TCPCON utility on the NetWare server. Select the Protocol Information | IP | IP Address Translation options to view the IP Address Translations Table, highlight the appropriate Host Name/Mac Address entry, and press the <Delete< key.

    • The ARP table may be corrupted, in which case you must delete all entries by using the commands and/or utilities mentioned previously.

  2. If no ARP entry exists for the default router's IP address, this usually indicates that there is a hardware problem with the devices on the network. Perform the following troubleshooting steps.

    • First check the physical connection of either host, as the ARP request is a physical layer broadcast and should be responded to. Type "set tcp arp debug = on" at the server console to display all ARP packets being transmitted and received by the stack. You should be able to verify whether a response to the original ARP request was received.

    • Verify that the IP address of the default route that is shown in the TCPCON utility through the IP Routing Table entry is correct and on the same IP subnet. You do this by checking with the IS&T department. If the workstation is requesting the MAC/IP address mapping for a different (and possibly inactive) IP address, there will be no ARP responses from that inactive host.

Scenario 2: Cannot PING or Communicate with Remote Interface of Local Router

Symptom. The user can PING from Workstation 1 (137.65.43.2) to the local segment side of the NetWare server (137.65.43.1), but not from Workstation 1 to the other side of the NetWare server (137.40.3.1).

Solutions. In this scenario, Workstation 1 needs to know which IP router to send the IP packet to when the destination network is on a different subnet (to a remote host, according to our earlier definition).

Note: This procedure is not required if Workstation 1 wants to communicate with hosts only on its local subnet (local host). See TID #10018660 at http://support.novell.comfor information on configuring and troubleshooting communication issues on Windows 95/98 and NT clients.

  1. Each TCP/IP stack configuration (whether client or server) has a parameter for a default router or gateway. In this scenario, Workstation 1 would need to configure as its default router the IP address of the server's network adapter that is local to the workstation. The IP address would be 137.65.43.1. This implies that any packets that Workstation 1 will transmit to any remote hosts will be sent through this IP address.

  2. The NetWare server must be configured as an IP router so that it can forward packets from one network interface board (137.65.43.1) to the other (137.40.3.1). For this to happen, TCP/IP must have been loaded with the "forward=yes" parameter as part of the configuration.

    The best way to verify that TCP/IP has been loaded with forwarding enabled is through the TCPCON utility. Load TCPCON at the server console. You will see the "IP Forwarded: numbers" entry in the lower left-hand corner of the top window. If this entry has numbers after it (even if it is 0), this server is configured as an IP router. If this entry has DISABLED after the statistic, it is not set to gateway mode.

    To enable gateway mode, load the INETCFG utility at the server console, select the Protocols entry, the TCP/IP entry, and then ensure that the "IP Packet Forwarding" parameter is set to ENABLED. (See TID #10013002 at http://support.novell.comfor more details.)

  3. Check to see whether the "Local Errors" field in TCPCON | Statistics | IP entry increases as your PING requests fail. This field increments anytime IP drops an incoming packet for any reason. If this field is increasing, perform the following diagnostic steps:

    • Verify that the packet is not being blocked through a filtering mechanism, such as IPFLT.NLM. If this NLM is loaded, type "Unload IPFLT.NLM" at the server prompt, then check to see if the behavior remains the same.

    • Check the LAN/WAN Drivers statistics in the server MONITOR utility to see if the server is running out of ECBs (as will be indicated by the "Receive discarded, no available buffers" parameter). To do this, load MONITOR at the server console prompt, select the LAN/WAN drivers entry, the Ethernet_II entry from the Available LAN Drivers, then press the Tab key and scroll down to Receive Discarded, No Available Buffers entry.

    If this entry shows a non-zero value, increase the minimum packet receive buffers setting for the server. To do this in MONITOR, select the Server Parameters | Communications option, then select the Minimum Packet Receive Buffers entry and double it. Note that the changes won't take effect until you restart the server.

    • Go to the TCPCON | Statistics | ICMP entry and see if any of the fields other than "ICMP Echos Sent and Received" are incrementing as the PING command fails. (A PING request is an ICMP Echo Request, so you will see this entry increase through the PING command.) Depending on the ICMP message, this procedure may help pinpoint some network- related issues. For example, the ICMP Time Exceeded Messages entry may indicate routing loops, while the ICMP Source Quench Messages entry may mean there are problems with the system being overloaded.

Scenario 3: Cannot Ping or Communicate with Internet Router

Symptom. From Workstation 1 (137.65.43.2) the user can ping both IP addresses that are bound to the network adapters in the NetWare server (137.65.43.1 and 137.40.3.1), but cannot ping the Internet Router (137.40.3.4).

Solutions. By default, the NetWare server uses RIP as its routing protocol. However, most IP Routers use either OSPF (Open Shortest Path First) or IGRP (Interior Gateway Routing Protocol) as the routing protocol of choice. Since the routing protocols are different on both routers, they will not update each other's routing tables.

  1. If the routing tables are not being updated, the IP Router will not have a route back to the 137.65.0.0 segment, and will therefore not know how to respond to the PING from Workstation 1.

    To fix this problem, insert a static route entry at the IP Router. On a NetWare server, this can be done using INETCFG by selecting Protocols | TCPIP | Static Routes. This entry tells the IP Router that in order to get to the 137.65.0.0 subnet, packets must go through the 137.40.3.1 gateway, which is the IP address of the NetWare server for the segment local to the IP Router. This implies that any time the Internet Router has a packet destined for 137.65.0.0, it will send it to the 137.40.3.1 gateway.

    For exact information on how to set this up, see the document entitled "Configuring Static Routers for LANs" found at http://www.novell.com/documentation/lg/nias42/docui/index.html#../uscomm/rtcf_enu/data/ hipa3gzv.html.

  2. Another possible solution is to synchronize the routing protocols at the NetWare server or IP Router so that they both understand either RIP or OSPF. You do this by enabling the same routing protocol on all routers in the network. This will guarantee that the routes being advertised by both sides will dynamically enter the necessary routing tables.

    Note that an ASBR (Autonomous System Boundary Router) can also be set up on either router to act as a conversion gateway between OSPF and non-OSPF (static, ICMP, or RIP) routes.

  3. Check to see whether an ARP entry exists for the Internet Router (137.40.3.4) in the NetWare server. To do this, go to the TCPCON | Protocol Information | IP | IP Address Translations screen.

    • If no ARP entry exists for the Internet Router, check the physical connection between the NetWare server and the Internet Router. Most IP routers offer commands to dump the ARP cache table; for example, Cisco's IOS router provides a "show ip arp" command.

    • If an ARP entry does exist for the Internet Router in the NetWare server, make sure that the hardware (MAC) address shown corresponds to the Internet Router's MAC address. If it doesn't match, the ARP table may be corrupted. In this case, load the TCPCON utility on the NetWare server. Select the Protocol Information | IP | IP Address Translation options to view the IP Address Translations Table, highlight the appropriate Host Name / Mac Address entry, and press the <Delete< key.

  4. One other possible problem is that another device is responding to the ARPs using the Internet Router's IP address. In this case, there is either an IP address conflict or a bad switch.

Scenario 4: Cannot PING or Communicate with Remote Workstation

Symptom. From Workstation 1 (137.65.43.2), the user can PING both IP addresses that are bound to the network adapters in the NetWare server (137.65.43.1 and 137.40.3.1), and the Internet Router (137.40.3.4), but cannot PING Workstation 2 (137.40.3.2).

Solutions. As described in Scenario 2, the workstation must have its default router or gateway set in order to reply or send packets to segments other than its local segment gateway. (See TID #10018660 for information on configuring and troubleshooting communication issues on Windows 95/98 and NT clients.)

  1. First, verify whether a default route exists from Workstation 1 to Workstation 2, and whether the route points to the next correct hop router for that subnet. To do this, type the "NETSTAT -R" command from a Windows workstation DOS prompt. This command displays protocol statistics and current TCP/IP network connections, while the "-R" parameter displays the routing table.

  2. Configure the default gateway on Workstation 2. In this scenario, the default route should point to the IP address of the Internet Router (137.40.3.4), or to the server network adapter that is local to Workstation 2's segment (137.40.3.1) Then reboot the workstation (unless you used the "ROUTE ADD" command as mentioned in TID #10018660 to insert the static route at the workstation).

Scenario 5: Cannot PING or Communicate with Remote UNIX Host

Symptom. From Workstation 1 (137.65.43.2), the user can ping both IP addresses that are bound to the network adapters in the NetWare server (137.65.43.1 and 137.40.3.1) and the Internet Router (137.40.3.4), but cannot PING the UNIX box (137.40.3.3).

Solutions. Here are several possible solutions for this scenario.

  1. At the UNIX box, use the "NETSTAT -R" command to see if a default route (0.0.0.0) exists on that box. If no static route exists, you must enter one in order for the UNIX box to have a route to the 137.65.0.0 subnet. The syntax for adding a static route on the UNIX box in this scenario should be similar to the following:

    route add net 137.65.0.0 137.40.3.1 1

    For more information on the route command for UNIX, refer to the documentation that comes with your UNIX software.

  2. Synchronize the routing protocols at the NetWare server or at the UNIX box so they will both understand either RIP or OSPF protocols (as explained in Scenario 3). This will guarantee that the routes being advertised by each side will dynamically enter both routing tables.

    An ASBR (Autonomous System Boundary Router) can also be set up on either the NetWare router or the UNIX box to act as a conversion gateway between OSPF and non-OSPF (static, ICMP, or RIP) routes.

  3. Check to see whether an ARP entry exists for the UNIX box (137.40.3.3 ) in the NetWare server. To do this, go to the TCPCON | Protocol Information | IP | IP Address Translations screen.

    • If no ARP entry exists at the NetWare server for the UNIX box, check the physical connection between the NetWare server and the UNIX box. (This procedure is often independent of what NetWare does, so begin by looking at cabling, switches, and so on.)

    • If an ARP entry does exist at the NetWare server for the UNIX box, make sure that the hardware (MAC) address shown corresponds to the UNIX box's MAC address. If it doesn't match, the ARP table may be corrupt. In this case, use the TCPCON utility on the NetWare server. Select the Protocol Information | IP | IP Address Translation options to view the IP Address Translations Table, highlight the appropriate Host Name/MAC Address entry, and press the <Delete< key.

  4. One other possible problem is that another device is responding to the ARPs using the Unix box's IP address. In this case, there is either an IP address conflict or a bad switch.

Scenario 6: Cannot PING or Communicate with Remote Hosts Beyond the Internet Router

Symptom. From Workstation 1 (137.65.43.2), the user can ping both IP addresses that are bound to the network adapters in the NetWare server (137.65.43.1 and 137.40.3.1) and the Internet Router (137.40.3.4). The user can also ping Workstation 2 (137.40.3.2) and the UNIX box (137.40.3.3), but cannot PING past the Internet Router.

Solutions. In this scenario, the NetWare server knows about both the 137.65.0.0, and the 137.40.0.0 subnet segments, but it does not know where to route the packet if the destination is not on either of these segments. To fix this, try the following:

  1. Add a default route to the NetWare server. Load the INETCFG utility at the server console and go to the Protocols | TCP/IP | Static Routing entry (be sure it is Enabled), then go to the Static Routing Table entry. Press <Insert< to add Default Route with an IP address of Network/Host 0.0.0.0 and with the Next Hop Router on Route (Gateway) of 137.40.3.4 Metric 1 Passive. This information is then written to the SYS:ETC\GATEWAYS file. (See TID #2911404 entitled "Set LAN Default Route NW 4.x, 3.x, WEB, Proxy" for more details.) Then use the Reinitialize System command from INETCFG's initial "Internetworking Configuration" window to add the static route to the routing tables located in the server's memory.

  2. View the Internet Router's routing table (by running commands such as "show ip route summary" for Cisco IOS at the router's console prompt) to see if Workstation 1's network (137.65.0.0) has an entry. Because of dynamic routing protocols such as RIP and OSPF, this should normally be the case. Problems here may indicate that the Internet Router's routing table is not being updated correctly.

    If no route exists, insert a static route for the 137.65.0.0 network and investigate why the 137.65.0.0 network is not being advertised by the dynamic routing protocols. In troubleshooting this problem, you need to understand the network layout. Having the layout in mind will enable you to identify other routers in the network that should be advertising the route. You can use LAN traces to verify whether or not these other routers are advertising the missing network, and if so, with the proper parameters, such as hop count. In some cases, invalid hop counts may be advertised and the routes are being dropped accordingly.

  3. Verify that the packet is not being blocked through some filtering mechanism, such as the IPFLT.NLM. If this NLM is loaded, type "Unload IPFLT.NLM" at the server prompt, then check to see if the behavior is the same.

Scenario 7: Cannot PING or Communicate with Internet Hosts via a Cisco Router

Symptom. I have a Cisco router between me and my ISP. I am able to PING my Cisco Router but I can't ping my ISP or anything on the Internet. If I use the telnet command to communicate to the Cisco router, I can see that the default route is set correctly and that there is a route to my subnet. I also see an explicit route to the Cisco router from the ISP. I can also use the "Show IP Routes" command and it displays the IP address of my Cisco router and the networks with their next hop. From the Cisco router, I can ping my ISP and other hosts on the Internet. I have a subnet mask of 224.

Solution. When adding a route to the Cisco router, you need to specify the subnet mask for the network. If you add the subnet mask and perform a "Show IP Routes" command, the table shows the networks with their next hop and the subnet masks. This will allow you to PING any device on the subnetwork that has the correct subnet mask and a correctly-configured default route.

Scenario 8: Creating Variable-Length Subnets

Symptom. I have enough IP addresses for all the nodes that I want, but I only need a few nodes on the 137.65.43.1 side of the NetWare server. I really don't want to make two equal subnets when I need most of the available addresses on the 137.40.3.1 side, and only a few on the 137.65.43.1 side. Is there a way to make variable-length subnets?

Solution. Make a smaller subnet (or a "stub" of the network) that is bound to the server's network board using the 137.65.43.1 IP address. You can then force proxy ARP on the network board that is bound to 137.40.3.1 as its IP address to make it "listen" for the other board in the server.

To force proxy ARP from the command line (or from the AUTOEXEC.NCF file), include the proxyarp parameter in the BIND statement as shown below:

bind 137.40.3.1 proxyarp=yes

If you are using the INETCFG utility, select Bindings, the TCP/IP binding for the 137.40.3.1 board, then select Expert Bind Options and choose Force Proxy ARP. Change this setting to "Enabled." Press "Esc" until you reach INETCFG's initial screen, then select the "Reinitialize System" option for the change to take effect.

Next, bind the other NetWare board (referred to as 137.65.43.1 in the sample network) with an IP address and subnet mask that define a smaller range. An example would be an address of x.x.x.193 and mask of 255.255.255.248, which would give this board a "stub" subnet between 192 and 199.

You must also enable Proxy ARP on the 137.40.3.1 board (as described above), so that this board will listen for addresses on the "stub" subnet.

In your Proxy ARP configuration, make sure the stub subnet does not have the same subnet broadcast address as the other subnet. For example, suppose you bind your first server board to an IP address of x.x.x.90 with mask 255.255.255.192 and a broadcast address of 255.255.255.127. If you enable Proxy ARP on that board and then try to bind a second board to an IP address of x.x.x.97 with mask 255.255.255.224, the stub subnet will also have a broadcast address of 255.255.255.127. The result is that the second board won't bind, since the broadcast addresses are the same. In the same example, if you use a subnet mask of 255.255.255.240 (outside the first board's range), the broadcast address for the stub subnet will be 255.255.255.111. (See TID #2911147 at http://support.novell.comfor more subnetting details.)

Note: When binding the IP address to the second board (the one in the stub subnet), you will receive a message saying that the subnet mask that you have used disagrees with the mask on your other network card. This is an informational message to make sure that you know you are stub subnetting; it does not necessarily mean that IP routing is not working. The board in the stub subnet will bind and work properly.

Also note that when using variable-length subnets in the IP network, the routing protocols must be configured for RIP2 or OSPF to advertise the correct information. RIP (the default routing protocol) has no concept of subnet masks and therefore will never advertise them. Failure to configure RIP2 or OSPF may lead to connectivity problems.

Conclusion

This AppNote has presented information about resolving common TCP/IP communication-related issues in the NetWare 5 environment. Following these troubleshooting tips should help you keep your network running smoothly.

* Originally published in Novell AppNotes

Disclaimer

The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.

© Copyright Micro Focus or one of its affiliates