Changing IP address in Novell Server 5.1 for all those Novell Guru's 1

[Guest_imported]

I recently went through changing ISP and had to configure my whole network. I'm running a Nat table through my netopia router. My windows server was assigned a nat address and so did my other computers. Now my Novell server is not able to come online to the network. I've gone into inetcfg and changed the ip addresses but because the Novell server is not recognized in the router it's not assigned a address. I've given it a internal address which works fine within the network. The other computers can log into the server but I can't use Portal and I get a TIMESYNC: unable to communicate with server error because the server can't access the internet. It was easy setting up the ip address when I first set up the server but to change it or set it up so the router will automatically give it one is a hassle. Can anyone help me out? Sorry for this long thread.

Peace

 

[TheLad]

Have you changed/assigned a default route? This is the servers default gateway and should be your local router. This can be configured by going into INETCFG, choose PROTOCOLS, choose TCP/IP, and under LAN STATIC ROUTING TABLE check to ensure that there is a Default route set. Also check to ensure it is the correct IP address.

If the default route is incorrect, delete the route and press INSERT to add another route. Route type will be DEFAULT ROUTE. Add the router IP address into the NEXT HOP ROUTER ON ROUTE section.

Also in INETCFG, choose BINDINGS, TCP/IP, and ensure that the IP address and subnet mask are entered correctly.

You will also have to go into DSREPAIR -A, Advanced Options menu, and run a CHECK EXTERNAL REFERENCES. -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[TheLad]

Check out the following TID for additional stuff you may have to do when changing the IP address:

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

-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[Psychoid]

The original install of NW5.1 doesn't use INETCFG, so if you've never run INETCFG before, your bindings will be in your autoexec.ncf file (sys:system\autoexec.ncf)

Just edit the line that reads something like:
bind ip NAME_OF_NIC addr=ADDRESS mask=MASK gate=GATEWAY

Example:
bind ip 3c90x_1 addr=192.168.1.2 mask=ff.ff.ff.0 (or 255.255.255.0) gate=192.168.1.1

The gate= switch may or may not be in there..... In order to make this work, though, you should put it in with the IP of your default gateway.

Hope this helps

Bill ------------
Certified in absolutely nothing

 

[SuperDaveDCF]

Psychoid makes a good point on a issue I just addressed today. I made an IP change on a 5.1 server yesterday using inetcfg. The change didn't occur properly and the symptoms were that the server could ping itself and the router (gateway) but could not get beyond that. I also could not ping it. I couldn't seem to find a setting in inetcfg to input the gateway so I had to do it manually in the sys:\etc\netinfo.cfg file. This is where inetcfg transfers the settings to. Once I did that the problem was resolved.

I also had an error with the NDPS manager that said the address wasn't the same as when it was created. This was because the sys:\etc\hosts file wasn't changed when I changed the address with inetcfg.

 

[salserocito]

OK folks...

According to Novell (I've already been through this), the GATE= switch no longer works with NetWare v5.1 when launched from the AUTOEXEC.NCF. The ADDR= and MASK= switches still work the same.

If you DO NOT use INETCFG, then you must go into TCPCON and configure a NEXT HOP... TCPCON/IP ROUTING TABLE/NEXT HOP.

***Please note... if you set your NEXT HOP through TCPCON, anytime you reboot your Server, this route is lost and must be input again.

Basically, Novell WANTS you to start using INETCFG.

Let INETCFG transfer all of the LAN info. BUT, it WILL NOT pull the GATE= switch from the AUTOEXEC.NCF. Again, you must manually configure your Default Gateway...

1. INETCFG - PROTOCOLS - TCPIP
2. Modify LAN STATIC ROUTING to ENABLE
3. ENTER on LAN STATIC ROUTING TABLE
4. Press <INS> to add a Static Route
5. Press ENTER on ROUTE TYPE and selct DEFAULT
6. Enter the TCPIP Address of the NEXT HOP and ENTER
7. <ESC> and save

When adding a Default Route through INETCFG, it only has to be done once!

Hope this helps!

Good Luck!

 

[Psychoid]

Without peeing in anybody's Cheerios, I can assure you that the gate= command in autoexec.ncf works.

I wasn't trying to address whether or not somebody should use inetcfg.... it has its good and bad points.

The goal was to get this guy's box talking again in an easily understood manner. ------------
Certified in absolutely nothing

 

[salserocito]

Psychoid...

Before you pee on anyone, check out this TID...

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

My assumption is you must not have your Server to NW51SP3 or later...

You say tomato, I say tomato... so what!

Cheerio!!!!

Good Luck!

 

[TheLad]

The reason I have always used INETCFG is because it is so easy to configure. You also have extra options to consider which you can enable/disable in INETCFG.

For example, IP Packet Forwarding causes more traffic on your network and can be disabled easily in INETCFG. Same with IPX. Saves time trying to figure out what the command line option for stuff like this is if you don't know already.

For anyone starting out configuring NetWare 5.1, I always show them INETCFG but I also show then SYS:ETC\NETINFO.CFG and how it writes the commands into the file. This way, they have the ease of configuring the server via the GUI interface of INETCFG, but they are also aware of what the command line parameters are should they ever need to use them.

For the record, I say tomato -----------------------------------------------------

&quot;It's true, its damn true!&quot;
-----------------------------------------------------

 

[tekieVB]

Server name change, serverID change or IP address change - READ Novell's TID10063497

Everyone is correct in one aspect or another. I personally find it easiest to use inetcfg. It properly updates the sys:etc\netinfo.cfg. Not sure if it is still an issue or not, but use to be if you touched the netinfo file it would no longer load properly and cause you all kinds of headaches.

First time you run inetcfg it will import all of the autoexec.ncf networking cmds into itself (associated files behind the scenes) and immediately prompt you to restart the server, so be ready!

Everyone have a nice day!