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 Connect 2.1 ; Prinergy 3.0 | |
Platform |
W2K/Solaris |
|
Operating system |
W2K Server SP4 |
|
|
|
||
Error |
When a Mac client disconnects from an Ethershare volume (Unix), reconnection fails. The following message may be logged in the Unix server (mbkpss001 is the W2K server running SFU Server for NFS). May 29 13:47:55 sydsrv002 unix: NFS server mbkpss001 not responding still trying May 29 13:47:57 sydsrv002 unix: NFS server mbkpss001 ok May 29 13:49:01 sydsrv002 unix: NFS server mbkpss001 not responding still trying May 29 13:49:01 sydsrv002 unix: NFS server mbkpss001 ok May 29 13:50:35 sydsrv002 unix: NFS server mbkpss001 not responding still trying May 29 13:50:35 sydsrv002 unix: NFS server mbkpss001 ok May 29 13:51:42 sydsrv002 unix: NFS server mbkpss001 not responding still trying May 29 13:51:43 sydsrv002 unix: NFS server mbkpss001 ok |
|
|
|
||
Symptoms |
This problem was seen in a Solaris server. When the Windows SFU NFS share is mounted on the Unix server, Mac clients have problems reconnecting to an Ethershare volume on the Unix box. Restarting Ethershare does not fix the problem. When the Windows SFU NFS share is dismounted and Ethershare is restarted, the Mac clients would be able to connect again. The following paired messages may be logged on the Unix station: May 29 13:47:55 sydsrv002 unix: NFS server mbkpss001 not responding still trying May 29 13:47:57 sydsrv002 unix: NFS server mbkpss001 ok May 29 13:49:01 sydsrv002 unix: NFS server mbkpss001 not responding still trying May 29 13:49:01 sydsrv002 unix: NFS server mbkpss001 ok May 29 13:50:35 sydsrv002 unix: NFS server mbkpss001 not responding still trying May 29 13:50:35 sydsrv002 unix: NFS server mbkpss001 ok May 29 13:51:42 sydsrv002 unix: NFS server mbkpss001 not responding still trying May 29 13:51:43 sydsrv002 unix: NFS server mbkpss001 ok |
|
|
|
||
Cause |
||
|
|
||
Solution |
Enabling TCP support in SFU Server for NFS resolved the problem. However, lab tests with Brisques with TCP support enabled resulted in slower network throughput. Advise customers that there may be some performance impact and they should evaluate the effect (if any) on their production system. To enable TCP support: 1. Launch Services for UNIX Administration. 2. On the left pane, select "Server for NFS". 3. On the right pane, click on the "Server Settings" tab. 4. In the "Server options" section, check "Enable TCP support". 5. Click on "Apply" to commit the change. Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
Unix, networking |
|
|
|
||
Technical contact(s) |
Philip Samaniego |
|
Submitted by |
Philip Samaniego |
|
Date submitted |
16 June 2006 |
|