Problems such as this are typically caused by problems with the name service configuration. If you are running 5.1 or later, then you can use the command "cifs testdc" to diagnose problems such as these.

Filer>cifs testdc [<wins addr> ] domain name [<optional name to test>]

This should give you a printout like this :

nttest> cifs testdc 10.10.10.55 nt-domain nttest Test will use WINS name resolution Testing WINS address...10.10.10.55 is alive Testing name registration... succeeded Current Mode of NBT is H Mode

Netbios scope "" <-------if you use netbios scope you need to set the scope using the options. Registered names... NTTEST < 0> WINS <-- the filer is registering with WINS. If you used broadcasts, then this would say broadcast. If you tried to register with WINS and this says broadcast -->Watch Out. WINS registration failed

Testing Primary Domain Controller found 1 addresses <- In your case I would expect this to fail trying 10.150.13.15...10.150.13.15 is alive <- can you route to the domain controller? found PDC FRENCH40 <- OK something is saying it is domain controller, is it really behaving like a domain controller.

Testing all Domain Controllers found 3 addresses trying 10.150.13.15...10.150.13.15 is alive trying 10.150.13.15...10.150.13.15 is alive trying 192.168.2.66...192.168.2.66 is alive found DC FRENCH40 at 10.150.13.15 Not able to communicate with DC 10.150.13.15 found DC NT-DOMAIN-BDC at 192.168.2.66

If your filer is multihomed, you are using WINS, and the registration test fails, then go to the WINS server and ping (or tracert) each interface on the filer. If the WINS server does not have a route to an interface then WINS registration will fail. The printout below does not indicate that this has happened, but others may find this useful.

Make sure the domain contains a freshly created machine account for the filer. You can create a machine account using Server manager.

Check to make sure that the domain controller is configured with the TCP network stack. We do not implement netbios.

Hope this helps.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > mailto: hawleyr@netapp.com mailto:hawleyr@netapp.com US Mail: Network Appliance Inc. > Phone: 408-367-3254 2770 San Tomas Expressway > FAX: 408-367-3451 Santa Clara, CA 95051

-----Original Message----- From: Alexander Strauss [mailto:strauss@ti.com] Sent: Wednesday, March 10, 1999 8:30 AM To: toasters@mathworks.com Subject: CIFS Setup Problems

Hello,

I tried to setup CIFS on my NetApp Fileserver using NT Domain authentication. The Filer has been added to the Domain by the NT server manager and can find the primary domain controller through the WINS service. Then I get the following error message:

filer> cifs setup [ ... ] Will this filer use an NT Domain for authentication? [yes]: Enter the NT Domain for the filer: EUROPE1

CIFS local server is registering... CIFS server is beginning domain installation. CIFS server is locating PDC. CIFS - Primary Domain Controller must be active for installation.

CIFS local server is shutting down...

But the primary domain controller *is* definitely active.

Any suggestions?

thank you,