Conflict between ARCserve and NetWare NFS or NetWare UNIX Print Services
(Last modified: 19Oct2004)
This document (10065725) is provided subject to the disclaimer at the end of this document.
fact
Novell NetWare NFS Services 3.0
Novell Native File Access Pack
Novell Native File Access for UNIX
Novell NetWare NFS Services 2.4
Novell NetWare NFS Services 2.3
Novell NetWare UNIX Print Services 2.5
Novell NetWare UNIX Print Services 2.3
Novell NetWare 6.0
Novell NetWare 5.1
Novell NetWare 4.2
symptom
Conflict between ARCserve and NetWare NFS or NetWare UNIX Print Services
If NetWare NFS or NetWare UNIX Print Services are loaded before ARCserve, the ARCserve management tool (run from Windows) will fail to contact ARCserve on the NetWare server.
If ARCserve is loaded before NetWare NFS services, NFS clients and NIS clients will not be able to find the NFS Server or NIS Server.
Error : NFS services initialization failed during PKernel initialization - Error Code : 65544. Unloading XNFS.NLM.
Error : PKERNEL-Error : Failed to initialize RPC Services. Exiting..
cause
ARCserve and certain Novell products both provide a SunRPC port mapper which controls port 111. Both programs cannot control the same port at the same time.
fix
To make these programs co-exist, the port mapper in ARCserve 7.0 must be configured to use a different port. Workstations running the management utility must also be configured to contact the different port. Instructions for this process are below. These instructions were taken from document 19103 at the Computer Associates support page (http://support.ca.com), but additional clarification of several points has been added. Novell strongly recommends reading the Computer Associates technical document as well, as it may contain information pertinent to other ARCserve concerns. For example, if ARCserve for Unix is in use, additional information should be obtained from that document.
1. CATIPRC.NLM can be loaded with ports specified for IP, SPX, IPX, and TISPX; and with a -d option to spawn an additional debug screen which will report the success or failure of each port's initialization. The -d parameter is always optional, but will still be shown in some "minimum required" examples below, as it's presence is helpful during the set up and troubleshooting process. For example, if CATIRPC were loaded with all the default ports set explicitly, and with the debug option on, the load command would look like this:
CATIRPC -ipport=111 -spxport=36890 -ipxport=36889 -tispxport=36913 -d
Keep in mind that the example above shows all the default ports. In order to solve the conflict, some of the ports may need to be changed.
Novell's testing showed different minimum implementations necessary, depending upon the Novell product in use:
a. For NFS 2.x; Unix Print Services 2.x; NFS 3.0 (Shipping version); NFS 3.0 SP1; NFS 3.0 SP2; NFAP 1.0 for NetWare 5.1 (shipping version): The minimum necessary is to manually change the following line in the ASCONFIG.INI file from:
NLM8=SYS:\ARCSERVE\NLM\CATIRPC
to
NLM8=SYS:\ARCSERVE\NLM\CATIRPC -ipport=120 -tispxport=36915 -d
(NOTE: the IP port 120 and TISPX port 36915 were available ports arbitrarily chosen and tested by Novell. Those ports may not be available on every server. Any available port should do. If conflicts still occur, try another port).
b. For NFS 3.0 SP3 and above; NFAP 1.0 for NetWare 5.1 SP1 and above; and NFAP for NetWare 6.0 (any support pack level): The CATIRPC configuration above will still work with these levels, but the true minimum required in these cases is to manually change the following line in the ASCONFIG.INI file from:
NLM8=SYS:\ARCSERVE\NLM\CATIRPC
to
NLM8=SYS:\ARCSERVE\NLM\CATIRPC -ipport=120 -d
(Again, note that port 120 is an arbitrarily chosen example of a port which might be available).
2. Windows workstations running the ARCserve Manager will need to be configured to know the new port on which ARCserve is listening. In REGEDIT, create the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\ARCserveIT\Base\AlternateRPCPorts
Then within the key, choose to create one or more of the following options, based on your environment:
Option 1 - Global Port Address
Create a DWORD Value, "DefaultPortNumber". Select the "Decimal" radial button and set this value in to correspond to the IP port number assigned for CATIRPC in the ASCONFIG.INI file. For example, if CATIRPC has been assigned ipport 120, then the value for the "DefaultPortNumber" registry setting must also be 120 in decimal. This registry setting will be used unless it is over-ridden by the existance of other keys, described in option 2, below.
Option 2 - Server Specific Port Address
Create a DWORD decimal Value. It's name should be the IP host name (as known to the Windows workstation) of a server running ARCserve. This is a case insensitive string. Select the "Decimal" radial button and set its value to the IP port number CATIRPC.NLM is configured to use on that server. Effectively, each server can have a different port number.
Both options can be used together. However, if there is a specific port assignment listed in the registry for an RPC server, then the specific assignment will take precedence over the global setting. In short, if option 2 exists for the server in question, it has precedence over option 1.
Customers on NetWare 5.1 or 6.0 (or above) who continue to have conflicts between ARCserve and NFS 3.0 (or Native File Acces for Unix) should update to current Novell support packs. If problems persist, it may be necessary to open a technical support incident with Novell, so the issue can be investigated. At this time there are no further known issues between these products.
.
note
ARCserve's SunRPC implementation is in CATIRPC.NLM.
In NetWare NFS Services 2.x, NetWare Unix Print Services 2.x, NetWare NFS Services 3.0 (up through SP2), and Native File Access Pack (NFAP) 1.0 (original shipping version) for NW 5.1, Novell's Sun RPC implementation involves TIRPC.NLM, RPCBSTUB.NLM, NETDIR.NLM, TCP_ND.NLM, and LOCAL_ND.NLM.
In NetWare NFS Services 3.0 (SP3 and above), NFAP (SP1 and above) for NW 5.1, and NFAP for NW 6.0, Novell's Sun RPC implemenation involves PKERNEL.NLM and RPCBSTUB.NLM.
document
| Document Title: | Conflict between ARCserve and NetWare NFS or NetWare UNIX Print Services |
| Document ID: | 10065725 |
| Solution ID: | NOVL62275 |
| Creation Date: | 30Oct2001 |
| Modified Date: | 19Oct2004 |
| Novell Product Class: | Connectivity Products 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.