We're experiencing a very strange problem with an NFS mount FROM a Windows 2003 server 
TO a Linux system. The patchlevel of 2003 is below .NET 2.0 (where they had problems 
with this).

What happens is you create a file:

$ touch filename

then

$ ls FILENAME

and you get the same result - it displays it as if it were in caps, but it is not. 
This is NFSv3.

It only happens on this 2003 system. Our Windows 2000 system does not do this.

As for the Linux portion of this, I was reading through the manpage to find out whether 
there were options I could pass that might tighten this behavior, but I see none 
that apply to NFSv3.

I'm simply baffled (yeah, I know, why use Windows as an NFS server - the fact is 
it's a production system and we can't change it right now).

I wonder if anyone has seen this interactivity problem between the two OS's.

It's noted that there are some patches that haven't been applied to this 2003 system 
"yet" - mostly because it's in active production and *everything* is on it, so any 
disaster would bring us to a halt.  So treading with care there.


Thanks.

• Reply or follow-up to this message

• Search this forum
• Start a new thread on a different subject

• Report abuse of the forum