Home | Contact Us | Submit Troubleshooting Info | Search | Help


    Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS


Cannot add/access shared Unix volumes in Prinergy


Product

  Prinergy Connect 2.0

Platform

 

Dell and Data General all

Operating system

 

Windows 2000


Error

 

When trying to add shared Unix volumes in Prinergy system configuration: "ARAXI PFileD.GetShares956 iFILE_FileImpl.cpp(730): Caught COMN_Exception; code = 1007044; Unable to determine shares for node:"

When trying to create a job on the Unix server: "Problem with file server : Could not access a server to look up network file-share information.[1100005]"


Symptoms

 

You can browse to the Unix server from Windows Explorer on the Prinergy server, but when you try to add shares in Prinergy, you get an error in Diagnostics indicating that shares could not be determined.

When trying to create a job on the Unix tertiary server, you get an error indicating that the server could not be accessed.


Cause

  Samba could not use SMB encryption on passwords until version 2.0 (late 1998). Some Unix administrators only want to use non-encrypted passwords, so they modify the Windows registry to allow this and to not set up SMB encryption support in Samba.

(The following information is from the Samba help files.)

WinNT refuses to connect to a server that is in user level security mode and that does not support password encryption unless it first prompts the user for a password. This means even if you have the same password on the NT server and the Samba server, you will get prompted for a password. Entering the correct password will get you connected only if Windows NT can communicate with Samba using a compatible mode of password security. All versions of Windows NT prior to 4.0 Service Pack 3 could negotiate plain text (clear text) passwords. Windows NT 4.0 Service Pack 3 changed this default behaviour so it now will only handle encrypted passwords.

The only two things you can do to stop this are to enable SMB encryption, which requires Samba v2.0 or better, or to enable plaintext passwords under Windows.


Solution

 

Have the Unix administrator set up SMB encryption support in Samba.

Note: You must also set up the Prinergy etc/otherhosts file for Macs to access PDFs on the Unix server.

Alternate Solution: The following information is from the Samba help files:

The following registry entry change will re-enable clear text password handling:

In Windows NT 4:

1) Rrun regedt32.exe and locate the hive key entry HKEY_LOCAL_MACHINE\system\CurrentControlSet\Services\Rdr\Parameters\.

2) Add the following value: EnablePlainTextPassword:REG_DWORD=1

In Windows 2000:

1) Rrun regedt32.exe and locate the hive key entry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkStation\Parameters.

2) Add a new DWORD value: Value Name: EnablePlainTextPassword Data: 0x01

Permanent fix:


See also

 


Keywords

 

networking, Unix


Technical contact(s)
 

Rob Prior

Submitted by
 

Tom Derr

Date submitted
 

10 Apr 2002


    Copyright © 2005 Creo Inc. All rights reserved. Confidential. Back to top.