-
No, it's just an ordinary internal IDE drive.
Thanks again for tying.
I've given up on this issue. For a short while (a couples of months) the problem disappear but it started again recently. It's not a big deal really; just a little bit of an annoyance.
-
When this problem crops up, can you write files to the root of the other physical disk?
What method are you trying to perform the write operation?
For example, are you dragging and dropping, pasting, or using a command prompt
Are you trying to move a file to the root or copy a file to the root?
Do all the computers belong to the same domain?
What network clients are loaded?
-
When this problem crops up, can you write files to the root of the other physical disk?
Yes.
What method are you trying to perform the write operation?
For example, are you dragging and dropping, pasting, or using a command prompt
Copy/paste, copy to/move to.
Are you trying to move a file to the root or copy a file to the root?
Yes ... from one computer to another.
Do all the computers belong to the same domain?
Not in a domain. Workgroup.
What network clients are loaded?
Client for MS Network, File & Printer sharing, TCP/IP
-
File and Printer Sharing for Microsoft Networks
or
File and Printer Sharing for Netware Networks?
File and Printer Sharing (for Microsoft Networks or Netware Networks) requires the Microsoft supplied 32-bit clients...
For example:
the 32-bit, Microsoft Client for Microsoft Networks
or
the 32-bit, Microsoft Client for Netware Networks.
If you are not using a server for authentication, simple file sharing must be installed, enabled and configured on the machine doing the sharing. My understanding from your previous post is that you had not had simple file sharing enabled at this time.
-
File and Printer Sharing for Microsoft Networks.
Client for Microsoft Networks is installed.
Have tried both "Simple File Sharing" both on & off ... make no difference.
-
Is TCP-IP the only protocol running on all three?
Was this drive recently converted to NTFS?
With Simple File Sharing, I think the procedure is as follows, once simple file sharing is installed and enabled.
On the computer where the needed files are:
Right click the drive and directory, find and select the sharing options.
For example, with simple file sharing, one option may be called
"Requires password"
Enable that and then assign a password for the root directory.
At least that's the way it works in Windows 95.
Have you tried the procedure while running the NETBEUI protocol?
See the following link
http://support.microsoft.com/default...&Product=winxp
Sometimes files retain the access rights and permissions which they had from a previous directory.
With the NTFS file system, permissions and access rights can be assigned on a file by file basis.
Sorry, don't know much more about it.
-
Since your message can't be found elsewhere, I would check the BIOS/CMOS setup for the target drive and be sure it's OK.
Also check for options which prevent or allow writes to the root in the BIOS/CMOS setup.
I would also be sure that a utility such as Norton Antivirus or VSAFE or other programs which can protect files is not running at any of the computers.
What file systems are in use on the other two computers?
FAT? FAT32? NTFS
What about on the drive which doesn't present the problem?
Is that message reported at the XP computer, or at the screen of one of the other remote computers?
If at a remote computer, what message appears when you try to perform the copy or move using the XP keyboard instead?
-
Thank you 4 the continuous interest in this thread.
Is TCP-IP the only protocol running on all three?
Yes.
Was this drive recently converted to NTFS?
No. It's been NTFS all along.
What file systems are in use on the other two computers?
All NTFS.
Have you tried the procedure while running the NETBEUI protocol?
I think so ... not sure ... had tried a lot of different things.
Simple File Sharing
As posted B4 it happened w/ or w/ Simple File Sharing.
With the NTFS file system, permissions and access rights can be assigned on a file by file basis.
But I have never set that up.
I would check the BIOS/CMOS setup for the target drive and be sure it's OK.
I'm sure the drive is fine.
Also check for options which prevent or allow writes to the root in the BIOS/CMOS setup.
No such setting in that BIOS.
Is that message reported at the XP computer, or at the screen of one of the other remote computers?
The other computers.
-
What about this?
I would also be sure that a utility such as Norton Antivirus or VSAFE or other programs which can protect files is not running at any of the computers.
-
Sorry, forgot to answer that one.
I've tried NAV on and off. Makes no different.
-
Turn off Norton on all three, reboot all three, and try again.
-
An excerpt from that Microsoft article I posted earlier is below.
With file sharing in Windows XP, you can configure five levels of permissions. Level 1 is the most private and secure setting, and Level 5 is the most public and changeable (non-secure) setting. You can configure Levels 1, 2, 4, and 5 by using the Simple File Sharing UI. To do this, right-click the folder, and then click Sharing and Security to open the Simple File Sharing UI. To configure Level 3, copy a file or folder into the Shared Documents folder under My Computer. This configuration does not change when you turn on or turn off Simple File Sharing.
What is in the Shared Documents folder when you have this problem?
-
Robert, I've pretty much given up on this issue but I thank you nonetheless.
I have tried both w/ NAV on & off but it makes no difference.
As far as permission is concern ... I've looked into that many times and have not seen anything that is suspecious.
The problem only occurs when the root directory is populated to a certain degree ... I've not spent the time to really make detail observations but it seems that when about 40% (or even as low as 30%) of the drive capacity is reached then I can't write to that root directory from a network computer any more ... only to its sub-directory is possible.
-
Are disk quotas set up on the Windows XP computer?
If they are, you may not neccessarily receive a warning when your quotas were reached depending on how that warning option was set.
-
