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

AIX Fast Connect
Version 3.1 Guide

Problem Determination

This chapter contains information on solving AIX Fast Connect problems. The following topics are dicussed in this chapter:

Traces

To isolate problems, the AIX Fast Connect server can create AIX trace files. 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
2EF CIFS Exit
2F0 CIFS-FSS
2F1 CIFS-LOGON
2F2 CIFS-NET
2F3 CIFS-SMB PARSER
2F4 CIFS-PSS
2F5 CIFS-SMS

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

Using the SMIT interface, complete the following:

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

Using the command line, complete the following:

  1. On the command line, type the following: 

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

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

  2. Re-create the problem.
  3. Type: 

    trcstop
  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.

Logs

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

Connection Problems

Following are some problems

Table 5. Actions to be taken when errors occur or when error messages are given.
Error or error message Action to be taken
Cannot connect to server. Check that the server has passthrough_authentication_server enabled. 
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.

 
System error 53 has occurred.
The network path was
 not found. 
System error 51 has
 occurred. The remote
 computer is not
 available.
 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 host name) 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.
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 or Windows 98 or Windows 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		 Occurs when AIX Fast Connect is configured for plain-text passwords but the client has not been configured to support plain-text 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.
  • Usually means the server cannot be started. Ensure the server has not started by running the ps -ef | grep /usr/sbin/cifs command.
  • Check for other services using the NetBIOS port (netstat -an | grep 139)
  • If services are found, this problem was caused by the current installation of an application using the NetBIOS ports (such as AIX Connections, SAMBA). 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 by 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 the dce_auth and the passthrough_authentication_server options 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 log out and log on again 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 permissions are set correctly. (Also, if acl_inheritance is enabled, examine the AIX ACLs using the acledit command or a similar command.
  • If permissions are not the problem, check that the file system where the share exists has enough space by 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.
Printing from client results in garbled printout Some AIX back-end printer drivers add controls to the file that is being printed. Windows clients always send print jobs in a format that needs no controls. 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 support personnel diagnose your problem.

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

Connection Checking Procedure

Follow these steps to complete the connection checking procedure:

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

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