PC or SMB created files not visible to Mac clients Windows 2003 se

[Guest]

We recently moved a large share from a Windows 2000 server to a new system
running Windows 2003 server. (530 GB, > 1.1 million files/directories)

It consists of one windows share (not the root directory) an one Mac volume
on the same directory.

If a PC (or a Mac connected to the Windows share via SMB) creates a file or
directory, Macs connected to the SFM volume can not see it.

It is behaving exactly like what's described in KB article 164138, but, that
article applies to NT4...

The file share on the Windows 2000 server has worked fine and in, fact is
working fine, and has more files on it, because there was some stuff we did
not transfer to the new server.

I've got no problems connecting to the volumes, and I'm using the latest MS
UAM for the mac clients.

 

[Jim Seifert [MSFT]]

We have seen similiar behavior with Services for Unix(SFU) installed on
Windows 2003 Server. If this is the case and you are not using SFU try
uninstalling it.

 

[Guest]

No, Services for Unix is not installed on this system.

 

[Guest]

Well, dropping the share, renaming the old directory, recreating the
directory and share and using xcopy to move the files from one directory to
the other took almost a day to accomplish (on a 2.8 GHz Xeon, 2G ram,
SCSI-320 Raid 5, just to move ~ 700 GB of files.) but it seems to have solved
the problem.