Home | Contact Us | Submit Troubleshooting Info | Search | Help
Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS
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 | |
Platform |
Server: Dell or Data General all; Client: PC or Macintosh |
|
Operating system |
Server: Windows NT or 2000; Client: Windows or Macintosh |
|
|
|
||
Error |
||
|
|
||
Symptoms |
Occasionally, when Prinergy Workshop is launched on a client machine, the Prinergy primary server name does not automatically appear in the Primary list, even though everything appears to be running normally on the primary. |
|
|
|
||
Cause |
One side of the network might be configured to use half-duplex, while the other side of the network is configured to use full-duplex, with neither side being configured for "auto-detect". | |
|
|
||
Solution |
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. Alternatively, you may leave some components as "auto-detect", and the mode will be determined by how the other end of the network is configured. Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
networking |
|
|
|
||
Technical contact(s) |
Simon Chen |
|
Submitted by |
Sinisa Nojkovic |
|
Date submitted |
10 Apr 2002 |
|