Filename character translation
Recently we got a case were File character translation was not working on customer’s environment.
On troubleshooting we found that the entries in the translation file were incorrect:
The correct entry is ‘0x00 0x3a : 0x00 0x2D’ but customer had the entry as ‘0x00 0x3a : 0x00 0x2d”.
After making the changes, we restarted the Server for NFS service from the Windows side which resolved the issue.
To create a character translation file for Server for NFS, you must use a pure ASCII text editor, such as Notepad. Do not use a word processing program. The format of the file is a list of mapped characters and their translations. The following text is an example of an entry in the file, where nn is the hexadecimal value for the character and the character is shown in double-byte mode:
0x nn 0x nn : 0x nn 0x nn [ ; comment]
All text on the line after a semi-colon is ignored as a comment. To use the translation file to map the question mark (?) to a dash (-), type the following line in the file:
0x00 0x3f : 0x00 0x2d ; replace client ? with server dash "-" ? Format
To prevent problems, you may want to translate the following characters:
• Asterisk (*): 2a
• Colon (:): 3a
• Question mark (?): 3f
Note The hexadecimal numbers in the character translation file must be exactly two digits.
Configuring Server for NFS to Use a Character Translation File
1. Log on to the Server for NFS computer by using an administrative level account.
2. Click Start, point to Programs, point to Services for UNIX, and then click Services for UNIX Administration.
3. Click the Server for NFS pane, and then click the Server Settings tab.
4. Under File name handling, click to select the Translate File names check box.
5. Type the full path to the translation file that you created in the Use character translation files box, or click Browse to locate the file.
6. Click Apply
Comments
- Anonymous
January 01, 2003
I had discussed on using File Name Translation over NFS here . Some additional information and an alternative