The rule on WINS is that the WINS server must be able to ping every address on the filer. We added the -wins option on ifconfig since WINS will not work properly if the filer has a private net. The option says to exclude this interface from WINS registration.

If you rc_toggle_basic you can use the nbtstat command to show the current registration status. If the entries say broadcast instead of WINS, then we were not able to complete registration with the WINS server.

As Andrew said, NetApp customer support would be happy to help you solve this problem.

-----Original Message----- From: Bond, Andrew [mailto:abond@netapp.com] Sent: Tuesday, April 04, 2000 2:12 AM To: johan.gillquist@cn.saab.se Cc: toasters@mathworks.com Subject: RE: Problem with WINS registration on 5.3.4R3

Maybe the WINS server is not accessible to the filer (in which case there should be errors in the messages file).

Some versions of ONTAP allow you to run "cifs testdc" and this will report whether the name was registered by WINS or by broadcast because the WINS server was not available (I think this shows as "WINS" or "WINS broadcast" respectively).

It is also possible to disable wins registration for specific IP address using the -wins flag to ifconfig.

Have you opened a call with NetApp support? There are other tools to debug this....

Regards, Andrew

-----Original Message----- From: owner-dl-toasters@netapp.com [mailto:owner-dl-toasters@netapp.com]On Behalf Of Johan Gillquist Sent: 04 April 2000 07:16 To: netapp mailing list Subject: Problem with WINS registration on 5.3.4R3

Hi all,

I have have a problem with my F720 running 5.3.4R3, CIFS and NFS. The toaster does not seem to register itself in WINS. When I run a "cifs sessions" command it states "WINS servers: xxx.xxx.x....." and it's the correct address. When a check the WINS server there is no entry's for the filer. If I enter a static entry in the WINs database it works fine

Suggestions ?

/Johan