Can read but not write to the root directory of a drive in network
Page 1 of 4 123 ... LastLast
Results 1 to 15 of 53

Thread: Can read but not write to the root directory of a drive in network

  1. #1
    Join Date
    Oct 2000
    Location
    Out of NoWhere
    Posts
    3,284

    Can read but not write to the root directory of a drive in network

    3 computers: XP Pro, NT4, Win2000 Pro in a ethernet LAN (workgroup.)

    Everything works fine for a long time, then suddenly:

    There is a drive (a seperate physical drive) in the XP Pro comp. that the other 2 computers can read and copy data from but cannot write or copy to it.

    The funky part is that:
    the other 2 computers can write or copy to any folder in this drive without problem. Just can't write/copy to its root directory (anymore.)

    Any idea?

  2. #2
    Join Date
    Jan 2000
    Location
    Hervey Bay, Queensland Australia
    Posts
    2,005
    Hi Falcon

    The first thought that I have is "how many files and folders are there in root". It would be unusual to get to the max allowed, (I don't remember what that is), but if you did, and no one has changed permissions, you need to look at this.

    For a quick experiment, delete an un-needed a file from root, then try to write a new one there. BF

  3. #3
    Join Date
    Feb 2001
    Location
    Adelaide, South Australia
    Posts
    6,447
    With FAT the limit is 512 root directory entries; less if you have things with long filenames in there. I don't know whether it applies to NTFS or not.
    Safe computing is a habit, not a toolkit.

  4. #4
    Join Date
    Jan 2003
    Location
    US
    Posts
    5,634
    There is no limit to the number of files in a root directory with FAT32 or NTFS. For more details, see the following link.

    Maximum files in root directory
    http://www.is-it-true.org/nt/utips/utips69.shtml
    Eric

  5. #5
    Join Date
    Oct 2000
    Location
    Out of NoWhere
    Posts
    3,284
    The drive is in NTFS.
    There are still plentty of space left.
    Usually short file names.
    Permission has not been changed (just checked to confirm.)

    ???

  6. #6
    Join Date
    Apr 2000
    Posts
    1,579
    The information in the link below may help.
    http://support.microsoft.com/default...&Product=winxp

  7. #7
    Join Date
    Oct 2000
    Location
    Out of NoWhere
    Posts
    3,284
    Thanks 4 the link. Unfortunately, the info there doesn't help.

    I triple checked the permission. "Full Control" is granted to the other 2 computers. So there is no issue there.

    At first I thought it was the limit on file numbers also, but according to the article ecross provided, there is no limit for NTFS.

    Still have 6GB left in that drive.

    ????

  8. #8
    Join Date
    Oct 2000
    Location
    Out of NoWhere
    Posts
    3,284
    According to Microsoft:

    http://www.microsoft.com/resources/d...c_fil_tdrn.asp

    there is a limit on files number per NTFS volume which is 4,294,967,295 (232 minus 1 file). EDIT: it should be 2 to the 32th degree not 232 (don't know how to input that using VB codes.)

    But, still, I am far far from there.

    ????

    2^32 will do just fine. Train The old extended Basic code.
    Last edited by falcon2000; March 25th, 2004 at 02:06 AM.

  9. #9
    Join Date
    Jan 2000
    Location
    Hervey Bay, Queensland Australia
    Posts
    2,005
    Hi Falcon

    Thanks for the link. Perhaps you might like to do a scandisk on that drive, just in case there is rubbish on it which is fooling the thing into thinking that all files are taken. Not likely but you are running out of options. You might like to defrag the thing also. Good luck. BF

  10. #10
    Join Date
    Oct 2000
    Location
    Out of NoWhere
    Posts
    3,284
    Defragged, cleaned up, scanned the drive.

    No go, still.

    ????

  11. #11
    Join Date
    Feb 2001
    Location
    Adelaide, South Australia
    Posts
    6,447
    You said you checked permissions; did you check permissions on both the directory itself and the share? It's possible that the share allows full control but the NTFS permissions on that directory are tighter.

    And since it hasn't been asked yet, what's the exact error you're getting?
    Safe computing is a habit, not a toolkit.

  12. #12
    Join Date
    Oct 2000
    Location
    Out of NoWhere
    Posts
    3,284
    "The specified output destination cannot be seen or created." is the message I get.

  13. #13
    Join Date
    Oct 2000
    Location
    Out of NoWhere
    Posts
    3,284
    Just to experiment I moved all the files in the root directory to another drive. Still no go.

    ????

  14. #14
    Join Date
    Jan 2000
    Location
    Hervey Bay, Queensland Australia
    Posts
    2,005
    It has to be something in the permissions or ownership of the files or the security set up for these files. Have a close look at the properties and security settings. Good luck. BF

  15. #15
    Join Date
    Nov 2003
    Location
    45 Degrees North - 10 Degrees East
    Posts
    1,237
    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.
    MCSE 2003, Network+, Security+
    Microsoft MVP Windows Server - Networking

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •