How to rename a NetWare 6.x server.
(Last modified: 24Jan2006)
This document (10080951) is provided subject to the disclaimer at the end of this document.
How to rename a NetWare 6.x server.
Novell NetWare 6.0
This guideline will help in renaming a NetWare 6.x server.
FOR INFORMATION ON RENAMING A NETWARE 4.x SERVER, SEE Solution Document #10021278.
FOR INFORMATION ON RENAMING A NETWARE 5.x SERVER, SEE Solution Document #10052290
The following are the steps to change a NetWare 6.x server's name or internal IPX and/or IP address:
NOTE: DO NOT CHANGE THE INTERNAL IPX AND/OR IP ADDRESS AT THE SAME TIME THE SERVER NAME IS CHANGED. ALSO, DO NOT CHANGE MORE THAN ONE SERVER'S NAME IN THE TREE AT A TIME.
CAUTION: This information given is intended to show how to change the server name or internal IPX and/or IP address of a server, but NOT to replace an old server with a new server by the same name. If you are trying to replace, or upgrade hardware, please use Solution Document 10010933, Novell DSMaint Procedure.
DO NOT CHANGE BOTH the internal IPX and/or IP address and the server name at the same time! Make only one change at a time and give it plenty of time to replicate out to the entire system. If you want to change both, execute the following procedure after each change.
BEFORE BEGINNING: Verify first that all servers in the NDS tree are up and communicating. Check the DSTRACE screen of the server holding the master replica of root, verify that all replicas are processing correctly. load DSREPAIR | time synchronization. This will check all servers in the tree for current time status and DS revision. In effect, it lets you know they are up and running and synchronized time wise. If there are errors, especially communication errors (-625, etc), stop and fix them before continuing.
Check NWAdmin or NETADMIN to verify that another object does not already exist with the new name of this server. This includes groups, users, print servers, etc.
1 - Load the NWCONFIG.NLM and edit the AUTOEXEC.NCF file to reflect the new file server name OR internal IPX and/or IP number and then save the changes.
2 - Down the file server in question and bring it back up.
3 - Once the file server comes up, it will kick off the Limber process. You can also force the Limber process to start by typing the following commands at the console: SET DSTRACE = ON, SET DSTRACE = +LIMBER, SET DSTRACE = *L, and SET DSTRACE = *H. You can then toggle or ALT ESCAPE over to the Directory Services screen and see the Limber process take off.
The Limber Process defined: Each server in the Directory tree goes out and checks its tree name and modifies it if necessary. The Limber process initiates when a server in the tree comes up, by forcing it as in the above paragraph, when Directory Services restarts by unloading the DS.NLM and reloading it (i.e. SET DSTRACE = *.), or when a server receives a CheckTreeName request from another server in the tree or for any other reason needs to establish communications with another server in the tree.
4. If the server name was changed, then the login script variables specifying the old server name need to be changed.
5. In ConsoleOne go into Device Manger, or the Media tab on for the server. Select NSS POOLS and click the Update NDS tab. Select the NSS Volumes and click the Update NDS tab. Run a DSREPAIR "Check volume objects and trustees" to verify this process is complete. If the Media Tab cannot be seen, check the General Tab, in Console One on the properties of the server, and ensure that the "Other Name" field is blank. This will allow the media tab to be seen.
6. Delete the NLS_LSP_Server object. Run SETUPNLS on the server console to recreate. Check the licenses and ensure they are assigned to the proper server.
7. Any DHCP object(s) will also need to be deleted and re-created/re-installed.
8. Delete the SAS, SSL CertificateIP , and SSL CertificateDNS associated with this server. Run PKIDIAG.NLM (Select options 4, 5, 6, then 0 to Repair) and this will recreate the SSL objects. If this server was the Certificate Authority, delete the Organizational CA, highlight the Security Container and do new object Organizational CA, select Standard, give it a name, and associate the proper server to this object. (This must be done prior to running PKIDIAG) For NetWare 6.5, you must also run tckeygen from the server console for Tomcat to load properly.
9. Any other object(s) (DNS, LDAP, SMS ojects etc.), that have dependencies on the server name will need to be deleted and re-created/re-installed. Each service has it's own unique dependency on the server name. This could include other Novell products and/or other 3rd Party products (Arcserv, etc.).
NOTE: For the reasons listed in Step 9, an optional method for changing the name of a NetWare 5.x server would be to remove the server from the tree - see Solution Document 10010922, Removing a Crashed Server from the NDS Tree, clean up any resultant UNKNOWN objects (these server-dependent objects would appear with a question mark icon in NWADMN32.EXE) and reinstall these products (including the licensing objects) as needed after the server name has been changed (Steps 1-4 above) and after the server has been placed back into the tree by reinstalling Directory Services (NWCONFIG | Directory Options).
The following are files that need to be changed to reflect the new server name. Paths may vary from 6.0 to 6.5 (for example, SYS:Apache will be SYS:Apache2)
Protocols | TCP/IP | DNS Resolver Configuration
OPERATING SYSTEM FILES:
SYS:etc\resolv.cfg (if you didn't use INETCFG)
SYS:NI\UPDATE\DATA\PortResolverInstalled.properties (If applicable)
SYS:ETC\TRAPTARG.CFG (If applicable)
SYS:SYSTEM\TIMESYNC.CFG (If applicable)
SYS:ETC\FTPREST.TXT (If applicable)
To re-generate the ifolderclient.exe, See Novell TID 10068551
NETSCAPE ENTERPRISE SERVER (NW 6.0):
You will need to reconfigure web access objects through ConsoleOne.
External References (not DS):
IP-Based Restriction files on other servers (such as FTPREST.TXT for FTP on NetWare).
OTHERS THAT MAY NEED TO BE CHECKED (NW 6.0):
Novell NetWare 6.5
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.
- Document ID:
- Solution ID: NOVL87689
- Creation Date: 10Mar2003
- Modified Date: 24Jan2006
- NovellConnectivity Products
- NovellConnectivity Products
Did this document solve your problem? Provide Feedback