[ Back | Print ]
Technical Information Document
What do I need to modify when I change IP address on NetWare 6? - TID10067853 (last modified 16AUG2004)
printer friendly tell a friend
Click here if this does not solve your problem
10067853 10067853 10067853

What do I need to modify when I change IP address on NetWare 6?


Novell NetWare 6.0


Customer changed IP address, however several applications no longer worked.


Here is a list of references that you will need to change when you modify the servers IP address(es).

Only products that ship with the Enterprise version of NetWare 6.0 are taken into consideration, please contact technical support for any other product concerned including products that ship with Small Business Server (SBS).

It should be understood that a CNE6 or equivalent level of knowledge is desirable for the implementation of these changes - this TID makes no effort to detail the steps required, it's just a list of references that may require changing.

Bindings and Subnet Mask

Default Route and possibly some other static network routes

Static NAT tables

DNS Resolvers



SYS:etc\resolv.cfg (if you didn't use INETCFG)


SYS:ETC\TRAPTARG.CFG (If applicable)


Bindings/Mask (if you didn't use INETCFG)

Default Route

Secondary IP address(s)


SYS:ETC\FTPREST.TXT (You probably won't need to change this)

Delete the ranges serviced by DHCP if they can no longer be serviced by the new IP address and no other server can service the range.  There is no edit option for DHCP in NetWare.


SYS:webapps\WebAdmin\servers.xml (If you Didn't use DNS)


SYS:apache\conf\adminserv.conf (There are up to 7 places that need changing - 'listen', 'securelisten' and 'redirect')

SYS:apache\nwdocs\nav.html - This is the default Apache "Welcome" page and could require changes in multiple places.

If running 2.0 Standard  edit the SYS:apache\iFolder\Server\httpd.conf (2 places - 'listen' and 'securelisten')

For both 2.0 Standard and Professional edit the SYS:apache\iFolder\Server\httpd_additions_nw.conf

If running 2.0 Standard the FIXUP.NLM needs to be run to change the IP Address of the installed iFolder Client - see TID 10068551  for details.

If running 2.0 Professional the iFolder Server Object needs the iFolderLDAPDNSorIP under the "Other" tab.

SYS:Apache\iFolder\DocumentRoot\html\iFolder_nav.html (If you didn't use DNS)

NetStorage - Verify that old and new IP address are listed, with "CDBE Edit on" at the server console at the following location: 
\my server\software\novell\xtier\configuration\xsrv\authentication domains\ 
       To remove the wrong IP address type: rd 192.xx.xx.xx   
Reboot the server or CDBE Flush


This procedure is detailed in TID 10067790


SYS:webapps\WebAccess\WEB-INF\PortalServlet.properties (If you didn't use DNS)



There are no configuration files assocaited with cluster serivces.  All configuration information is stored in NDS.  Therefore, the modifications will need to be made through ConsoleOne. 

Each node will require that the IP address field be changed via ConsoleOne under the properties page of the node object that resides inside the cluster container.
Once the node IP addresses are changed, each resource associated with an IP address change will need to be modufied.  This can be done in ConsoleOne by going to the properties page of the respective resource under the cluster container object.  

Once the node and resource IP addresses are changed, the Master IP address resource will need to be changed.  This is modified on the cluster container object under the Management tab.

 If there are hard-coded DNS references you must ensure that they still resolve to the correct address.

For the changes to take effect, the 'Cluster Down' command must be issued and type  'ULDNCS' on each node before starting the cluster with 'LDNCS'.

Note: if you are changing to a different subnet all cluster resources IP address will have to be changed to be within the new subnet.  If client mappings are done using the virtual server's IP address then the login scripts will have to be changed accordingly.

ConsoleOne: The ldap server object will have to be recreated and reassociated to the ldap group object.  A new SSL KMO object will have to be reassociated to the ldap server object.

As the names of the servers have changed you will need to recreate the following certificates:
        1. SSL CertificateIP (Regardless)
        2. SSL CertificateDNS (Only if the DNS Name changes)

One can use PKIDIAG.NLM to recreate the SSL Certificates.
Hit the readme, but here is a quick start:  C
opy pkidiag.nlm to sys:\system | load pkidiag | 4 to change the mode to fix | 0 to execute (follow your nose).

set dstace=*L

Execute a Repair Server Address from DSRepair.
In a small/mid sized environment dsrepair -rn is fine, however in large environments this takes a long time.
Do this after updating the \etc\hosts and \etc\hostname
1) Find the replica ring holders |  Advanced options menu | Replica and partition operations | note the partitions and go
into each replica ring. Note the server names of all ring members.
2) Now repair network address for each server in the ring. dsrepair | adv. option | Servers known to this database | Enter
on the server name | Repair selected server's network address | do this for each replica ring holder; for each Partition.

Then do the normal DS health check.  dsrepair | report sync and timesync. (see knowledge base for more details).

If you are running a SLP DA you can remove objects from the SLP Scope that reference services on the server to ensure this happens instantly.

Once this is done, execute a 'SET SLP RESET = ON' on the DA(s).

Server SET parameters (also accessible via MONITOR.NLM):

set SLP include, exclude addresses if you have changed them from default settings.

set NCP include, exclude addresses if you have changed them from default settings.

External References (not DS):
Change any DNS records pointing to services (for example the iPrint NDPS Manager DNS record) to point at the correct ip address.

IP-Based Restriction files on other servers (such as FTPREST.TXT for FTP on NetWare).

Static Routes on other servers or devices pointing to the old address.

SLP.CFG files on other servers that may have pointed to this server by IP address.

CLIENT: directory agent list

Other servers may point to this server for Timesync information, if that is the case you will need to change the SYS:SYSTEM\TIMESYNC.CFG information.

If you are running Novell Advanced Audit Service, see TID 10080358 for details.

ZEN for Desktops:

On the database object, confirm the IP address or DNS name of the database object in two places:

1.        ?Zenworks Database? tab | ?Server IP address or DNS name?

2.       ?Jdbc driver information? tab | Database Service name.

NOTE: If you don?t have the Database Service name under the JDBC driver information tab, it means that you don?t have the ZFD4 SNAPIN correctly installed and you?ll need to download the ?4.0.1 Snap-in for ConsoleOne? from download.novell.com

SCMD has a prefered IP address, this may need to be changed if it is hard-coded.


NOTE: This process is not needed for NetWare 6.5. NetWare 6.5 includes a new feature known as "IP Address Management" that allows you to schedule IP Address changes in the NRM (NetWare Remote Manager). This process will also update the necessary configuration files/setting for any product that IAM is enabled for. More information about IAM is available in the online documentation NetWare 6.5 IP Address Management Administration Guide.

Document Title: What do I need to modify when I change IP
Document ID: 10067853
Solution ID: NOVL70014
Creation Date: 24JAN2002
Modified Date: 16AUG2004
Novell Product Class: Groupware
Management Products
Web Services


The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.

Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.

[ Back | Print ]