If a network adapter is not fast enough to keep up with the data it is
LMC can experience delays and error messages when performing
large data transfers. If this happens with LMC, you see:
Terminating read ahead with server server_name.
To work around this problem, specify a smaller read/write buffer size in your LAN Manager client filesystem mount options. 1024 is a reasonable value for slower adapters. For more information about configuring this option, see Read/write buffer size (bytes) in the Networking Guide.
If you try to log on to an account that does not exist, it may log on as GUEST, or it may tell you you cannot log on.
If you try to mount off a machine that does not exist, you see the following error message:
mount: server not available /:Not available (error 138)
If you enter :
lc /mnt
and have not logged on to a remote filesystem, it tells you that:
lc: cannot access directory /mnt: Not privileged (error 1)
If you try to log on to an unknown machine, you will receive a message that it is not available. This can either mean that it does not exist, or that a known machine is not responding.
If you mount a non-existent filesystem on a known machine, you will not know this until you log on. You will receive a message similar to the following:
lc: /mnt2 not found: No such device or address (error 6)
If you enter vcview -v and examine the errors in the TxErr and RxErr columns, if either of these is increasing in value you should suspect a problem on the network. For example, cables not connected, LAN Manager server you are trying to access is no longer running.
You can also examine the values in the Reconns and Retrans columns. If these are increasing, this indicates either network or server overload.