Server 2008 NFS sharing a folder with Character Translation

[krandun]

Hello. I'm trying to mount an NFS share hosted on Windows Server 2008 on a
Linux client (Fedora 11). I have the Active Directory user mapping set up,
and the folder is shared to my network. I can mount the share just fine, I
can create and delete files and folders in the NFS share from my Linux
client. The problem I'm having is that Character Translation seems not to be
working at all.
I have set up a translation file (C:\Temp\mangle.txt) containing one line
(0x00 0x3a : 0x00 0x2d ; Replace ':' on client with '-' on server).
I have checked the checkbox for "Translate File names:" in the Server for
NFS Properties.
I have made sure that the "Translate file names" box is pointing to my
translate character file.
I still get an IO error on the client when I try to create a file with a :
in the name.

I have tried changing this translation file to turn some arbitrary character
into another arbitrary character (change 'T' into 'r' for example) and that
has no effect, either. I've checked and re-checked all of these settings,
restarted the NFS server service, rebooted the server machine, powered off
the server machine for 5 minutes, then turned it back on. Nothing seems to
make a difference.

What am I doing wrong? How do I make this work?

[Ashish]

I think you are running in to this problem - http://support.microsoft.com/kb/958144

The download link for this hot fix is -
http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=958144&kbln=en-us

- Ashish

[krandun]

Ashish,
Thank you for the suggestion. I have applied this hotfix on all 3 of the
machines in the cluster, and rebooted them. Nothing has changed, as far as I
can tell.

[Ashish]

Hmm...

Were there any events related to character translation before this hot
fix? Do you see them now as well?

- Ashish

[krandun]

Ashish,
Wow, I apologize for my last message. Apparently the pop-up message I got
at the end of install on each server was saying "This patch does not apply to
your system" and not "This patch has now been applied", and I didn't notice.
I have downloaded all 3 of the versions of that patch and tried them, with
the same final message (The update does not apply to your system). I had the
1057 error in the system log (which I hadn't checked before. I apologize
again.) before the patch, but I'm not seeing any new errors now.

[Ashish]

What does your character translation file looks like now?
Can you paste it here?

- Ashish

[krandun]

Certainly. It contains one line:
0x00 0x3a : 0x00 0x2d ; Replace : on client with - on server. I hope.

It is saved in plain-text format, and stored in the root on the drive that's
shared by my cluster (so whichever node in the cluster is currently managing
the share will have that file).

[Ashish]

Can try storing this file on a local drive on both nodes and see if
that helps. I know that storing UNM source files etc didn't work fine
so just thinking that may be the case as well.

If that doesn't work - please send me an email through my blog on MSDN
- http://blogs.msdn.com/sfu - I think you will someone to assist you
with it.

- Ashish

[krandun]

I created a test install on a machine that's not connected to anything except
my Linux client, configured everything (except the clustering, since it's
only one box) and applied the hot fix you suggested to that machine, and
character translation works on that machine. I'm guessing that the problem is
that the cluster I'm trying to do this on is fully updated (including SP2)
while the patch only applies to SP1. Though, the download link does say
"SP2". Odd.

Okay, moving the translation file to a fixed location on each node.
... Wow. I feel really stupid now. That fixed it! Thank you so much!
The person who is actually in charge of the FS cluster started to set it up
that way, then turned it over to me. I set it up with the character
translation file in the share, so I could change it and not worry about which
node it was on. Obviously I am doing it wrong.
Thank you, thank you, thank you.