win7 notebook cant access xppro usb drive

[dblake]

my thinkpad with win7 cant access usb hard drive conn to my desktop running xppro. it shows up on the tree but cant access the folders. it does access the internal hard drives on the desktop ok.

if i boot to win7 on the desktop the laptop can access the usb drive ok so it appears to be a prob with xp. permissions somewhere?

the odd thing is it accesses the internal hard drives fine, just not the usb drive.

 

[sdifox]

You need to setup sharing on the xppro for the usb hdd

 

[JackMDS]

You have to make sure that the USB gets always the same Drive Letter, then configure its sharing Permission and Security.

 

[dblake]

sharing is setup in xp & the drive letter is the same.

i think i narrowed it down to my pci usb 3.0 card cause when i added my usb 2.0 drive to the network, there was no problem accessing it in xp.

i doubled checked that the usb 3.0 drive works in the network when in win7 & it does.

only thing i can think of is some setting for the card itself. i looked in device mgr but nothing obvious there.

syba claims the card is compat with xp, win7, etc but who knows if they mean network compat. anyway i sent a msg to them.

 

[sdifox]

There is no such thing as network compatible.
Try removing sharing then share it again.

 

[JackMDS]

https://technet.microsoft.com/en-us/library/bb456988.aspx

 

[VirtualLarry]

Are you using the XP credentials, or the Win7 laptop credentials to access it?

To specify machine-specific credentials, you have to use SERVERNAME\USERNAME format.

I had this problem with a NAS, when I upgraded from XP to Win7, I had issues accessing it, until I mastered this little trick.

 

[dblake]

redoing the share didn't help.

not sure about credentials but im trying to access it from the win7pro laptop.

im flummexed by the fact that the usb 2 (conn to mb) drive is seen fine but the usb 3 (conn to pci card) drive gives the permissions error msg & denies access.

the properties tab (on the laptop) for the bad drive show location as \\newbuild2 and description as T (\\newbuild2).
under network tab i have computer name=newbuild2, computer type=windows professional, workgroup=workgroup.

are these credentials a setting somewhere in xp? if so where?

 

[JackMDS]

What drive letter get assigned to th USBs, if it the same change the USB 3 assignment to another letter and redo the sharing.

 

[adam8matek]

What if I do not have usb3 only 2

 

[sdifox]

What if I do not have usb3 only 2

doesn't matter.

 

[dblake]

still no luck but have discovered additional info.

on the win7 laptop, go to explorer-network it shows all the xp desktops networked drives, (7 drives + a printer).

right clicking each one, go to properties & all the ones that work have a security tab listing users, including the usb 2 drive that works. the usb 3 drive that dont work DOES NOT have a security tab.

this seems significant but not sure exactly what it means.

most of the google hits i found for this error msg refer to people that cant access entire computers. in my case i can acces the computer ok & all the drives except the one.

 

[JackMDS]

Is it XP Pro, or Home. XP Home have a rather low allowance for concurrent sharing connections and there is limited Simple Share capacity.

 

[dblake]

xppro.

still googling, i found the bit about checking remove security tab setting in gpedit.msc. it was set at not configured. i tried disable but no help.

 

[sdifox]

Try this

http://www.amydprojects.com/2013/10/permissions-time-machine-v14.html?m=1

 

[dblake]

tried the permissions program but no luck

in win7 i couldn't figure out how to save the parameters & in xp it locked up, couldn't do anything.

I do have some more info tho: from the laptop in win7 command prompt, if I do a dir command on the Y drive (elements 2tb usb drive that shares & has security tab) I get a dir listing. If I do same command on the T drive (seagate 2tb usb drive that won't share & has no security tab) I get 'not enough server storage is available to process this command'.

doesn't quite make sense tho in as much as I had the T drive conn first & when it woudn't work I conn the Y drive & it had no problems. both drives same size EXCEPT the Y drive (works) is usb 2 conn to mb & the T drive (don't work) is usb 3 conn to pci extension card.

I also fired up a 2nd desktop which has vista & xppro on it & got the exact same error msg fot the T drive, ie, no permissions, not enough server storage to process command, etc. the Y drive shared ok in both os's.

 

[sdifox]

What make is the drive you have trouble with?

 

[dblake]

seagate 2T, usb 3 conn to a syba usb 3.0 pci express card (which I'm getting increasingly suspicious of, tho this thing does work if I boot the desktop to win7, so it appears to be just an issue with xp).

the 1 that works is a western digital 2T, usb2 conn to mb

I just found the help video for that permissions prgm & it appears I never had the segate drive loaded. It was in the top narrow window but not the large lower window where I guess it's supposed to be. Guess it wouldn't load cause it won't share. why it appears at all if it won't share it's files is mysterious.

 

[sdifox]

seagate 2T, usb 3 conn to a syba usb 3.0 pci express card (which I'm getting increasingly suspicious of, tho this thing does work if I boot the desktop to win7, so it appears to be just an issue with xp).

the 1 that works is a western digital 2T, usb2 conn to mb

I just found the help video for that permissions prgm & it appears I never had the segate drive loaded. It was in the top narrow window but not the large lower window where I guess it's supposed to be. Guess it wouldn't load cause it won't share. why it appears at all if it won't share it's files is mysterious.

Explain why you are booting to xp when you have win7 on the desktop? Also, have you tried the drive on a usb2.0 port?

 

[dblake]

i got a few programs that won't run on anything newer than xp. meantime i'm constantly running anti spyware/malware/virus programs. suppose i'll eventually switch.

in any case, solved the problem. should have paid more attn to last line of error msg re 'not enough server storage...'. stumbled on this http://www.techfleece.com/2011/03/03/how-to-fix-not-enough-server-storage-is-available-to-process-this-command-error/
and it worked like a charm.

 

[sdifox]

As long as it gets fixed.