Thanks 4 the reminder, jmwills, but it's been setup correctly since day 1.Quote:
Originally posted by jmwills
The default share on a folder is to read only, on all users. Creat a user profile that has write priviledges also. Don't just give it to everyone.
Again to experiement, I moved all the folders to another drive also (last time I just moved the files out from the root directory.)
Now, with the drive being essentially empty I can once again write to it from the other computers like I did before.
Actually, ecross was correct all along. There is no limit on amount of files in the root directory under NTFS. I read the MS article I quoted too fast and missed its finer points. Since then I've re-read it; done more research into this subject and consulted the good old "Upgrading and Repairing PCs" (don't know why I didn't check it there B4.)
But this only serves to deepen the mystery. What then was the problem?
It's not the limit of entries in the root directory as there is none in NTFS.
It's not permission and sharing b/c all are cheked out (both network shares and NTFS permissions.) Plus, I have not changed any of those settings. All I did was emptying out the drive.
The drive had about 200 files in the root directory and there were about 15 folders each with about 10 - 30 files in them.
????? ???? ???? ???? ???? ???? ???? ???? ????
You're not using XP's "Simple File Sharing" are you - it has limitations re account permissions and sharing root directories.
falcon2000, can you please move all those files back and see if the problem recurs?
If it does, can you please post (character-perfect) the errors that the 2000 and NT4 machines display? That one you posted earlier doesn't seem to have anything documented on it.
If the problem comes back then a couple of network traces will be useful as well, but I'll save that set of instructions until I know the error has come back.
Do you have Microsoft File and Print Sharing Service installed? (Or its Windows XP equivalent name)
What type of security is implemented...User-level security or share level on the XP system?
If File and Print Sharing is installed and running, how is it configured for the root directory?
For example if you right click on the root drive and select sharing, what is shown?
What about a firewall. Is a firewall in place anywhere on the network?
Protocols should match for File and Print Sharing and they should each be 32- bit protocols.
This may also be a security feature of XP but not 100% sure.
I would also check to see that the files you are trying to write do not already exist in the root. See if the files you are trying to copy have the read only attribute set also.
rambler,
I've tried both using "Simple File sharing" and not. Same thing. Just out of curiosity what are those special limitations?
Tuttle,
The error I posted B4 was verbatim.
I'll try moving everything back tomorrow and post back the result.
Robert M,
"File and Print Sharing" has always been setup.
Firewall is not an issue. These are pure intranet LAN machines. Never go outside; therofore, no outside firewall installed (the XP one is off, of course.)
The problem is that I had always been able to read & writes; to & from these 3 computers. Problem started just recently. No setting has been changed as far as I know.
I remember researching "Simple file sharing" when I installed XP on my neighbour's PC (he's networked into my LAN). There was something about permissions on the root directory being set to Guest permissions by default, even if the user on the connecting PC had full permission otherwise. In the event, I just installed standard F & P sharing, and I can't check it out, as I've recently reinstalled W2K for him. He wanted fast filesearching back, and he claimed he was in danger of getting RSI with the extra mouse clicks XP seems to need.
I'll see if I can find the article I read.
Found it!
Good info, rambler.However, the drive in question is not a system drive. It's a seperate physical drive for data only.Quote:
You can create a share at the root of the system drive, but simple sharing does not adjust the file permissions on such shares.
Yup, I know that's what you made clear early on, but when you've been around as long as I have, your first rule will be "believe nothing you haven't actually seen working", and your second rule "don't believe everything you read in MS documentation".Quote:
Originally posted by falcon2000
Good info, rambler. However, the drive in question is not a system drive. It's a seperate physical drive for data only.
It was just a thought.
Hey rambler,
Even though it doesn't help solving my problem there're very useful info in that article so I thank you nontheless. :)
I didn'tknow about that "ForceGuest" situation. At first I thought that may be it. But then I realised that when I used to use "Simple Sharing" on this LAN long time ago on I still didn't have the problem I am having now. Strange.
Falcon2000,
Are you saying that You DIDN'T have the problem using Simple File Sharing?
If so, why does that make you think that rambler's "forced guest" thing isn't the problem? Just wondering. They may be mutally exclusive....For example: If Simple File sharing is not in use, the force guest issue may come into play.
I used to use simple sharing. Then switched to the traditional method. Then there were some back and fro between the 2 methods. Now, for a long time now, I have been using the traditional method.
The thing is that until about 2 weeks ago I had never had a single problem either using simple sharing or the traditional method. The settings for sharing and permissions have always been the same. Nothing has changed as far as I know.
Therefore, I think the "ForcedGuest" situation is not the cause of my problem. But I'll look into this more when I can devote more time into this (kinda busy at work these days.
Have you found the solution to this yet?
Here's some other information that may be useful.
http://support.microsoft.com/default...&product=winxp
Some other thoughts I had:
Trying to write a file when a file with this name already is in the root?
The pre-existing file may have the read-only attribute or the file you are copying has the read-only attribute.
Thank you for picking up this old thread.
I've been so busy (company is going through a massive re-organization) that I have all but abandoned this problem (for the time being.)
Anyway, thanks for the link but it's won't help. As mentioned, I have rechecked the sharing & permissions settings more than I can remember. Besides, it used to work just fine. None of those files in question is read-only, either.
Well, when I have time to get back to it I will keep everybody up to date.
:)
Is the disk a removable type such as a zip drive?
If so is there a disk in?