Product

Platform

Operating system

Error

Symptoms

Any or all of the following:

- consistently poor network throughput, for example as measured by the standard Creo/HDPP NetPerf utility.

- intermiittent Orbix-related CORBA communication failures

- "no Prinergy servers were found on the network" message at Workshop startup

This last is a symptom of the Locator Daemon (PLocatorD.exe) on the primary node not responding to Workshop client requests via IP multicast.

Cause

device driver configuration settings.

Prinergy server software is highly sensitive to Windows NT/Windows 2000 network configuration, for example the wrong version of device drivers or inappropriate Control Panel settings.

On all Intel processor-based systems shipped by CreoScitex for use with Prinergy, the Intel EtherPRO/100 or similar adapter is standard issue.

This adapter may go by a variety of display names, but is always

based on the same underlying Intel 825xx core chipset.

The device driver file itself is e100bnt5.sys for Windows 2000 and e100bnt.sys for NT 4.0.

Solution

On Windows 2000, the network driver should be dated Jan 2000 or later. The original driver shipped on the retail Windows 2000 CD dated Oct/99 will NOT work reliably. An updated version of the driver can be obtained from the Intel website.

After updating to the correct version of the driver, go to the Advanced tab, click "Adaptive Technology", and ensure it is set it to OFF. The default when the new driver is installed manually is ON. Turning this setting OFF should result in improved network transfer speed and makes various Orbix and Locator Daemon problems go away.

Any CreoScitex-prepared ghost image for the system disk should already have the correct version of the network driver and the Adaptive Technology setting appropriately disabled.

Permanent fix:

See also

Keywords

networking, orbix

Technical contact(s)

Simon Chen

Submitted by

Date submitted