Changing Server IP Address (NetWare 6.5) 2

[MichiganRon]

The CNE where I work built a new NetWare 6.5 SP3 server for me to migrate our GroupWise system to. The GroupWise system is currently running on NW 5.1 SP7. I plan on moving the system to the new server this weekend, but I was just told that after the migration, I need to down the old server and change the IP address & domain name of the new server to match the old server's IP address & domain name.

I can handle the GroupWise migration. But, I don't know which files need to be modified to change the server IP address & domain name. I found thread871-955145, which points to

http://support.novell.com/cgi-bin/search/searchtid.cgi?/10067853.htm,

which describes how to change the IP address on a 6.0 server.

How much different is it to change the IP address & domain name on a 6.5 server? Can anyone point me to the right direction?

Thanks,
Ron

P.S. Naturally, my CNE is on vacation and won't be back until next week.

“If you are irritated by every rub, how will you be polished?” ~ Mevlana Rumi


Do you live in Michigan? Join us in the Tek-Tips in Michigan forum.

 

[BudTheGrey]

In NetWare 6.5, they made changing the IP address much easier.

browse to

https://<serveraddress>:8009,

and login as admin

On the right-hand side, near the bottom of the list under the heading "server management", you'll see "IP address mangement"

The how-to is more fully explained here (long url might wrap):

http://www.novell.com/documentation/nw65/pdfdoc/ipaddmgmt/ipaddmgmt.pdf

Hope this helps

 

[marvhuffaker]

Ron, NetWare 6.5 handles IP address changes much easier than NetWare 6.0 did. However, it doesn't handle the Name change as well. You still might need to modify several files after the name change -- mainly for various web based services.

The main thing for the name change is getting the actual NCP server name changed.. That is done in the Autoexec.NCF file. Just change it there and reboot the server. (Also you will want to modify the ETC\HOSTS file, but that is more for the other services).. So make those changes, then reboot the server. Once the servers come back up, make sure that the name change propgates throughout the NDS tree.

For the IP address change, if Once the server is back up, go into the Portal at http:\\xxx.xxx.xxx.xxx:8008. There are two places you'll need to go:

1) Configure TCP/IP -- go in there to your bindings and make the change. It should also remint your certificates automatically.. (as opposed to INETCFG, which won't).. Once you've done this, you'll probably want to reboot the server.. OR it may lose connection and you'll have to anyway.

2) After reboot, Go into IP Address Management - You'll see a list of stuff, and most of it will be RED.. Anything red means the address is invalid.. You just need to change it to the valid address.

After you're done with all this, you may want to run PKIDIAG just to make sure your certs are clean..

Then you'll need to go into ConsoleOne and modify any addresses and UNC paths for the various GroupWise components.. I am pretty sure you already know how to do that part..

Back to the Name Change.. you should be fine, but if you find anything that shows the name incorrectly, you'll need to track down which config file controls that and modify it. It's probably in the list of files that you referenced in that one TID.


Marvin

Marvin Huffaker, MCNE

http://www.redjuju.com

 

[MichiganRon]

I did the migration over the weekend. Although the suggestions and links were helpful, there was a bit more to it than described above.

I tried just downing the old server (GW2) and changing the IP address of the new server (GW3) to the IP address that GW2 was previously assigned. Unfortunately, NDS was confused. So, I ended up downing the new server, removing the old server from NDS, then bringing up the new server and changing the IP address (as described by Marvin). There were several references to the old server in ConsoleOne which I had to change to the new server.

I had been at work for about 23 hours at this point, so I burned an incident with Novell to figure all this out. I think the tech who was paged for my incident called me from home because I heard his cat in the background. Good to make me smile after a way-to-long day at work.

Once all references were changed, everthing worked like a charm.

My CNE came in this morning and mopped up the rest, like backup jobs.

Thanks for your help.

Ron

“If you are irritated by every rub, how will you be polished?” ~ Mevlana Rumi


Do you live in Michigan? Join us in the Tek-Tips in Michigan forum.

 

[marvhuffaker]

Yeah, you gotta make sure the old server is done and gone first.. That will get you every time.. If you just downed it, that's not good enough. Glad you got through it.

Marvin Huffaker, MCNE

http://www.redjuju.com