Windows access problems

Kinds of access problems

This section describes preliminary troubleshooting steps, then describes how to troubleshoot the following problems:

Preliminary troubleshooting steps

Complete the steps in the following table to begin to troubleshoot Windows problems.


Step	Action
1	Make sure that the filer is licensed for CIFS by entering the `license` command at the filer prompt. If the following message appears CIFS not licensed or if a message with protocols other than CIFS appears but CIFS is absent, you must get a license for CIFS. Note: For information about how to get a license, contact Network Appliance Technical Support, as described in "Getting technical assistance."
2	If you are authenticating through a Windows NT domain, make sure that the filer has an account in the domain. Note: You can verify that the filer is registered with a domain controller by using the `cifs testdc` command.
3	Make sure that CIFS service has been properly configured with the `cifs setup` command.

Filer can't register with the Windows NT domain

If you are using WINS, use the table in "Using Wins" to troubleshoot the problem; if you are not using WINS, use the table in "Not Using WINS."

Using WINS

Use the following table if you are using WINS.


Is the WINS server working?
Yes	No
Is the domain controller running?	Get the WINS server working.
Yes		No
Can you ping the domain controller?		Start the domain controller.
Yes			No
Can you ping the filer?			Check network connectivity
Yes				No
Contact Network Appliance Technical Support, as described in "Getting technical assistance."				Check network connectivity

Not Using WINS

Use the following table if you are not using WINS.


Is the PDC or BDC on the same subnet as the filer, and is the subnet connected to the first configured network interface card on the filer?
Yes		No
Is there a computer account created for the filer in the Windows NT domain?		Put the domain controller on the same subnet as the filer, and connect the subnet to the first configured network interface card on the filer. Without a WINS server, the filer can talk only to the domain controller by broadcast. The filer broadcasts only from the first configured network interface. The domain controller must be on this subnet.
Yes	No
Contact Network Appliance Technical Support, as described in "Getting technical assistance."	Create a computer account for the filer in the domain.

Incorrect password or unknown username

Use the following table to troubleshoot the problem.


Are users in the same domain as the filer?
Yes		No
Are you using a virtual LAN?		Is there a trust relationship between the filer and the domain?
Yes	No	Yes	No
Have the users log in with DOMAINNAME\ USERNAME	Enter the users into the /etc/passwd file.	Have the users log in with DOMAINNAME\ USERNAME	Establish a trust relationship between the user's account domain and the filer's domain.

Users can't map a drive

If users get an Access Denied message, use the following decision table to troubleshoot the problem.

Is the filer in the same domain as the PDC?
Yes No
Does the user have access rights to the share? Use Server Manager to add the filer to the domain or establish a trust relationship between the domains.
Yes No

Contact Network Appliance Technical Support, as described in "Getting technical assistance."

Give the user rights to the share.

Is the filer in the same domain as the PDC?
Yes	No
Does the user have access rights to the share?	Use Server Manager to add the filer to the domain or establish a trust relationship between the domains.
Yes	No
Contact Network Appliance Technical Support, as described in "Getting technical assistance."	Give the user rights to the share.

Part No. 210-02334
File: trbl19.htm
Last updated: 02/24/99 12:17:24