252 subnet on Netware 5.0 server

I have 3 netware 5.0 servers. 2 production and the other runs the backup. A contractor wanted us to go to private 192 addresses with a subnet of 255.255.252.0 to support more than the 250 nodes. The problem was that by default the tcpip.nlm didn't support this. So on the back up server I installed the tcpip enhancement from Novell to test. All was well to I went to change the ip add in inetcfg. When I went to reinitialize the system I got a netware critical error and locked the server down and had to reboot. The problem is that I had already installed the enhancement to the two production servers. Now here is were it gets strange. I ended up using fdisk and blew away the partition on the back up server and reinstalled netware 5.0. I can still assign a 252 subnet. On one production server I had to contact support becasue I was having nici errors and no one would authenticate to the server (licenses). I cleared the nici errors and ran the uninstall script for the tcpip enhancement and also copied the previous old files back were they came from. All is well, but I can still assign a 252 subnet. The last production server did not have any nici problems and I did nothing to remove the enhancement and of course I can assign a 252 subnet to it as well. The only problem with this box is that whenever it is rebooted the system must be reinitialized for it to bind it's ip addresses. My delima is this, I need to reassign the addresses to a private 192 ip and 252.0 subnet, but I don't want the servers to go south like my back up server did. Need a list of things to check to ensure that nothing goes wrong when I make the changes. I feel pretty confident that I can make the changes and nothing will happen, but the back up server having to be rebuilt is probably what scares the heck out of me. I just want to make double sure before I make the changes.