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 |
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 SMIT:
Using commands:
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.
trcstop
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.
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 |
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 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 |
|
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. |
|
Guest user cannot logon, Client reports Unknown user or password or similar error. |
|
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. |
|
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. |
If you need to contact technical support, the following information can help them diagnose your problem.
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.