🚀 go-pugleaf

In article <rhoads-0807961148270001@mac102325.med.cornell.edu>, 
rhoads@mail.med.cornell.edu says...
>
>Another support department in my institution has over 30 Netware 3.12
>servers.  Every day I get several of the messages below on my Netware 4.1
>server consoles.

Here's what fixed it for me.....
------------------------------------------------------------
From:          "Steve McKelvey"
Organization:  SCUP
To:            Netware Administrators
Date:          Fri, 31 May 1996 14:05:20 EST
Subject:       "Server xxx address changed... messages"
Reply-to:      
Priority:      normal

In case anyone is getting the infamous "Server <xxx> address has 
changed..." messages, and wants to stop them on a 4.1 server, here's how.

   LOAD INETCFG
      (select to transfer load and bind from your autoexec.ncf if you
      haven't used inetcfg to manage your lan channels before)
   Select PROTOCOLS from the menu
   Select IPX from the menu
   Select ADVANCED IPX and set it to ENABLED
   escape out of inetcfg to the console prompt
   REINITIALIZE SYSTEM or wait for the server to be restarted
      and the messages should stop

The cause of the problem (for those who are interested):
A device that is advertising a network service (print service or whatever)
is advertising the service with the same name and service type (sap 
number), but doing it through two different lan interfaces so that it has 
two addresses for that name/sap type, or doing it through two different 
sockets on the same machine.  In either case, it appears to the rest of 
the network as if two separate things are advertising the same service and 
the same name, something that would not be good.  It would be the same 
thing as having two separate servers appear on the network offering file 
services with the same server name.  So NetWare reports it to you as a 
problem.  The "right" answer is to find the device or devices that are 
misconfigured or have the same name as another device, but that isn't 
always easy in our environment.  If you load the IPXRTR.NLM (which 
gets loaded when you set the advanced IPX options on), the messages aren't 
displayed.