Troubleshooting RCONSOLE.

(Last modified: 13Feb2003)

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

goal

fact

Novell NetWare 5.0

Novell NetWare 4.11

RCONSOLE.EXE all versions

symptom

Error: "RCONSOLE -4.10-112 SPX Establish Connection failed to establish a connection to the desired server."

Error: "RCONSOLE -4.10-113 The server connection was terminated by AllocateConnection"

fix

There are a few things that could be the cause of RCONSOLE errors:

1) Is the REMOTE.NLM loaded on the server? Is RSPX.NLM loaded?

2) Has DS been checked and made sure it is healthy and that everything is synchronizing?

3) Errors can be caused by a router that is filtering out the RConsole SAP. SAP type 0107 is the RCONSOLE SAP, and must not be filtered out if RCONSOLE is to work properly. To verify that SAP type 0107 is active on the server, load IPXCON.NLM | Services | Display entire services table | Look for the server name and verify that 0107 shows up in the Type field next to the server name.

4) A bad NIC card can prohibit the client from establishing the SPX connection.

5) Make absolute certain that all IPX Network Numbers are unique. This is ACTUALLY the number one reason why RCONSOLE fails, but sometimes the hardest to troubleshoot. Download DSDIAG.NLM from http://support.novell.com to assist in gathering those addresses. While very powerful, this tool can be hard to use.

6) Force the frame type on the client instead of Auto-detecting the frame type. This can be done by going to properties of Network Neighborhood, IPX 32-bit Protocol for the Novell NetWare Client for the NIC in the machine | Properties | Advanced IPX tab | Primary Logical Board | Select the frame type (typically 802.2) | Use only the following frame types | select the frame type. Also go to properties of Network Neighborhood | IPX/SPX-compatible Protocol for the NIC | Properties | Advanced tab | Frame Type | Select the frame type.

7) The NIC to which the IPX protocol was bound to may not have initialized properly, even though users may be able to obtain an IPX connection to the server. Unbind the Protocols from the NIC(s) on the server and re-bind the IPX protocol to the card. To do this, load INETCFG | Bindings | and select the IPX protocol (document these settings before deleting and re-adding the binding), delete the IPX protocol and re-add it. Then choose Reinitialize System from the main menu of INETCFG.

Workarounds:
1- At the RCONSOLE screen, press INS and enter the IPX internal network number of the target server. The IPX internal network number of the server can be found by typing CONFIG at the server console. If manually entering the IPX internal network number allows RCONSOLE to work, it could mean that the IPX socket table on that server has been exceeded. Increase the Maximum IPX socket table size from INETCFG | Protocols | IPX | IPX/SPX Parameters | Maximum IPX socket table size. The default is 1200. Increase this value to 2400 to start. The server needs to be rebooted in order to reset this table size.

2- Use RCONJ.EXE. Refer to solution 10014711 on configuring RCONJ.EXE.

document

Document Title:	Troubleshooting RCONSOLE.
Document ID:	10019606
Solution ID:	1.0.36204794.2373582
Creation Date:	21Oct1999
Modified Date:	13Feb2003
Novell Product Class:	NetWare Novell BorderManager Services

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.