Extracted files invisible on shared drive?

[Kirk MacLean_1]

When files are extracted from an archive (zip tar etc.) which came from a Unix machine, the files can only be seen on the local machine and are missing from the subdirectory of the main network share. By cutting and pasting the files to a new folder, they become visible to the network clients. This is an issue because the system was just migrated from a unix network and there could be untold files hidden in the shared tree. Tried security settings This is a new XW4200 w/ XPSP2 workgroup environment.

[Ron Kinner]

On the machine where the files are, open a cmd window and cd to the folder containing the files. Then

attrib -h -s -r *.*

Does that help?

Ron

[Kirk MacLean_1]

Tried the attrib suggestion: same result.

[Jon Finley]

The cut and paste works, because the files inherit the permissions of the folder.

It still comes back to a permissions thing.

If the Administrator Takes control of the tree, and forces full control to replicate through all sub folders, the files "should" become visable.

Jon

[Kirk MacLean_1]

As you explained: "If the Administrator Takes control of the tree, and forces full control to replicate through all sub folders, the files "should" become visable."
I have sone this with no positive effect on accesibility.

There are a large number of ID: 10009 DCOM errors in the event log.
DCOM was unable to communicate with the computer (name of client attempting to access share) using any of the configured protocols. Have found numerous writings about this that lead me to believe this is semi normal behavior.

On the client, I have seen this Event: 3019, The redirector failed to determine the connection type. Found a patch that silenced the message but did not resolve the issue.

Anyone recommend a good remote support provider?

[Kirk MacLean_2]

Never did resolve this one. Ended up buying $35 XP support from Microsoft India. After explaining and training their support personnel twice it was sent to the "R&D" team. After re-explaining, testing, and retesting the shares had to be opened up so guest user had ownership of the share to eliminate the problem. Of course this creates a new set of problems...