nw 3.12 autoexec.ncf problem

Posted on 2000-04-10
Last Modified: 2008-02-01
hi im running 3.12 and am trying to change the external net address.  i changed it in autoexec.ncf but it still did not change.  so i rem'd out all of autoexec.ncf and everything still came up the same!!  obviously the autoexec.ncf that i modify using install is not being read.  how is that possible?  what is being read and how can i modify it?
Question by:enoch010299
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
  • 2
  • +2

Expert Comment

ID: 2702599
form the console:
-Unbind and rebind the NIC card
-On the bind statement make sure you put "NET=Your_New_Segment_number"
Then go to monitor>and check the LAN statistics, you should see the segment number you entered above.
-also if you type "config" you should see the new net number
-Use Hexadecimal numbers only when you specify the NET=

Of course when you change autoexec.ncf you have to reboot... for the changes to take effect. (...Just in case you are new to NetWare)

To make sure you are editing the right autoexec.ncf, at the console:
load edit sys:system\autoexec.ncf
But if you did it with install, it should be the right one:
-you have to save the edited autoexec.ncf when you return to install.

By the way:
If you rem out everything, in autoexec.ncf, when the server will reboot it should ask you for the "Name of the server" and the IPX internal net number"

Author Comment

ID: 2702621
I did unbind and bind the NIC, that does the job.  But the problem is I need it to do it automatically in autoexec.ncf.  I also did rem out everything in autoexec.ncf, but it did not ask for "name of the server"'s getting this somewhere else when I reboot.  Also, you don't have to use hex numbers when entering the net address.  I am saving correctly as the autoexec.ncf file maintains the changes I make on it.  Thanks though!

Expert Comment

ID: 2702799
Run inetcfg at the console prompt.
If your system has been setup with this then your net binds etc are not used in autoexec.ncf
You will be able to change the settings in this.

Salesforce Has Never Been Easier

Improve and reinforce salesforce training & adoption using WalkMe's digital adoption platform. Start saving on costly employee training by creating fast intuitive Walk-Thrus for Salesforce. Claim your Free Account Now


Expert Comment

ID: 2703457
Zombite has a point. I was not sure if 3.12 was using inetcfg.
But if you rem out everything (I mean every lines) in autoexec.ncf it has to ask you the name of the server and the IPX internal net number. If not you have another problem.
If you want to see: rename autoexec.ncf to autoexec.old.

Author Comment

ID: 2703551
Unfortunately, Zombite, 3.12 does not use inetcfg.  

Expert Comment

ID: 2703722
Explain your configuration a little bit: nic, special setting etc...
You cab always try a brand new autoexec.ncf with just the server name, internal IPX number and only one load NIC... and bind statement.
Interesting problem!!!

Expert Comment

ID: 2703926
Check is there is an autoexec.ncf on the C: drive, either instead or as well as startup.ncf. There was is fudge required with 3.12 if you required extra ram, plus a couple of other oddities that required an autoexec.ncf on the c: drive.


Expert Comment

ID: 2704160
cczjtw's right... I've run into that before. Check the C drive for for an autoexec.ncf and change it there.

Author Comment

ID: 2705993
You are right...cczijtw was right.  So I'll let him propose the answer.  Thanks all!

Expert Comment

ID: 2706194
Well done enoch.

Accepted Solution

cczjtw earned 200 total points
ID: 2706623
Ok so I'll resubmit it as the answer:

Check is there is an autoexec.ncf on the C: drive, either instead or as well as startup.ncf. There was is fudge required with 3.12 if you required extra ram, plus a couple of other oddities that required an autoexec.ncf on the c: drive. Additional information, the oddities, were some system parameters, that were only allowed on autoexe.ncf, but were required before loading the disk drivers or mounting any volumes.


Featured Post

Creating Instructional Tutorials  

For Any Use & On Any Platform

Contextual Guidance at the moment of need helps your employees/users adopt software o& achieve even the most complex tasks instantly. Boost knowledge retention, software adoption & employee engagement with easy solution.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Novell DNS in conjunction with Microsott DNS 3 307
Poor enterprise laptop performance (Any Tips?) 5 597
SLP Server crash 2 857
Problem trying to load a dos netware client 6 593
This article describes how to import an Outlook PST file to Office 365 using a third party product to avoid Microsoft's Azure command line tool, saving you time.
After hours on line I found a solution which pointed to the inherited Active Directory permissions . You have to give/allow permissions to the "Exchange trusted subsystem" for the user in the Active Directory...
In a recent question ( here at Experts Exchange, a member asked how to run an AutoHotkey script (.AHK) directly from Notepad++ (aka NPP). This video…

739 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question