![]()
Home | Contact Us | Submit Troubleshooting Info | Search | Help
Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS
|
|
||
Product |
Prinergy 1.1; Prinergy Connect 2.0 | |
Platform |
Server: Dell or Data General all; Client: PC or Macintosh |
|
Operating system |
Server: Windows NT or 2000; Client: Windows or Macintosh |
|
|
|
||
Error |
No Prinergy servers found on the network |
|
|
|
||
Symptoms |
Attempt to launch Prinergy Workshop fails with an error message indicating that no Prinergy servers could be found. |
|
|
|
||
Cause |
Possible causes: A) The Workshop client and the primary server are not on the same subnet, so the switch/router is not forwarding multi-cast packets. B) Heavy network traffic is causing UDP datagrams (multi-cast messages) fail to reach the primary server. C) Prinergy Locator Daemon is not running. Prinergy Workshop sends a multi-cast message to discover the available Prinergy primary servers on the network. The Locator Daemon running on the primary server responds to the message and Workshop populates the user interface with the server name. Assuming the network is functioning properly, this enables users to log in to the server without knowing the name or IP address of the primary server. If there is heavy traffic or the transfer mode (duplex setting) is not set properly causing low throughput, UDP traffic is lost and the locator deamon does not receive the message. However, if any of the above conditions exist, the Locator Daemon will fail to properly populate the user interface with the name of the primary server. |
|
|
|
||
Solution |
Check the network configuration. Ensure that all computers, hubs, switches etc. are configured to use the same network transfer mode, either all half-duplex or all full-duplex. Note that performance tests indicate half-duplex yields better overall throughput. If workshop cannot detect the primary server, it is not critical. Workshop remembers the last server you logged on to, so you can usually just continue to log in. Alternatively, you can type in the IP address of the primary server. Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
networking |
|
|
|
||
Technical contact(s) |
Simon Chen |
|
Submitted by |
Sinisa Nojkovic |
|
Date submitted |
11 Apr 2002 |
|