No PC in my home network can read my 400GB Drives, but can read the others. In my PC, I have nine Seagate HDD's. I'm using two 4-port SATA cards to add more HDD's to my PC. The layout is as follows: 500GB - IDE 200GB - IDE 250GB - SATA Card 1 250GB - SATA Card 1 400GB - SATA Card 1 400GB - SATA Card 1 400GB - SATA Card 2 400GB - SATA Card 2 500GB - SATA Card 2 The two PC's networked via modem/router in my home have no trouble accessing the files on all my other drives, it's just my four 400GB HDD's they can't explore. I've unshared and re-shared all drives for the sake of troubleshooting. I've tried new 4-port SATA cards, new cables, and plugging the unreadable 400GB HDD's cables into various holes on each of the cards. Despite all four unreadable HDD's being 400GB, they're not all the same generation. They are (according to Device Manager): ST340062 ST340062 ST340063 ST340083 Any theories or troubleshooting steps I missed? There are three PC's in my home, and it's annoying that the other two can't read these drives. Technically, they can SEE the drives, and look in their root directories and see folders inside, but if they try to explore any of the folders, they are greeted with the error popup "\\Folder is not accessible. You might not have permission to use this network resource. Contact the administrator of the server to find out if you have access permissions. Access is denied." Again, all the Sharing & Security settings are the same for all my HDD's, including Permissions... it's only the 400GB drives they can't explore. The capacity is the ONLY common factor I can see.

If Pro then disable simple file sharing and correct permissions. Or map drive to include logon as a user that has local rights and passworded logon. NTFS drives have the ability to use two types of permissions. One is the file sharing. Make that read/write all. Then configure the permissions based on ntfs permissions. I read it wrong and answer it wrong too. So get off my case you peanut.

Your conclusion concerning its the capacity causing the issue can't be valid. In a networked environment the capacity or the hardware is transparent to those accessing these resources via the network. Sharing clearly was working. Issue appears to be permissions. My recommendation is ignore ntfs file level rights. They should be wide open at everyone with full control. Same with your share: everyone with full control. I would further suggest that your run chkdsk /r on the drives to assure their integrity. Disable the 400GB host machines filewalls to make sure it was not blocking your access. update: if you are convinced its the size then using disk manager make only a 50gig volume on the drive. If you still get the same message you know its not size. Imagine the power if you knew how to internet search

I disabled File & Print Sharing and shared (with "Everyone" permissions) them manually. Didn't work. One of my 250GB's has been partitioned already, making a small 50GB (currently "J:"). It is accessable on the network. Using Partition Magic, I created a 50GB partition on one of my 400GB drives, and moved all the files to there (and added the same Sharing & Security settings I used on the previous 50GB partition. The other PC's can access the 50GB partition on the 250GB HDD, but NOT the new 50GB partition on the 400GB HDD.

I'm about to run chkdsk /r, but this message pops up: Chkdsk cannot run because the volume is in use by another process. Chkdsk may run if this volume is dismounted first. ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID. Would you like to force a dismount on this volume? (Y/N) Is this okay? The files on my HDD's won't be affected?

"I disabled File & Print Sharing and shared (with "Everyone" permissions) them manually. Didn't work." Sounds to me like you are confusing share permissions with file permissions. You do NOT disable file and print sharing. That kills file sharing period so of course it wouldn't work. Partition Magic? Why? Use Disk Management!!! You want to see the drives from the OS's perspective not from an outside of the system utility!!! Concerning your question on chkdsk I would answer no and then you should be asked the question do you want to schedule it on reboot [or similiar message] which you would answer yes to and then reboot. Chkdsk should run on the volume then. You could answer yes as long as you are sure no apps are open using something on this drive or you could crash. Imagine the power if you knew how to internet search

All those drives and no RAID? Why? "Computer security." — Oxymoron