Toasters-

Has anyone seen any difficulty in getting a F880c running 6.2.2 to bind to a NIS domain running on a Solaris 8 NIS master? We have an F880c that plays very nicely when bound to a NIS server running Solaris 2.6. We built a new NIS domain, with a new name, running on Solaris 8 but the F880c systems refuse to bind to the new domain when following the standard DataONTAP commands.

We're pretty confident that the new NIS domain config isn't the problem as we have 75 other Solaris systems of the flavor of 2.6, 7, and 8 bound to it with no problems.

Here is the relevant portion of the snoop output when snooping the interface on the NIS server. I see the call from the filer "filer2" to the NIS server "dvniss" but the NIS server refuses to answer it's bind request. This just repeats over and over every time the filer sends a bind request.

{root}on dvniss< snoop filer2 Using device /dev/dmfe (promiscuous mode) filer2 -> dvniss NIS C DOMAIN_NONACK pwcorp filer2 -> dvniss NIS C DOMAIN_NONACK pwcorp filer2 -> dvniss NIS C DOMAIN_NONACK pwcorp

Can anyone shed any light on what we may be missing? A search of now.netapp.com revealed no similar problems and Sun has validated our NIS configuration.

Thanks to all,

Brent Killion