Error Messages and Solutions

This section provides solutions to error conditions accompanied by error messages. The table below details the exit codes that appear as tn-utilities error messages. The rest of this section lists causes and solutions for other common error messages.

0	Success
1	Usage
2	Incompatibility
3	Invalid command line
4	General memory allocation
5	Disabled system
6	Invalid realm, system, or service
7	Application Interface error
8	System call failure
9	C library failure
10	Invalid characters in volume, for specified realm
11	Invalid characters in service, for specified realm
12	Service name too long for specified realm
13	Denied permission; superuser access only

Access denied

The user does not have privileges to either read a file, write a file, execute a program, or search a directory.

Cannot access a directory

The NetWare client cannot access a UNIX directory. Verify that the directory has the execute permission bit set and resides below the virtual root of the volume.

Cannot access network drive

The Windows interface on the network has one of these problems:

• The correct driver has not loaded. Under the Windows Setup program on the client, check the Network option and verify that the correct network driver has loaded. For example, for a Microsoft client, the words Microsoft Network should appear. If they do not, click Change System Settings on the Options menu, then select the correct driver from the list under Network.

• The drive connected using the Windows file manager and the existing file manager saved the settings. The user chose, under Windows Control Panel->Networks, to restore all connections at startup, and consequently used the drive letter for DOS to make a different redirection.

Cannot create socket on server

The system socket call failed on TAS startup for one of the following reasons:

• You did not shut down NetBIOS. If the UNIX operating system contains NetBIOS, shut it down before starting TAS.

• The system has used all of its sockets.

• Another process has claimed one of the reserved NetBIOS ports.

Cannot log in to server as supervisor

The server uses the UNIX operating system to authenticate users, so the user account must exist on the UNIX host before you can log in. A Novell server's system administrator defaults to supervisor; the UNIX equivalent defaults to root. Typically, you must log in as root to administer the UNIX operating system.

Incorrect password

The server has not validated the user's name or password. Make sure the name and password fulfill the following requirements:

• Correct spelling.

• Correct format for upper-case characters. A tilde (~) must precede each one.

• Satisfaction of the following system limitations:

  • NetBIOS has a 14-character maximum.

  • NetWare has a 30-character maximum with TAS.

  • AppleTalk has an 8-character maximum.

  • Users with account names or passwords longer than eight characters may have difficulty making connections. On many UNIX systems, only the first eight characters of the password matter, so you may establish a connection by providing only the first eight characters of the password.

  • On systems with password aging supported and enabled, the password may have lost validity. Have the user log in to the UNIX host at the console or with a terminal emulator such as telnet and update the password.

  • The user name lists as restricted.

Incorrect response from network

The name discovery phase succeeded, but the system rejected the connection request, for one of the following reasons:

• The user made a connection attempt to a TAS host immediately after the user's previous connection terminated ungracefully, such as by client PC reboot, and the connection definition file still exists. Run tnck.

• A user attempted to connect to a service with an invalid command in its service definition file.

• You caused TAS to reject new connection attempts. To accept services, use the "tnaccept" command.

• TAS has reached its user limit. Multiple connections from a single client to the same service name count as a single user, but each connection to a new service name, even if it comes from the same client, counts as a separate user. Contact your Syntax representative at (253) 838-2626 to order user licenses.

• The time limit on your evaluation copy of TAS has expired.

Invalid connections in "tninfo" report

The output of tninfo shows a connection that does not exist. The tninfo report normally shows only one connection per Ethernet address. Occasionally, a duplicate may list when the server has not yet recognized a connection termination. An ungraceful disconnection by the client, as when the client turns off the PC or reboots without logging out, usually causes this.

To detect dead connections, enable the keepalive function for the LM-NT-OS/2 and NetWare realms. This tells the server to send keepalive packets, similar to Novell watchdog packets, to determine whether clients remain attached. After sending the first keepalive packet, the server sends another packet every minute for 10 minutes. If it receives no response during this time, the server assumes that the connection died and updates the connection database accordingly. The client no longer lists in the tninfo report.

To enable keepalives, use the following command, where n represents the number of minutes for the server to wait after a connection establishes before sending the first keepalive packet:

tnservice -M -r NW -s nwhera:file -a keepalive=n:

Invalid drive was specified

A problem exists with the drive letter in a client command. This can occur when a client attempts to redirect a local drive, such as a diskette drive or a hard drive partition.

Network device type incorrect

The user has attempted to redirect either a drive to a print device or a printer port to a directory.

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. Use the "tnstat" command to make sure the service status contains the correct service name.

• When a client attempted to connect to a TAS host, the named service did not run. Use the "tnstat" command to see if the service status runs. If it does not run, restart LM-NT-OS/2 services.

• The user misspelled the server name. Use tnservice -l 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 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) 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. 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.

No servers listed by "slist"

In a PC's net.cfg file, you can list several frame types to use over the network card. The network uses only the first entry when transmitting packets. If a server host does not have the configuration to use the same type of frame as the client, the client cannot see that server; the server does not list from the slist utility or on the Windows NetWare interface.

Remote computer not listening

This problem may occur with an inactive NBdaemon process. Use the "tnstat" command to verify that you started TAS. If you have not, use the "tnstart" command.

Routing information database corrupted on large internetwork

NetWare servers broadcast routing information every 60 seconds using the Routing Information Protocol (RIP), and they broadcast service information every thirty seconds using the Service Advertising Protocol (SAP). On a very large internetwork or wide-area network, the RIP or SAP database can grow so large that the time necessary to download it exceeds the interval between downloads, especially if you have a low-speed WAN link. This can cause the apparent disappearance of volumes, printers, or servers or extreme delays in packet re-routing, if a node fails.

Novell will replace RIP and SAP with NetWare Link State Protocol (NLSP). NLSP associates multiple network interfaces with a single network number, distributing traffic across multiple network segments. If a node fails, NLSP can quickly establish an alternate path. NLSP builds a map of the network incrementally and sends updates only as needed. NetWare 3.11, 3.12, 4.11, and 4.12 servers support NLSP. They can still work with existing SAP/RIP servers.

Server not found

The name-discovery phase succeeded, but the system cannot find the requested resource on the server, for one of the following reasons:

• A user attempted a connection to a TAS host with an invalid UNIX name. Verify the validity of the user name. Check the spelling and case. Make sure a tilde (~) precedes each upper-case character.

• You set the NetBIOS naming scope incorrectly. Check the naming scope with the "tntransport" command. If you do not set the NetBIOS Name scope attribute, TAS ignores the client's naming scope.

• When a user attempted a connection to a TAS host, an attach point defined in TAS's configuration of .profile.file in the user's home directory matched a UNIX user name or directory. Change the name of the attach point with the "tnattach" command and retry the connection.

• The user attempted connection to a directory with a user limit, and the directory has reached its limit. Try again later.

• A user attempted to establish a print service connection to a nonexistent printer. Verify that either the server configuration contains a reference to the printer, with the "tnservice" command, or the user's .profile.file contains a prdefault or printer command for the requested printer.

• An attempted extended connection contains a path to a nonexistent directory. Verify that the directory exists and try again. Stop and restart TAS if you modify the directory configuration with the "tnshut" and "tnstart" commands.

Too many redirections

The user has attempted to exceed the number of connections allowed by the client computer's network operating system, NetBIOS, or TCP/IP. Update nb_sessions, tcp_sockets, or udp_sockets entries in the net.cfg file to allow more redirections. If you do not want to allow more redirections, cancel a redirection, then try again.

Unknown board ID

The age of the network card driver exceeds the age of the physical network board. Replace the board interface software with a newer version.