[ Previous | Next | Table of Contents | Index | Library Home | Legal | Search ]

System Management Guide: Communications and Networks

AIX Fast Connect Problem Determination


The AIX Fast Connect server comes with the ability to create AIX trace files to isolate problems. When a trace facility is active, information about selected events is recorded in the trace file. To obtain trace files, you must have the trace command installed on your machine. The trace command is in the bos.sysmgt.trace package.

The following trace hooks are used by the AIX Fast Connect server:

2EE CIFS Enter

Trace files can be created by using either through SMIT or the command line.

Using SMIT:

  1. Type the smit trcstart fast path on the command line.
  2. Select the CIFS hooks for ADDITIONAL event IDs to trace field, then exit SMIT. This creates a trace file named trcfile in the /var/adm/ras directory (default).
  3. Recreate the problem.
  4. Then type smit trcstop on the command line.
  5. Exit SMIT.
  6. Type smit trcrpt on the command line and select the output format. It displays the trace file into readable format.

Using commands:

  1. Type the following on the command line:

    trace -a -j 2EE,2EF,2F0,2F1,2F2,2F3,2F4,2F5 -o /tmp/cifs.trace

    This creates a trace file named cifs.trace in the /tmp directory.

  2. Recreate the problem.
  3. Type:

  4. Type:

    trcrpt -t /etc/trcfmt /tmp/cifs.trace

    The trcrpt command formats the trace file into readable text and writes a report to standard output.


The AIX Fast Connect server writes information and error messages to a file in /var/cifs named cifsLog.

Troubleshooting Connection Problems

Cannot connect to server. Check that the server has passthrough_authentication_server enabled.

When you get one of these error messages on the client PC, try the following:
access is denied
password is invalid
password is not correct
not authorized to login
  • Enter the correct password.
  • Check logon user ID and its password on clients that should have an account on the AIX server. Log clients off and on with correct user ID and password.
  • For clients with Window NT with Service Pack 3 installed, the NET VIEW command returns access is denied. See Enabling Windows Clients for Plain Text Passwords for more information.

Note: AIX Fast Connect does not support mixed-case passwords when encrypt_passwords=0.

When you get this error message on the client PC, try the following:
System error 53 has occurred.
The network path was
 not found. 

System error 51 has
 occurred. The remote
 computer is not
When you get this error message on the client PC, check server status. It might be paused.
Connection Error when using a Passthrough Server
  • Be sure the passthrough_authentication_server parameter is set to the IP Address (rather than the hostname) by typing net config /parm:passthrough_authentication_server.
  • Test the network connection by pinging this machine. See Connection Checking Procedure.
  • Check that the networklogon or guestlogonsupport option is not being used. These options are mutually exclusive with passthrough authentication.

Cannot view Network Neighborhood from Entire Network on Windows clients Each Windows Workgroup must have a master browser present for network browsing to work properly. By default, any Windows NT, Windows 95, or Windows 98 client is set up to act as a master browser. The domainname parameter on the AIX Fast Connect Server determines which workgroup this AIX Fast Connect server is a member of. AIX Fast Connect does not function as a master browser.
Windows Primary Domain Controller reports that it cannot be started when AIX Fast Connect is running: If the networklogon parameter is set to 1, the AIX Fast Connect server acts as the Logon Server for Windows 95/98/NT clients. Set this parameter to 0 if you do not want this behavior.
Client reports
Account is not authorized to logon from this station
This error message occurs when AIX Fast Connect is configured for plaintext passwords but the client has not been configured to support plaintext passwords. See Enabling Windows Clients for Plain Text Passwords.
Server reports
Net:connect: A remote host refused an attempted connection
, Can't start server: Operation could not be performed, or similar message.
  • This usually means the server cannot be started. Ensure the server has not started by using ps -ef | grep /usr/sbin/cifs
  • Check for other services using the NetBIOS port (netstat -an | grep 139)
  • If services are found, then this problem was caused by the current installation of an application using the NetBIOS ports (AIX Connections, SAMBA, etc.). The intruding application must be removed so the port can be made available to AIX Fast Connect.
  • Additionally, check to be sure you have sufficient disk space available in the /var file system by using the df /var command, and that sufficient paging space is available and active using the lsps -a command.

Guest user cannot logon, Client reports Unknown user or password or similar error.
  • Ensure guestlogonsupport is set to 1.
  • Ensure guestname is set to a valid AIX user.
  • Ensure that guestname's AIX password is null.
  • Additionally, check that dce_auth and passthrough_authentication_server are not being used. These are mutually exclusive with the guest logon option.

Client reports The credentials supplied conflict with existing credentials or similar error. Client must logout and relogon with the user ID granting the desired access on the server. This usually happens when one client attempts to access the same server as two different users.
Client reports that it cannot create a file on the server.
  • In most cases this is an AIX permissions problem. Check the AIX share path to ensure desired permissions are set. (Also, if acl_inheritance is set to 1, examine the AIX ACLs using the acledit or similar command.
  • If permissions are not the problem, check that the file system where the share exists has enough space using the df [share path] command.
  • The administrator might want to log on to the AIX machine as the user who is having problems and attempt to create a file in the path that is causing problems. AIX might provide a more descriptive error message.

Printing from client results in garbled printout Some AIX back-end printer drivers add controls to the file that is being printed; others do not. Windows clients always send print jobs in a format that needs no controls. So, if your AIX printer driver adds controls, set the -o -dp printer share options when you create the printer share.

Technical Service Information

If you need to contact technical support, the following information can help them diagnose your problem.

  1. Your machine type
  2. Output from oslevel command - Operating System Level
  3. Output from netstat -an command - Network Information
  4. Output from lsps -a command - Paging Space Information
  5. Amount of memory on the machine.
  6. /etc/cifs/cifsConfig - Server Configuration File
  7. /var/cifs/cifsLog - Server Error Log
  8. Output from lslpp -l command - Software Installed
  9. Full output from errpt and errpt -a commands - System Errors
  10. Output from ps aux and ps -efl commands - Process Listing
  11. Output from trace.

Additionally, it might be helpful to have full core enabled, especially in the rare event that the AIX Fast Connect server crashes. To enable a full core, use the command chdev -l sys0 -a fullcore='true' and ensure you have plenty of space in your root (/) filesystem.

Connection Checking Procedure

  1. ping the AIX Fast Connect server by IP address. If timeout occurs, check:
  2. ping the AIX Fast Connect server with its NetBIOS name. If it fails, refer to NetBIOS Name Resolution for more information.
  3. Check server status on the AIX machine using net config, net status, and net statistics commands.

[ Previous | Next | Table of Contents | Index | Library Home | Legal | Search ]