I have a OSR505 system and a OSR506 system running Visionfs 3.10.911.

When I view files in a directory in the Visionfs fileserver from my Windows
PC (W2000 in my case), they have a creation or access date as 12 hours
ahead.

I look at the files from a UNIX prompt and their Date and Time is correct
(i.e. the date and time they were created or modified).

It appears Visionfs is doing the misreporting of the "Current Time" and
passing it on to Windows to display in the "Modified" column.

To demonstrate that , when I do a "net time" request from a command prompt
on my Windows PC, I get the following 2 answers, as per this example:

H:\>net time \\sytmnz2
Current time at \\sytmnz2 is 4/12/2005 4:52 AM

Local time (GMT) at \\sytmnz2 is 4/11/2005 4:52 PM

The command completed successfully.

The "Current Time" ,which is 12 hours ahead, is being passed to Windows,
whereas the "Local Time" ,which is the correct time, is being ignored.

Does anybody know how I can correct this misreporting of the date and time
in Visionfs?

TIA
Dave