Re: Slow file transfer on network drive.

Tech-Archive recommends: Speed Up your PC by fixing your registry

So why does the same action take less time when the same box is loaded with XP?

"Zer0byte" wrote:

> Actualy, it seems to you that its done within the same drive, and controlled
> by your machine, thats wrong, the procedure here is that when you do a copy
> operation, the data and copy commands are transferred from/to server twice,
> so i think if you are going to copy within a mapped drive, that mustnt be in
> the rush hours, that must be in low traffic time.
> Or you have to improve the network infrastructue,, and thats hard to be done
> just for copying files, so i think you have to choose the first choice. which
> is to prevent copying frm server in high traffic times.
>
> "DCA" wrote:
>
> > Thanks for the info, but it didn't help. There must be a difference between
> > how XP and 2K run a copy within the same partition on the same network drive.
> > Is there a way to the server hosting the network drive run the copy?
> >
> > "Zer0byte" wrote:
> >
> > > see what is written here:
> > > http://support.microsoft.com/default.aspx?scid=kb;en-us;814112
> > >
> > >
> > > "DCA" wrote:
> > >
> > > > Thanks for the help. I kinda thought that was why, but what in XP (on the
> > > > same box) makes the same process much quicker? My users are running a
> > > > program that performs the copy, so I'll have to think of another way of
> > > > getting it done.
> > > >
> > > > Thank you.
> > > >
> > > > "Phillip Windell" wrote:
> > > >
> > > > > Becuse it has to copy from the original location across the network to the
> > > > > "buffer" in you local machine and then it has to copy from you local machine
> > > > > back to the new location on the remote machine. In otherwords,...it has to
> > > > > go "over the wire" twice.
> > > > >
> > > > > You solve the problem by not doing that and actually going over to the
> > > > > machine itself and do the copy/move locally. You could also use Remote
> > > > > Desktop.
> > > > >
> > > > > --
> > > > >
> > > > > Phillip Windell [MCP, MVP, CCNA]
> > > > > www.wandtv.com
.

Relevant Pages

  • Re: Slow file transfer on network drive.
    ... that must be in low traffic time. ... >> Or you have to improve the network infrastructue,, and thats hard to be done ... >> is to prevent copying frm server in high traffic times. ...
    (microsoft.public.windows.server.networking)
  • Re: Slow file transfer on network drive.
    ... Idon't know if I'll be changing the registry though. ... that must be in low traffic time. ... >>> Or you have to improve the network infrastructue,, and thats hard to be done ... >>> is to prevent copying frm server in high traffic times. ...
    (microsoft.public.windows.server.networking)
  • Re: Slow file transfer on network drive.
    ... that must be in low traffic time. ... Or you have to improve the network infrastructue,, and thats hard to be done ... is to prevent copying frm server in high traffic times. ...
    (microsoft.public.windows.server.networking)
  • Re: Slow file transfer on network drive.
    ... do you have Novell NetWare server or a UNIX NFS server? ... that must be in low traffic time. ... >> Or you have to improve the network infrastructue,, and thats hard to be done ... >> is to prevent copying frm server in high traffic times. ...
    (microsoft.public.windows.server.networking)
  • Re: Updating asp.net DLLs in production webfarm
    ... Actually, I would remove all except one, at the lowest traffic time ... which you left online (the old requests will be handled from memory, ... by leaving only one server in the farm, ... >>> Can I remove each server one by one from the web farm, update it, then ...
    (microsoft.public.dotnet.framework.aspnet)