• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Can't access mapped drive from external HD

G

ghart999

Member
Hi all.

I have a new Buffalo Drivestation external 250GB drive that I am trying to access from other PC's on my nextwork. The drive is hooked direct via USB2.0 to one of my PC's. I have mapped the entire drive from within XP Home using the standard Share Drive functionality by right-clicking on the drive in file explorer and selecting Sharing and Security. The image below shows exactly what my screen looks like for this step.

http://tinypic.com/view.php?pic=4t6d7xx

At this point everything seems fine. The drive shows the little sharing icon on it and the drive even shows up on my other PC's under network neighborhood. The problem is when I click on the drive from another PC I get an error that says. "\\DESKTOPPC\Movies _(H is not accessible. You might not have permission to use this network resource. Not enough server storage is available to process this command."

How could I not have permissions as XP Home does not even have options for permission setting. Further what does the not enough server storage space error mean. The external drive has 50GB free space.

I have other drives within the same PC (where the Buffalo is connected) that are mapped and accessible no problem. It seems it is something different with being an external drive or something. Any suggestions???

Also I am sure that all the PCs have the same network group name, etc and I can share drives between all the PC's just fine. This is the only one causing issues.


Thank you so much.

Gregg
 
Wow - how the hell did you find that? I will try it when I get home. However I don't use Norton antivirus, but rather Zone. Maybe it will work though. Thanks a lot for the suggestion.
 
Bumb. Still a major problem for me. I verifies this occurs only on my main desktop and not other pc's on my network. And it also happens with multiple eternal drives. Any ideas???
 
Really sounds like a permissions problem. You don't even have access to view the properties of the share, hence the error message.

Try taking ownership of the drive and it's folders from the machine that is sharing.
 
Originally posted by: spidey07
Really sounds like a permissions problem. You don't even have access to view the properties of the share, hence the error message.

Try taking ownership of the drive and it's folders from the machine that is sharing.
Click to expand...

Not exactly sure what you mean. I can fully access the drive and the folders from the PC where the drive is connected via USB2.0.

I set permissions where anyone should be able to edit the drive as well.

 
What exactly are the permissions for the drive and for the share and exactly what is the username the other client PC is logging in as?

My guess is the client is using the "Guest" username/account and you don't have this user in your permissions for the share or the folders in the share.
 
A common problem with network shares is a conflict between local USB devices and the network share. Local devices, even those that are unused, will tromp over network shares.

Go into the Disk Management control panel and change the drive letters of all used and un-used USB drives (such as memory card readers). Move their drive letters to high letters (above "s:"). Reboot the PC and see if you can access the shared folders.
 
Originally posted by: spidey07
What exactly are the permissions for the drive and for the share and exactly what is the username the other client PC is logging in as?

My guess is the client is using the "Guest" username/account and you don't have this user in your permissions for the share or the folders in the share.
Click to expand...

XP Home does not allow you to set permissions for different accounts. The drive is accessible to all or its not accessible to anyone. At least I have never seen a place to select permissions.
 
Originally posted by: RebateMonger
A common problem with network shares is a conflict between local USB devices and the network share. Local devices, even those that are unused, will tromp over network shares.

Go into the Disk Management control panel and change the drive letters of all used and un-used USB drives (such as memory card readers). Move their drive letters to high letters (above "s:"). Reboot the PC and see if you can access the shared folders.
Click to expand...

Thanks for the suggestion. I will try that and see what happens. I only have the one USB drive plugged in and its set at G drive. I will rename to U and see what happens. I do have a USB card reader but I plug it in/out only when I use it.
 
That did not seem to work. Also a new problem, even internal drives cannot are inaccessible from other PCs and not just external drives. This is killing me. Please help if you can.
 
Uh...would you mind filling everybody in on how you came to that solution? Were you getting errors in your XP Event Logs that pointed to IRPStackSize errors?

Quote from a UseNet thread:
SOLUTION: Windows XP, Windows 2000, and Windows NT all have an IRPStackSize value that controls how much physical storage space and RAM are available to new applications, and some new software installs incorrectly set this value.
This value ranges from 11 to 20 for XP and from 11 to 15 for Win2K and NT. If you set this value to less than 11, you'll receive an error message indicating that the system doesn't have enough server storage. As a result, clients won't be able to access network shares and Event ID 2011 will appear in the System log.

Originally posted by: nweaver
you have a permissions issue...I hate XP Home because of simple file sharing
Click to expand...
Amen. The two different Permissions models makes support of XP Home a pain for those who don't normally use it.
 
Yeah someone earlier in the thread mentioned doing what I did. However I did not have IRPStackSize as a parameter. After further research I found you can just create it and then put in a value. Believe it or not it worked.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top