Can the NDPS Manager specify an IP address?

(Last modified: 04Dec2002)

This document (10065012) is provided subject to the disclaimer at the end of this document.

goal

Can the NDPS Manager specify an IP address?

What does the NDPSM /IPADDRESS switch do?

fact

Novell NetWare 6.0

Novell NetWare 5.1

NDPSM v3.0

NDPS v3.0

Novell Distributed Print Services v3.0

symptom

On a server with multiple IP addresses, the NDPS Manager listens to the IP address of the first card loaded.

On a server with multiple NICs and multiple IP addresses, the NDPS Manager listens to the wrong IP address.

The NDPS Manager shows status down in NWADMN32.

Multiple IP addresses are bound to the server.

Error:  IP address X.X.X.X, specified at load time, is not bound.

The IP address on the server has changed

NDPS Manager is unable to load.

cause

The NDPS Manager can only bind to one IP address on a NetWare server.

fix

The below fix is available for NetWare 5.1 or NetWare 6.  NetWare 5.0 customers need to upgrade their OS to get this functionality.

NDPSM v3.00 dated 04SEP2001 or later has the ability to specify an IP address using the /IPADDRESS= switch.  (NDPSM.NLM v3.00 dated 04SEP2001 ships with NetWare 6.0.)  For example, if you have a NetWare server that has two IP addresses bound to it (10.1.1.1 and 137.65.215.36) and you want the NDPS Manager to bind to the 10.1.1.1 IP address, you would do the following:

LOAD NDPSM ".NDPS-MANAGER-NAME.OU.O" /IPADDRESS=10.1.1.1

With the /IPADDRESS= switch enabled, the NDPS Manager does a check to see if that IP address is actually bound to the server.  If the IP address specified is invalid (not bound) due to a typo, the NDPS Manager will return an error.  The error shows up in a red "Error Report" box on the NDPS Manager and the manager will not load.  The error reads as follows:

========
NDPSM-3.00-895

IP address 10.1.1.2, specified at load time, is not bound.

Program execution cannot continue normally.
========

ISSUES WITH NDPSM v3.00 DATED 04SEP2001

In prior implementations of the NDPS Manager, the NDPS Manager would just load and take the IP address that is bound on the server and start listening for NDPS traffic.  With NDPSM v3.00 04SEP2001, the NDPS Manager now goes and looks at the SYS:ETC\HOSTNAME file and compares the IP address in that file to what is currently bound on the server.  If the address that is bound does not match what is in the SYS:ETC\HOSTNAME file, then you will receive the error above, as if you had used the /IPADDRESS= switch with an invalid IP address.  To work around this, you can do the following:

*  If the SYS:ETC\HOSTNAME file exists and contains an IP address, but IP is no longer bound on the server (server is IPX only), then delete or rename the SYS:ETC\HOSTNAME file.

*  If the SYS:ETC\HOSTNAME file exists and contains an IP address, but IP is no longer bound on the server (server is IPX only), then go into INETCFG and bind the IP address that is found in the HOSTNAME file.  You will need to make sure that the IP address found in the HOSTNAME file is valid and not in use by any other device on the network.

*  If the SYS:ETC\HOSTNAME file exists and contains an IP address, but the IP address of the server has changed, then modify the IP address found in the HOSTNAME file to what is currently bound on the server.

*  In a clustered environment, in addition to the /DBVOLUME=NOCHECK switch, you will want to add the /IPADDRESS= switch to your load script.  Otherwise, you may get the above error.

document

Document Title: Can the NDPS Manager specify an IP address?
Document ID: 10065012
Solution ID: NOVL59238
Creation Date: 26Sep2001
Modified Date: 04Dec2002
Novell Product Class:NetWare

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.