Network path not found

The client did not receive a response from a server when it broadcast a request for a NetBIOS name, for one of the following reasons:

• The user supplied an invalid service name when attempting to connect to a TAS host. Follow these links or use the tnstat command to make sure the service status contains the correct service name: LM-NT-OS/2 Realm->Configuration and Control-> LM-NT-OS/2 Realm Status.

• When a client attempted to connect to a TAS host, the named service did not run. Follow the links LM-NT-OS/2 Realm->Configuration and Control->LM-NT-OS/2 Realm Status or use the tnstat command to see if the service status runs. If it does not run, restart LM-NT-OS/2 services by following "5.1.2 Shutting Down LM-NT-OS/2 Services", then "5.1.1 Starting LM-NT-OS/2 Services".

• The user misspelled the server name. Use tnservice -l or check the service configuration at LM-NT-OS/2 Realm->Manage File Services->[select the service]->Administer->Configuration to verify the spelling.

• The system has reached its NetBIOS session limit. Check the initialization file of the client protocol software to verify that the system allows sufficient NetBIOS sessions.

• The server cannot run NetBIOS.

• The NBname daemon does not run. NBname exits if it detects another network node with the same NetBIOS name. TAS then ignores name requests. Check the NetBIOS error log $TNHOME/NB/log on the host for an error message. Change the NetBIOS name, if necessary, and restart TAS as described in "4.1.2 Shutting Down TAS Services", then "4.1.1 Starting TAS Services", or with the tnshut and tnstart commands.

• The server and client reside on different networks--they reside on different sides of a router or a bridge--and NetBIOS broadcasts do not propagate. Use the TAS Enterprise Name Server (ENS) as described in "6.1 Modifying TCP/IP Configuration" or by using the tntransport command. Alternatively, you could configure routers to propagate broadcasts using a p-node NetBIOS setup, but this substantially increases network traffic and lowers network capacity.

• IP addresses have incorrect formats or content. Check the IP addresses with the tniface command or by following these links: Transports ->TCP/IP Addresses. On the server, you can find an IP address using the ifconfig command. The address should have four segments separated by periods, as in the following example, where A, B, C, and D represent sets of decimal numbers:

• A.B.C.D

  Determine the address with this table:

  If A is:	the network number is:
  < 128	A
  128 - 191	A.B
  > 191	A.B.C

• The network mask for the client does not match that for the server. This table gives the default network masks for IP addresses:

  If A is:	the network mask is:
  < 128	255.0.0.0
  128 - 191	255.255.0.0
  > 191	255.255.255.0

• The broadcast addresses cannot work together. The original TCP/IP did not define a way to broadcast packets on the Internet. When this became desirable, enterprising corporations developed several different mechanisms, not all of which interoperate. To try a different broadcast style on the PC, see the client TCP/IP documentation.