XP Home Simple Fie Sharing Problem

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello,

Recently (everything has been fine until a few weeks ago) I've started to
have this problem with two XP Home computers running through a router and
with McAfee Personal Firewall on both PCs.

The problem is, when placing files in some sub-folders in the shared
documents on one computer, they have 'disappeared' on the other computer.
It's the same case if the other computer places a file in a sub-folder of its
shared documents. The strange thing is, is that this is only happening with
some sub-folders (though recreating them has no effect). Though the files are
guaranteed to appear on the other computer if they are placed in the root of
the shared documents folder.

So what's going on?

TIA.
 
Hello,

Recently (everything has been fine until a few weeks ago) I've started to
have this problem with two XP Home computers running through a router and
with McAfee Personal Firewall on both PCs.

The problem is, when placing files in some sub-folders in the shared
documents on one computer, they have 'disappeared' on the other computer.
It's the same case if the other computer places a file in a sub-folder of its
shared documents. The strange thing is, is that this is only happening with
some sub-folders (though recreating them has no effect). Though the files are
guaranteed to appear on the other computer if they are placed in the root of
the shared documents folder.

So what's going on?

TIA.
Click to expand...

Alan,

By any chance, is Hotfix 885250 installed?
 
Yes, why do you ask?

Alan.
Click to expand...

Alan,

Your symptoms are similar to others who have installed that Hotfix - please
Google this group, or the web, for details. There is a second Hotfix available
from Microsoft, which they may or may not give to you, depending upon how
persuasive you are when you call them. Or you can un install 885250, as
numerous victims have done.
<http://support.microsoft.com/kb/895900>
 
Thanks for the hint, Chuck.

However, after some searching I found a particularly interesting post at:

http://www.askmarvin.ca/forums/inde...7e8a56dd99ddb&showtopic=3189&st=0&#entry12712

This is the post that provided me with the simple answer:

After working with Microsoft on this issue for a few days now, we have found
the problem (at least it fixed my issue).

The patch from Microsoft caused the issue (885250), but there is a registry
key that is the root cause. The key is
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\NtfsDisable8dot3NameCreation
-- By default, this key is supposed to be set to 0, but the machines hosting
the shares that were giving us the problems had them set to 1. After setting
the key to 0 and then rebooting the machines, we were able to see all files
in the shares even with 885250 installed.

Give this a try and post here if you see the same results after setting the
key to 0.



So, I changed a single registry key and my problem has been solved! Now I
can see all files and folders that previously I couldn't.
 
So what's going on?
Click to expand...

Have the same problem and posted a detailed request for help on Thu,
13 Oct 2005 21:26:48 -0500 under the subject of "Some Files/folders
Within Shared Folder not seen over Network" but no one answered so I
assume no one knows what the problem is. All I can say is that
Linksys (my router and wireless adapter manufacturer) says it is a
Windows problem but they could be passing the buck. At least I got
some feedback from them but no help.

Good luck to both of us as it seems we are on our own on this one.....

Regards,
 
So, I changed a single registry key and my problem has been solved! Now I
can see all files and folders that previously I couldn't.
Click to expand...
Thanks for the hint, Chuck.

However, after some searching I found a particularly interesting post at:

http://www.askmarvin.ca/forums/inde...7e8a56dd99ddb&showtopic=3189&st=0&#entry12712

This is the post that provided me with the simple answer:

After working with Microsoft on this issue for a few days now, we have found
the problem (at least it fixed my issue).

The patch from Microsoft caused the issue (885250), but there is a registry
key that is the root cause. The key is
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\NtfsDisable8dot3NameCreation
-- By default, this key is supposed to be set to 0, but the machines hosting
the shares that were giving us the problems had them set to 1. After setting
the key to 0 and then rebooting the machines, we were able to see all files
in the shares even with 885250 installed.

Give this a try and post here if you see the same results after setting the
key to 0.
Click to expand...

Alan,

That's VERY interesting. Thanks for the link.

Any idea what is different about these "some of the subfolders" on your system,
or why they were susceptible to this setting?
 
Chuck, there wasn't any specifc pattern. These folders showing the sympton
generally were random. I thought perhaps specific file types, file names,
folder names, folder settings but nothing changed - strange.
 
Ed, have a look at the previous reply I made to this post - the solution I
found worked and solved what used to be an incredibly annoying problem. I
knew how you feel.

Post back if the solution helped.
 
Post back if the solution helped.
Click to expand...

The bit was set to 0 (Zero) on my desktop where all folders/files in
the share directory could be seen on the network but that bit was set
to 1 on my laptop where random folders/files located in the share
directory were always missing. I set the bit to 0 (Zero) on the
laptop and everything is working fine now.

Both computers have KB885250 on them but only the laptop had the
specific registry bit set to 1. This makes me question whether it
is/was KB885250 that changed the bit from 0 (Zero) to 1 causing this
foul-up.

Anyway, thank goodness I came across your thread about this instead of
watching my empty thread about the same problem or I would never have
gotten the help I needed....

Thanks a bunch Alan..... I'm back up and running on file transfers...

Best Regards,
Ed
 
Back
Top