If the crossover interface doesn't have a route to the WINS server (which seems rather likely), add the -wins option to your ifconfig line, and it will stop trying to register that interface with WINS. More detail is available in the SAG, conveniently located on line at now.netapp.com

You can fix this by running the following command (and putting it in your /etc/rc file for persistence):

ifconfig <interface> -wins

Where <interface> is the name of the network interface that you don't want to attempt WINS registrations on. It is probably wise to add this to the ifconfig line in /etc/rc that initially configures the interface - just tag it on the end like so:

ifconfig <interface> 10.254.2.2 netmask <netmask> <other options> -wins

Hope this helps!

-- Jeff

On Fri, May 18, 2001 at 05:58:52PM -0400, William W. Arnold wrote:

I received the following message [nbns_timer:error]: WINS Server [our wins server IP address] is not responding to registration of 10.254.2.2

then the following message every hour: [nbns_timer:error]: No WINS servers are responding; still trying

It started when I activated one of the previously unused interfaces on my Quad Fast Ethernet card. The interface in question is attached to a cross-over cable to a sun server, There are no WINS (Or any other microsoft protocol) servers on it.

As far as I can see, everything is working correctly. All other interfaces are properly registered with our WINS servers. Everything on the NT side of the network can access the Filer without any problems.

Is there any way to stop this message from repeating forever? It's rather irritating.

-- -billy- warnold@vipnet.org