How to add TCP/IP to an SFT III server

I have installed an NLM on an 4.12 SFT III server that implements time syncing through NTP. Obviously it requires TCP/IP.
I ran INETCFG and and Enabled TCP/IP. Then I gave the engine the IP address of 192.168.1.250. According to the help, I should another unique IP address to the network cards using the same address for both cards. When I attempted to do this the second card errored out with an IP address conflict.
The documentation is fairly silent on this and most of the third party notes I can find address Netware 4.12 single server. SFT plays by a different set of rules.
Does anyone have experience with this that could give me the quickstart version of a howto?
LVL 1
scarpenter104Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ShineOnCommented:
Is this NLM specifically made for 4.x servers to use an NTP time source for timesync?

Is it a third-party NLM or is it a Novell-provided NLM?  What is the NLM?  I'm asking because there may be relevant documentation somewhere, but I have no idea where to start.

TCP/IP is available on NetWare 4.x only for certain things.  I don't know if they ever set up the 4.x TCP/IP stack to fail over with SFTIII.  Maybe someone else knows...

Do you only have the one SFTII pair, or are there other NetWare servers in your network / tree?  Perhaps you could use a non-SFT server as the Timesync time source, with the NTP module running on it, and have the SFTIII pair set as secondary.

Alternatively, upgrade to a currently-supported version of NetWare, which comes with 2-node clustering built-in, that doesn't need a special card like SFT did, and natively works with NTP time sources (and can act as an NTP time source as well.)
0
scarpenter104Author Commented:
Read about the NLM here: http://www.novell.com/coolsolutions/tools/13717.html

I'm not having issues with the NLM but with TCPIP itself. When I enable TCPIP in INETCFG I can run the ping utility and successfully ping itself.
When I Bind IP to a NIC I can ping that NIC from outside but the Netware ping utility can't ping it. It appears there is no connection between the internal network and the network cards. When I try to enable forwarding on the internal network it will not enable. It say disabled and won't let you change it.

It is the only NDS server on the LAN.

Upgrading is not an option. Any input is appreciated.
0
ShineOnCommented:
Can you post your sys:\etc\netinfo.cfg file  (I think they still called it that back then) and your other IP-related files from SYS:\ETC (like hostname, hosts, resolv.cfg, tcpip.cfg, gateways, networks)

Since TCP/IP is kind-of an afterthought on 4.x and prior, it's very possible that not all of the required components have been configured.

Let's get IP working first, on your primary of the SFT pair, and deal with making it work in an SFTIII failover as a secondary issue.
0
Cloud Class® Course: CompTIA Cloud+

The CompTIA Cloud+ Basic training course will teach you about cloud concepts and models, data storage, networking, and network infrastructure.

scarpenter104Author Commented:
Here's everything network related that I know of:

INITSYS.NCF:
load snmp config=SYS:ETC
initialize system

NETINFO.CFG:
#!SERVERTYPE=MSENGINE
#!SERVERNAME=PARAGON_SFT
#!
#!BEGINGENLOAD
LOAD SNMP
#!END
#!
#!BEGINTSMLOAD
#!END
#!
#!BEGINPROTO PROTO=IPX STATUS=ENABLED
#!END
#!
#!BEGINPROTO PROTO=TCPIP STATUS=ENABLED
LOAD Tcpip RIP=Yes Forward=No
#
BIND IP MSENGINE Address=192.168.1.251 Mask=FF.FF.FF.0
#
#!END

TCPIP.CFG
AutonomousSystem 0
Protocol rip on {
}
Protocol egp off {
}
Protocol ospf off {
}

IOAUTO.NCF:
LOAD N100 SLOT=10009 FRAME=Ethernet_802.2  NAME=N100_1_E82
BIND IPX N100_1_E82 NET=B
LOAD N100 SLOT=10009 FRAME=Ethernet_802.3  NAME=N100_1_E83
BIND IPX N100_1_E83 NET=A
LOAD N100 SLOT=10009 FRAME=ETHERNET_II NAME=LAN_IP
LOAD TCPIP
BIND IP TO LAN_IP ADDR=192.168.1.250 MASK=255.255.255.0 GATE=192.168.1.1
0
maquesCommented:
I'm not a great SFT III wizard, those I've seen usually ended up the half shut down and ran as standalone server fine. However, as far as I understand, there are two IOENGINE-s (for the two server) and a "common" MSENGINE, for those and between them you have to set up TCP/IP to work correctly.

This article could be your friend:
http://support.novell.com/docs/Tids/Solutions/10014741.html

TCP/IP Configuration on NetWare SFT III
...
symptom: Server Mirroring on NetWare 4.11 or 4.2
      Can't configure tcpip on SFT III
      Can't ping from SFT III
cause: TCPIP needs to be configured on an SFT III server pair.
...
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
scarpenter104Author Commented:
Believe it or not, this is not abandoned. This is just a remote client that I don't get out to much and a very low priority issue. I will update as soon as I take the next step.
0
scarpenter104Author Commented:
*Sigh* Believe it or not, still not abandoned, just stalled.
0
scarpenter104Author Commented:
Never was able to confirm this but I believe this would be the solution for my issue.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Novell Netware

From novice to tech pro — start learning today.