Hi,

In my company we have several PC under windows XP. And a windows 2003
server.

On this windows server, we have connected a USB drive.

But from the PC we are unable to connect to this server USB drive. When
we try to access the shared directory on this drive, we always have the
message "insufisant memory to perform the operation" or something like that.

Do you have an idea on how I can access this USB drive from a windows XP
computer?

Thanks

Lledrith <nospam@invalid.personne> wrote:
Show quoteHide quoteSee
http://windowsitpro.com/article/articleid/71337/jsi-tip-0011---irpstacksize-error.html
.... you have to increase the value of the IRPStackSize in the hosting
computer's registry.

That said, I'm not a fan of sharing removable hard drives over the network.

Lanwench [MVP - Exchange] a écrit :
This was because we needed additional storage and we bought a 2 To USB
hard drive ;)

Lledrith <nospam@invalid.personne> wrote:
I'd have invested in a decent NAS appliance that can participate in AD.

Lanwench [MVP - Exchange] a écrit :

The price is not the same ;) And as we will soon change our server... we
can move a USB drive. And 2 Tb of NAS is very expensive...

Lledrith <nospam@invalid.personne> wrote:
That's true. But good things cost money.

When you change your server invest in an external storage array that gives
you the space you need. I would bet a lot of money that the USB drive you
have now does not give you SAS or SCSI drives in a hardware RAID, which is
the only place you should be storing data you care about. :-)

If cost is the concern, then it's worth noting that most of the commercial
NAS boxes use Busybox Linux as their OS. You can download this for free
anyway, and build your own NAS fromany suitable hardware. Or, you could use
other distros such as Debian or CentOS, which will allow you to add a wider
range of services if needed.

A fullsize case will also allow you far more vesatility in adding drives
than a pokey NAS box. I would be inclined to go for a mobo with SATA-300
interfaces, nowadays the only reason to need a (costly) SCSI/SCA interface is
if you want to use 15,000rpm disks, and in a cost-conscious build that's not
sensible anyway.

If not familiar with Linux/Samba then the build will involve a bit of
head-scratching, but then there is always a tradeoff between
speed-of-deployment and cost. Once done you will have a cracking-good
filestore with absolutely no licensing restrictions on its use.

Show quoteHide quote

But with NAS we are limited by the network speed. That is why I do not
really like NAS. Moreover, NAS has its own rights managements, and that
is what I do not like with NAS.

I do not want to have to create users for user management in the NAS. We
had a iomega NAS before and I do not like that, as I would like to be
able to use my windows users to create the correct right access. And for
the quota management as well.

That is why I prefer a local drive that can use the windows 2003 users
and right management...

You're limited by the network speed anyhow, unless all of your users are
simply working at the local console or via TS or something.

Lacie has some NAS devices that integrate with AD for permissions and
account management.

Show quoteHide quote

DHCP
RRAS and FQDN ('connection-specific dns suffix' is blank)
NLASVC
Server 2008 DC Access Problem
Browsing not working accross VLANs
No DHCP Offers on Wire
sbs 2k3 and dns - driving me crazy
RRAS on Win2003 with 2 public ip's
How to Configure Windows Machine to Allow File Sharing with DNS Alias
How to connect to sql2008 express from xp