Clients unable to attach to eDirectory 8.6.1 Windows Server via IP.

(Last modified: 15Jan2003)

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

fact

Novell eDirectory 8.6.1

Microsoft Windows NT/2000 Server.

symptom

Clients unable to attach to eDirectory 8.6.1 Windows Server via IP.

Server to Server NDS communication via IP fails with 8.6.1 installed.

Under NDS Services Transports tab, NCP Bound Transports shows a 3xxx or 4xxx port instead of port 524.

change

Installed or upgraded to eDirectory 8.6.1

cause

The NCP listener is configured to listen on a dynamic high TCP and UDP port instead of port 524.

fix

This can be resolved by editing the transports section of the config.acs file as described below:

Stop the NDS Server Service.

Edit the C:\Novell\NDS\DIBfiles\config.acs file. Below is a clip from a sample config.acs file:

[NCP Engine/Transports/Enum/000] = {0x00 0x00 0x03 0xf9 0x00 0x06 0x10 0x10 0x19 0x56 0x00 0x00 0x00 0x00 0x00 0x01 0x04 0x51}
[NCP Engine/Transports/Enum/001] = {0x00 0x00 0x00 0x06 0x00 0x02 0x0c 0x02 0x51 0x56 0x41 0x89}
[NCP Engine/Transports/Enum/002] = {0x00 0x00 0x00 0x11 0x00 0x02 0x0c 0x02 0x51 0x56 0x41 0x89}

The first line is the IPX address. The first five bits are header information (ie: 00 00 03 f9 00). The next five is the internal IPX address (10101956 here). The next six is the node address, which is always 000000000001. This is followed by the last two bits for socket 451.

The second and third lines are the TCP address and UDP address. Again, the first five bits is header information. The next two bits are the port. This should always be 0x02 0x0c for port 524. The remaining bits represent the actual IP address of the interface.

Finally if there were extra lines in here for bindings that were deleted, such as a bogus binding listed under a good binding, the number of entries for NCP Engine will have changed. The NCP Engine/Transports/Enum line represents the number of NCP Engine entries. This line needs to be changed to reflect the new number of entries if any were deleted. For instance, if there had been a NCP Engine/Transports/Enum/003 line in the above example that had a bad port on it, and it was deleted to get rid of the bad port, the original value of NCP Engine/Transports/Enum would have been 0x00000004. It would need to be changed to 0x00000003.

Once the change has been made, delete the transact.acs file in the same directory if it exists. Restart the NDS Server Service.

document

Document Title:	Clients unable to attach to eDirectory 8.6.1 Windows Server via IP.
Document ID:	10068554
Solution ID:	NOVL72798
Creation Date:	25Feb2002
Modified Date:	15Jan2003
Novell Product Class:	NetWare Novell eDirectory

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.